Hello everyone

I got the following message every hour:

"Remote access for ESXi local user account 'root'  has been locked for 120 seconds..."

I found a lot of information how to figure this out:

Security.AccountLockFailures. Maximum number of failed login attempts before a user’s account is locked. Zero disables account locking.

Security.AccountUnlockTime. Number of seconds that a user is locked out.

But I didn't get out where to find the source IP who is trying to access our ESXi hosts. Isn't it in /var/log/auth.log ?

Thank you for your input.

I am installing ESXi 6.0 on 6 Dell PowerEdge R440's  They all have 2 default onboard 1GB nics installed as well as Broadcom 57412 Dual Port 10GB SFP+ PCIe Adapter and Broadcom 57416 Dual Port 10 GB E BaseT Network LOM Mezz Card.  Both are on the HCL for this version of ESXi.

After installing 6.0 on the hardware, I went in to configure the network and the only NICs I see are the onboard 1GB nics.  From vCenter all I can see are the 2 onboard nics.  I thought maybe it was a Driver issue  so I researched and found the vib file from VM to install the driver on my host.  When I run the esxcli software vib command, it returned that it skipped the vib for the driver.

I run lspci and I find all 6 nic's in the list.  I run esxcli network nic list, but only see the 2 onboard nics.  If I go into my vCenter, I can find the additional 4 cards when I go to the host\Manage\ Hardware\PCI Devices and Edit PCI Device Availability, but that enables passthrough so that the VM's can directly access the ports, but that is not what I want.  I want them in the vSwitch so all VM's use those ports instead of the 1GB ports.

Any suggestions\help would be greatly appreciated.

Hello All, Good Day to you!

In my customer environment, we have a 100GB LUN specified solely for swapping. However it is now full, with only 322 MB remaining - and right now it doesn't allow any host vMotion saying that there isn't enough free space. When I browse the relevant data store I can see a lot of .vswp files ans some .swp files ( I am attching the data store ). As far as I know  a VM seperates out for itself a capacity equal to it's guest memory size on the swap space. What would be the best way to figure out which .vswp files are not required, and which are ? I can easily expand this LUN on the VNX, but would that be god administering - anyways on the LUN properties, I can see that it is only using 4+% - How does that figure with what is told me in the VMware front ( I would be asking this in an EMC forum seperately ) ?

Basically is there any adminstration guide with regards to virtual memory usage in VMware ?  Or should I simply expand the LUN and add the expanded capacity on the VMware side ? What is the difference between vmx-XXXX.vswp, XXXX.vswp and sysswp-xyz.swp , where XXXX presents VMname ?

Regards,

Naleendra

Today I installed a fresh homelab with esxi 6.5. All with default settings.

After created successfully an Ubuntu server and Windows 10 workstation I was ready to setup a new Windows 2016 server. Right after starting up the server it comes with:

I thought I did something wrong with selecting the SCSI Controller. What ever I choose to use I always get this message.

Tried the paravirtual SCSI and browsed the VMware tools to the driver, but same error.

Tried Windows 2012R2 and same message.

With esxi 6 never had this problem

Anyone having a tip to look further?

Setup

• Closed lab (no internet access)
• One Physical switch
• 4 working ESXi VM Hosts (but only one powered on for this issue)
  2 with ESXi 6.5, 2 with ESXi 6.7.
• One Windows 10 Pro PC - with installed VMWare Workstation 14 running vCenter VM and Content Library NAS (FreeNAS) VM
• 2 other Windows 10 Pro PCs
• All static IP addresses;   No Windows Servers (no active directory), DHCP, etc.
  BIND for DNS service (needed by vCenter)
• All VMWare products are currently evaluation licenses.

Note: newbie VMWare user...

Description:

Wanted to perform a disk test to compare between a physical PC and a VM, so I wrote an application to append the contents of one file (75 GB) to the end of an existing one (5 GB).

I ran the test app on a older and slower (as compared to the one for the ESXi Host) Windows 10 Pro physical PC (SATA IDE) - took 15 mins to complete.

The same test on a Windows 10 Pro VM running in an ESXi 6.7 Host (SATA AHCI) - took 37 minutes.

Basically, it's just this VM Host with the one VM running.

Why would there would be such a big difference in time?

Appreciate any help... Thank you.

-------------------------------------------------------------------------------------------

Details of ESXi 6.7 Host:

• SuperMicro X10SRA-F (Intel C612 SATA Controller)
• 128GB memory
• BIOS I/O configured for SATA AHCI
• DataStore consists of 2 1 Seagate 1TB SATA HD (no RAID)
• version of AHCI native driver:  1.2.0-6vmw.670.0.0.8169922

Details of VM:

• 1 CPU
• 8 GB memory
• 512 GB disk
  SCSI Controller (1:0), LSI Logic SAS, Dependant
• Windows 10 Pro

Disk performance stats (esxtop):

Hi, this issue started 2 days ago when I attempted to update from 6.5.0.20100 to "VC-6.5.0U2b-Appliance-FP" (6.5.0.21000 Build Number 8815520) in the vSphere Appliance Management. It stopped at 60% and prompted with an error code about "not being able to contact the server...". I then restarted the Appliance and from there it went down hill.

I figured out if I ran the command "Service vami-lighttp start" and  it came up again, but after some time I couldn't authenticate etc.. seems as some services aren't running.

I did find this discussion in a different thread and noticed it was the exact same issue I have -> vCenter 6.5 - vcenter appliance stops working out of the blue, AGAIN!!

I will post the same output and hopefully figure this out. (I did notice those 4 commands, but haven't used those yet since I don't quite understand what they do)

service-control --status
Running:
 applmgmt lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-psc-client vmware-rhttpproxy vmware-sca vmware-sps vmware-sts-idmd vmware-stsd vmware-updatemgr vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui
Stopped:
 vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-rbd-watchdog vmware-statsmonitor vmware-vcha

service-control --start vmware-vpxd-svcs
Perform start operation. vmon_profile=None, svc_names=['vmware-vpxd-svcs'], include_coreossvcs=False, include_leafossvcs=False
2018-07-18T17:45:49.534Z   Service vpxd-svcs state STARTED
Successfully started service vpxd-svcs

systemctl list-unit-files | grep vmware
vmware-bigsister.service               static
vmware-cis-license.service             masked
vmware-cm.service                      masked
vmware-content-library.service         masked
vmware-eam.service                     masked
vmware-firewall.service                enabled
vmware-imagebuilder.service            masked
vmware-mbcs.service                    masked
vmware-netdump.service                 masked
vmware-perfcharts.service              masked
vmware-pschealth.service               masked
vmware-rbd-watchdog.service            masked
vmware-rhttpproxy.service              masked
vmware-sca.service                     masked
vmware-sps.service                     masked
vmware-statsmonitor.service            masked
vmware-updatemgr.service               masked
vmware-vapi.service                    masked
vmware-vcha.service                    masked
vmware-vmon.service                    enabled
vmware-vmonapi.service                 masked
vmware-vpostgres.service               masked
vmware-vpxd-svcs.service               masked
vmware-vpxd.service                    masked
vmware-vsan-health.service             masked
vmware-vsm.service                     masked
vmware-bigsister.timer                 disabled

After running the "service-control --start vmware-vpxd-svcs" the Appliance Manager came up again.

systemctl list-unit-files | grep masked
applmgmt.service                       masked
vmcam.service                          masked
vmware-cis-license.service             masked
vmware-cm.service                      masked
vmware-content-library.service         masked
vmware-eam.service                     masked
vmware-imagebuilder.service            masked
vmware-mbcs.service                    masked
vmware-netdump.service                 masked
vmware-perfcharts.service              masked
vmware-pschealth.service               masked
vmware-rbd-watchdog.service            masked
vmware-rhttpproxy.service              masked
vmware-sca.service                     masked
vmware-sps.service                     masked
vmware-statsmonitor.service            masked
vmware-updatemgr.service               masked
vmware-vapi.service                    masked
vmware-vcha.service                    masked
vmware-vmonapi.service                 masked
vmware-vpostgres.service               masked
vmware-vpxd-svcs.service               masked
vmware-vpxd.service                    masked
vmware-vsan-health.service             masked
vmware-vsm.service                     masked
vsphere-client.service                 masked
vsphere-ui.service                     masked
ctrl-alt-del.target                    masked

/etc/systemd/system ]# ls -lisa
total 108
180710 4 drwxr-xr-x 24 root root 4096 Jul 17 17:01 .
180226 4 drwxr-xr-x  7 root root 4096 May 31 15:04 ..
183069 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 applmgmt.service -> /dev/null
183110 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 applmgmt.service.d
182577 0 lrwxrwxrwx  1 root root   40 Feb  3  2017 default.target -> /usr/lib/systemd/system/runlevel3.target
180712 4 drwxr-xr-x  2 root root 4096 May 31 15:03 getty.target.wants
183131 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 halt.target.wants
188806 4 drwxr-xr-x  2 root root 4096 Feb  3  2017 local-fs.target.wants
182743 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 lwsmd.service.d
180714 4 drwxr-xr-x  2 root root 4096 Jul 17 19:58 multi-user.target.wants
180718 4 drwxr-xr-x  2 root root 4096 May 31 15:03 network-online.target.wants
183133 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 poweroff.target.wants
183129 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 reboot.target.wants
182530 4 -rw-r--r--  1 root root  268 Jun  7  2016 sendmail.service
183127 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 shutdown.target.wants
182483 4 -rw-r--r--  1 root root  476 Mar  1 19:03 snmpd.service
180720 4 drwxr-xr-x  2 root root 4096 May 31 15:03 sockets.target.wants
180722 4 drwxr-xr-x  2 root root 4096 May 31 15:03 sysinit.target.wants
182042 0 lrwxrwxrwx  1 root root   39 Feb  3  2017 syslog.service -> /usr/lib/systemd/system/rsyslog.service
182708 4 -r-xr-xr-x  1 root root  470 Jun 13 09:50 vcha-hacheck.service
232102 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmafdd.service.d
320650 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmcad.service.d
183086 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmcam.service -> /dev/null
182854 4 drwxr-xr-x  2 root root 4096 May  7 12:12 vmcam.service.d
320579 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmdird.service.d
320789 4 drwxr-xr-x  2 root root 4096 May  7 12:12 vmdnsd.service.d
182138 4 drwxr-xr-x  2 root root 4096 Feb  3  2017 vmtoolsd.service.requires
182905 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-cis-license.service -> /dev/null
182904 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-cm.service -> /dev/null
183082 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-content-library.service -> /dev/null
183083 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-eam.service -> /dev/null
183104 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-imagebuilder.service -> /dev/null
183076 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-mbcs.service -> /dev/null
183072 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-netdump.service -> /dev/null
183105 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-perfcharts.service -> /dev/null
182906 4 drwxr-xr-x  2 root root 4096 Jul 17 23:18 vmware-psc-client.service.d
183073 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-pschealth.service -> /dev/null
183084 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-rbd-watchdog.service -> /dev/null
182903 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-rhttpproxy.service -> /dev/null
182916 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-sca.service -> /dev/null
183087 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-sps.service -> /dev/null
183074 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-statsmonitor.service -> /dev/null
183118 4 drwxr-xr-x  2 root root 4096 Jul 17 23:18 vmware-stsd.service.d
183122 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmware-sts-idmd.service.d
183093 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-updatemgr.service -> /dev/null
183060 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vapi.service -> /dev/null
182878 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vcha.service -> /dev/null
183067 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vmonapi.service -> /dev/null
183114 4 drwxr-xr-x  2 root root 4096 Jul 17 23:18 vmware-vmon.service.d
183075 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vpostgres.service -> /dev/null
183081 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vpxd.service -> /dev/null
182872 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vpxd-svcs.service -> /dev/null
183094 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vsan-health.service -> /dev/null
183103 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vsm.service -> /dev/null
183077 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vsphere-client.service -> /dev/null
183080 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vsphere-ui.service -> /dev/null

Can anybody help me with this error

"Unable to connect to the MKS: Internal error"

It's appear on my console, when i want to install my first Host.

I'm using Vmware ESX

Thanks,

Hi there,

I wish all a happy new year!

Did anybody ever tried to manipulate the CPUID, which is shown to the guest OS?

I have the following scenario:

CPUID shown in the guest OS: 0FABFBFF00020651
 

vmx-File Parameters:
 

guestCPUID.0 = "0000000b756e65476c65746e49656e69"
guestCPUID.1 = "0002065100010800829822030fabfbff"
 
As you can see I find the ID shown above splitted in two parts inside of the value of guestCPUID.1 (marked in bold).
 
 
I need to change this ID to 0FEBFBFF000006F1
If I manipulate the guestCPUID.1 value according to the ID I need I get the following result: After PowerOn the VM again the value gets instantly overwritten by the original value.  
I assume that the other part of the value and maybe also guestCPUID.0 are also related in some way.

Unfortunally I can´t find anything in the documation / google about this paramaters.

Thanks for any help!

Cheers,

Mario
 
 

Hi Guys,

Hope to get some needed guidance.

I've read several KBA's and posts from here but still I cant get my VM to open...

The files that I have are:

Error show on power on:

Failed to start the virtual machine.

Module 'Disk' power on failed.

Cannot open the disk '/vmfs/volumes/5a0edc98-5d83df4e-1c3d-a0369fe81e02/SAFEGUARD/SAFEGUARD.vmdk' or one of the snapshot disks it depends on.

The file specified is not a virtual disk

File system specific implementation of LookupAndOpen[file] failed

File system specific implementation of LookupAndOpen[file] failed

In attachment is the vmware.log file.

Ive tried:

VMware Knowledge Base

VMware Knowledge Base

VMware Knowledge Base

But with no luck unfortunately...

Can somebody kindly point me to the right direction?

Thanks in advance!

Hi,

First time post!

I am having trouble installing server 2008 r2 from an ISO that I downloaded from Technet.

I have done checksum and the iso is okay.

I have created a virtual machine using server 2008 r2 type. 

I start the machine and then connect the iso using "connect to ISO image on local disk..." option in the cd drive icon.

It tries for a little and errors with:

