VMWare released new image for ESXi5.0 on 15th December. Following bugs are fixed. List is huge but following made sense to me
- This image profile enables support for Mac OS X 10.7 and Mac OS X 10.7.1.
Mac OS X 10.7.2 is not supported by this patch release.
- vMotion fails with the A general system error occurred: Failed to flush checkpoint data! error message when:
- The resolution of the virtual machines is higher than 1280×1024, or smaller if you are using a second screen
- The guest operating system is using the WDDM driver (Windows 7, Windows 2008 R2, Windows 2008, Windows Vista)
- The virtual machine is using Virtual Machine Hardware version 8.
Call”HostProfileManager.CreateProfile” for object “HostProfileManager” on vCenter Server”<Server_Name> failed.
Error extracting indication configuation: [Errno- 2] Name or service not known.
For example, to set the login timeout value to 10 seconds you can use commands similar to the following:
~ # vmkiscsi-tool -W -a “login_timeout=10” vmhba37
~ # esxcli iscsi adapter param set -A vmhba37 -k LoginTimeout -v 10
The default login timeout value is 5 seconds and the maximum value that you can set is 60 seconds. We recommend that you change the login timeout value only if suggested by the storage vendor.
- The updated tools-light VIB updates the pre-built kernel driver modules for Ubuntu 10.04.3, Ubuntu 11.04, and Ubuntu 11.10. In addition, it also resolves the following issues:
- When VMware Tools installed on a Windows XP virtual machine running on an ESXi 5.0 host patched with ESXi500-201109001 is upgraded using the automatic upgrade option, a warning message similar to the following might be displayed in the Software Installation window of the virtual machine: The software you are installing has not passed Windows Logo testing to verify its compatibility with Windows XP.
This issue also occurs when VMware Tools is installed by using the Install/Upgrade Tools option and selecting the complete mode, or custom mode with LSI driver selected.
- When a virtual machine with Windows 2003 guest operating system is installed with a Windows XP display driver model (XPDM) driver, the virtual machine might stop responding with a malloc() in vmx_fb.dll error and fails with a blue screen and STOP 8E vmx_fb.dll error.
This VIB updates the VMware display driver version to 220.127.116.11.
- VMXNET 3 driver versions 18.104.22.168-k to 22.214.171.124-k fail to activate the device if the number of vCPUs that you assign to a virtual machine is not a power of two. You might see an error message similar to the following while running the demsg command:
Failed to activate dev eth0:error 1
- An error message similar to the following might be written to vmware.log:
VMXNET3 user: failed to activate Ethernet1 with status 0xbad0007
The updated net-e1000 and net-e1000e VIBs resolve a security issue in the e1000 and e1000e Linux drivers for Intel PRO/1000 adapters that allows a remote attacker to bypass packet filters and send manipulated packets.
- The updated misc-drivers VIB resolves an issue where if software FCoE drivers are used with NICs that support partial FCoE offload, the ESXi host might fail to boot on Cisco’s UCS rack-mount servers and stops responding with a backtrace similar to the following on the purple screen: