As per https://communities.vmware.com/docs/DOC-9279 %USED is the percentage of physical CPU time accounted to the world. If a system service runs on behalf of this world, the time spent by that service (i.e. %SYS) should be charged to this world. If not, the time spent (i.e. %OVRLP) should not be charged against this world. So ideally, %USED = %RUN + %SYS - %OVRLP However, why does this value exceed 100%? The answer simply is Turbo boost....
The sfcbd (Small foot print CIM broker daemon) is responsible for reporting the hardware status that is viewed via the vSphere client. In order to enable debug logging: Stop sfcbd service by running the command: /etc/init.d/sfcbd-watchdog stop Set the CIM log level to 7 by running the command: esxcfg-advcfg -s 7 /UserVars/CIMLogLevel Start sfcbd service by running the command: /etc/init.d/sfcbd-watchdog start Collect the vmsupport log bundle. In ESXi 5.1 and above, sfcbd logs to /var/log/syslog....
Afraid that the scp transfer will eat up all available Bandwidth? To throttle scp file transfers, use the ‘-l’ parameter: For e.g.: To set the file transfer limit to 1Mbps scp -v -l 1024 useraccount@destinationhost:/path scp -v -l 1024 vmware.log root@10.10.10.101:/tmp
Worked on this issue recently where, after upgrading to ESXi 5.5, a rescan on a software ISCSI initiator was taking a long time to complete. About 10 minutes. There were only two LUN’s presented to the software ISCSI initiator The software ISCSI initiator was configured to discover LUN’s from four targets. The vmkernel.log and hostd.log did not show any errors or relevant messages for the ISCSI initiator. The software ISCSI daemon logs into the following file: /var/log/syslog....
In order to check if a snapshot chain is broken in ESXi 5.x and later: Run the command: `vmkfstools -e -v10 .vmdk For e.g: vmkfstools -e -v10 “XP-64-000003.vmdk”