VMware vSphere 5.0 Update 1 : Released.

Great News! VMware vSphere 5.0 Update 1 has been released.

Download it now!

Whats new in update 1?

What’s New

The following information describes some of the enhancements available in this release of VMware ESXi:

  • Support for new processors – ESXi 5.0 Update 1 supports new AMD and Intel Processors. See the VMware Compatibility Guide for details.
  • Support for additional guest operating systems – ESXi 5.0 Update 1 adds support for Mac OS X Server Lion 10.7.2 and 10.7.3.
  • New or upgraded device drivers – ESXi 5.0 Update 1 adds support for Native Storage Drivers for Intel C600 series chipset and upgrades LSI MegaRAID SAS driver to version 5.34.

Resolved Issues – In addition, this release delivers a number of bug fixes that have been documented in the Resolved Issues section.” 

Full VMware ESXi 5.0 Update 1 Release Notes

Make sure to check out the Resolved Issues 

a ton interesting resolved issues….

 

 “vCenter SRM failover fails due to virtual machine misconfiguration

If a virtual machine configured in the recovery plan of VMware vCenter Site Recovery Manager (SRM) uses one or more Raw Device Mapping (RDM) files, and the pointer file is in a folder other than the home folder, VMware vCenter SRM failover process fails. SRM logs contains entries similar to:

[fusion_builder_container hundred_percent="yes" overflow="visible"][fusion_builder_row][fusion_builder_column type="1_1" background_position="left top" background_color="" border_size="" border_color="" border_style="solid" spacing="yes" background_image="" background_repeat="no-repeat" padding="" margin_top="0px" margin_bottom="0px" class="" id="" animation_type="" animation_speed="0.3" animation_direction="left" hide_on_mobile="no" center_content="no" min_height="none"][2011-05-05 09:26:35.756 22348 verbose 'RSVm-49592-Task'] Error set to (vim.fault.InvalidDeviceBacking)

This issue is resolved in this release.”

 “Using the bundled Emulex BE2/BE2 NICs (be2net driver)
When using vSphere 5.0 with Emulex BE2/BE3 NICs (be2net driver) in a HP FlexFabric/Flex-10 or IBM Virtual Fabric Adapter (VFA) environment, connectivity may not work properly on Windows virtual machines or the server when VLANs are configured.

This issue is resolved in this release.”

“DHCP server runs out of IP addresses
An issue in the DHCP client might cause the DHCP client to send DHCPRELEASE messages using the broadcast MAC address of the server. However, the release messages might be dropped by an intermediate DHCP proxy router. Eventually the DHCP server runs out of IP addresses.

This issue is resolved in this release. Now the release messages are sent using unicast addresses.esxcfg-nics -l command displays the description of pseudo-device as “Unknown Unknown”

This issue is resolved in this release.–>  “

ESXi host might fail with a purple screen when a virtual machine connected to VMXNET 2 vNIC is powered on
The purple diagnostic screen displays an error message similar to the following:

0x412261b07ef8:[0x41803b730cf4][email protected]#nover+0x2b stack: 0x412261b0
0x412261b07f48:[0x41803b76669f][email protected]#nover+0xf6 stack: 0x412261b07f98

An error message similar to the following is written to VMkernel.log:

WARNING: Vmxnet2: 5720: failed to enable port 0x2000069 on vSwitch1: Limit exceeded^[[0m

This issue is resolved in this release.”

Hostd might stop responding during Network File Copies
In rare instances, hostd might stop responding during a Network File Copy operation. This is usually triggered by environmental networking issues. Hostd logs messages similar to the following to /var/log/vmware/hostd in rapid succession (several times per millisecond) resulting in high CPU usage (80-100%):

[2010-12-14 13:15:39.238 F5135B90 warning 'Libs'] [NFC ERROR] NfcFssrvrRecv: failed with code = 9
[2010-12-14 13:15:39.238 F5135B90 info 'Libs'] NfcNetTcpRead: timed out waiting for data

These messages are logged until you restart hostd.

This issue is resolved in this release.”

 “Corrupt VMFS volume causes VMFS heap memory exhaustion
When an ESXi host encounters a corrupt VMFS volume, VMFS driver might leak memory causing VMFS heap exhaustion. This stops all VMFS operations causing orphaned virtual machines and missing datastores. vMotion operations might not work and attempts to start new virtual machines might fail with errors about missing files and memory exhaustion. This issue might affect all ESXi hosts that share the corrupt LUN and have running virtual machines on that LUN. This issue is resolved in this release”

 “vSphere Storage APIs for Array Integration (VAAI) sends XCOPY commands to the source device, in violation of VAAI specification
XCOPY commands that VAAI sends to the source storage device might fail. By default, XCOPY commands should be sent to the destination storage device in accordance with VAAI specification.

This issue is resolved in this release.”

 “Performance of Windows 2000 Terminal Servers degrade after upgrading from ESXi 4.x
After you upgrade to ESXi 5.0 from ESXi 4.x, Windows 2000 Terminal Servers might perform poorly. The consoles of these virtual machines might stop responding and their CPU usage shows a constant 100%.

This issue is resolved in this release.”

And those are just a few.

 All qotes taken from http://www.vmware.com/support/vsphere5/doc/vsp_esxi50_u1_rel_notes.html#whatsnew

With the fixes, I would think we would all want to rush out and upgrade.

Roger L..[/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]

Written by Roger Lund

VMware and Storage crazy man, vExpert, MN VMUG leader