PXE-E53: No boot filename received

PXE-M0f: Exiting Intel PXE ROM.

Operating system not found.

Also looked at the VM > properties > Hardware > CD/DVD drive 1 and checked Device type selected was Client Device

I checked the virtual machine in options > Boot options and made sure there was a delay for the boot iso to be recognised and then

I thought it might be trying pixie boot so I opened the BIOS on the virtual machine and moved Network boot to the bottom

I have faith in the ISO because I accidentally tried installing onto an Ubuntu VM I had created and it got to the windows loading screen for the DVD.

Any thoughts why I can't install using a Windows 2008 r2 iso onto esxi 5.0?

Thanks,

Shaun

Hi,

I just face a event log as below:

Warning message from localhost.localdomain:

The guest OS has reported an error during

quiescing. The error code was: 5 The error

message was: 'VssSyncStart' operation failed:

IDispatch error #8449 (0x80042301)

warning

it caused the Acronis Backup software fail to backup

In Communities information, it seem relate to disk space and i/o speed.

For disk space, we should have enough disk space for OS.

Also i trust it is not heavy duty when backup, i/o should be enough

In knowledge base 1018194, resolution is reboot the virtual machine.

is it reboot the acronis appliance or our production os?

Any method to prevent the same?

Existing our version is EXSi 5.1 built 799733.

Thank you

Rgds,

Sun

Hello everyone

I got the following message every hour:

"Remote access for ESXi local user account 'root'  has been locked for 120 seconds..."

I found a lot of information how to figure this out:

Security.AccountLockFailures. Maximum number of failed login attempts before a user’s account is locked. Zero disables account locking.

Security.AccountUnlockTime. Number of seconds that a user is locked out.

But I didn't get out where to find the source IP who is trying to access our ESXi hosts. Isn't it in /var/log/auth.log ?

Thank you for your input.

What is meaning of option "Quiesce Guest File System" while taking snapshot. And what is its use? Please share deep dive.

Hi Experts,

We have an exisiting VMware cluster with windows server 2008 on ESXi 5.5.  We are planning to use Windows Server 2016 with DC edition.

Is it advisable to use exisiting hardware/cluster or new hardware/cluster to benifit from licensing.

Thaks

Dear team,

in my environment i have esx 3.5.0 (64607),4.0,4.1 hosts, just want to know is there any impact if i restart management service on production esx hosts 3.5.0, 4.0,4.1

be fore restarting this service do i need to take check anything, is there any pre-requisite ?????

regards

Mr VMware

I have several ESXi 5.1 hosts in a cluster. There is one vm that I can't add to inventory. I have followed several kb articles and even removed the ESXi host from the cluster completely after verifying that it was the ESXi host causing the lock by finding the MAC address. I am unable to view the vmware.log file for this virtual machine. I get an "invalid argument" error when trying to cat the vmware.log or the .vmx file. The lock file is "vmname.vmx.lck". I've rebooted and restarted the management agents several times. I'm just not sure where to proceed from here as I've been reading about how to resolve this for about 3 hours and have yet to find anything that works. The contents of the directory contain the following files if this helps at all:

Suggestions?

I'm trying to mount an NFS volume on ESXI 6, but keep running into this error.  Googling about hasn't helped, so here I am. Error:

Call "HostDatastoreSystem.CreateNasDatastore" for object "ha-datastoresystem" on ESXi "192.168.xx.xx" failed.

Operation failed, diagnostics report: Unable to get console path for volume, sample name.

The NFS share is located on a synology nas. I've checked permissions and configuration. Everything looks correct based on the various tips and KB articles.

Ideas?

Thanks.

Has anyone seen these event log entries on virtual windows servers - they seem to be floooding the application logs.

Where do they come from, what do they mean and can I stop them from being logged without missing any important information?

Log Name:      Application
Source:        vmStatsProvider
Date:          17/07/2013 09:02:06
Event ID:      258
Task Category: Guest Library API
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     
Description:
The "vmGuestLibrary" is successfully initialized for this Virtual Machine.

Log Name:      Application
Source:        vmStatsProvider
Date:          17/07/2013 09:02:06
Event ID:      256
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     
Description:
The "vmStatsProvider" is successfully initialized for this Virtual Machine. WMI namespace: "root\cimv2".

** I've just noticed that they seem log every 30 minutes.

Hi,

Can the vSphere 6.5 support the auto reclaimed space of datastore? e.g. If I write and delete the 100GB files on one of VM, the datastore can reclaim the space of datastore?

Can the vSphere 5.5 / 6 support the manual reclaim space? Where to run the reclaiming function through GUI? Need command base to do that?

Hi All,

We have a requirement to assign Physical NIC to Virtual Machine , Can someone confirm how this can be achieved ?

Thanks in advance !!

Regards,

Varun Khatri