Today I’ve updated my vSphere 5 hosts witch patch 1 released one week ago. Before I started the build number was VMware ESXi 5.0.0 469512:
To update the host I used PowerCLI, the code:
Get-VMHost esx02.vmpros.lan | Set-VMHost -State Maintenance
$DataStore = Get-VMHost esx02.vmpros.lan | Get-Datastore ESX02_VMFS01
Copy-DatastoreItem C:\vmpros\patch1\ $DataStore.DatastoreBrowserPath -Recurse
Get-VMHost esx02.vmpros.lan | Install-VMHostPatch -Hostpath "/vmfs/volumes/ESX02_VMFS01/patch1/metadata.zip"
The script will upload the content of the update-from-esxi5.0-5.0_update01.zip located at your local computer (which running PowerCLI) to the selected datastore. Then the update installation will start.
Update installation process:
WARNING: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Today VMware released ESXi 5.0 Update 1 with a download size of 564 mb
The update contains multiple bug/hotfixes bundled in Update 1, some more information:
This patch release contains the bug fixes for ESXi. For more information, see the KB articles for the individual bulletins.
For information about the issues fixed with the ESXi-5.0.0-20120301001s-standard image profile, see KB 2012673.
For information about the issues fixed with the ESXi-5.0.0-20120301001s-no-tools image profile, see KB 2012674.
For information about the issues fixed with the ESXi-5.0.0-20120302001-standard image profile, see KB 2012671.
For information about the issues fixed with the ESXi-5.0.0-20120302001-no-tools image profile, see KB 2012672.
Host Reboot Required: Yes
Virtual Machine Migration or Shutdown Required: Yes
The VMware Host Update Utility can’t “Upgrade Host” your system anymore since vSphere 4.1 with the download .zip files (in my case to upgrade to vSphere 4.1 Update 1 – update-from-esxi4.1-4.1_update01.zip ) …but you can still use the “Scan for Patches” option to apply the latest patches or even full Updates.
Today I updated my ESXi 4.1.0 server to Update 1 with the VMware Host Update Utility
Couple of weeks ago I asked on Twitter “Can anyone explain this #VMware storage view? MP status: Partial/No Redundancy.. Same cluster, same Dell Eql. SAN” .. now I was reading the release notes of vSphere 4.1 update 1 and there’s the fix…
Multipathing status for datastores that have fully redundant paths might be reported as having Partial/No Redundancy:
In the Storage View tab of vSphere Client, under certain conditions, volumes that are reported as “Partial/No Redundancy” actually have fully redundant paths. This type of misreporting occurs on iSCSI volumes with hardware initiators. VMware support called this a display bug
Cool, this issue is solved in vSphere 4.1 update 1
This release of VMware vCenter Server 4.1 Update 1 offers the following improvements:
- Additional Guest Operating System Customization Support: vCenter Server now supports customization of the following guest operating systems:
- Windows 7 SP1 (x32 and x64)
- Windows Server 2008 R2 SP1 (x32 and x64)
- RHEL 6.0 (x32 and x64)
- RHEL5.5 (x32 and x64)
- Additional vCenter Server Database Support: vCenter Server now supports the following databases:
- Microsoft SQL Server 2008 R2
- Microsoft SQL Server 2005 SP3
- Oracle 11g Standard/Enterprise Release 2, 22.214.171.124.0 or later, (x32 and x64)
- IBM DB2 9.7.2 Express C (x32 and x64)
- IBM DB2 9.7.2 Enterprise (x32 and x64)
For more information about using IBM DB2 – 9.7.2 database with vCenter Server 4.1 Update 1, see KB 1033201.
- Resolved Issues: In addition, this release delivers a number of bug fixes that have been documented in the Resolved Issues
When attempting to upgrade ESX 4.0 to ESX 4.0 Update 1 (U1), you may experience these symptoms:
- Upgrade operation may fail or hang and can result in an incomplete installation
- Upon reboot, the host that was being upgraded may be left in an inconsistent state and may display a purple diagnostic screen with the following error:
COS Panic: Int3 @ mp_register_ioapic
To download the newest (re-released) Update 1 check url:
Upgrading virtual hardware in ESX 4 may cause Windows 2008 disks to go offline.
Upgrading virtual hardware from version 4 to version 7 may cause Windows 2008 disks to go offline.
Creating a new virtual machine on hardware version 7 may cause Windows 2008 disks to go offline.
Note: The first disk (C: drive) is not affected. Any additional disks may be affected and show marked as Offline within Disk Management.
When attempting to upgrade ESX 4.0 to ESX 4.0 Update 1, you may experience the following symptoms:
- Update Manager (VUM) upgrade operation fails or times out at 33%.
- Upon reboot, the host that was being upgraded displays a purple diagnostic screen with the following error:
COS Panic: Int3 @ mp_register_ioapic
Customers using VMware vSphere 4 upgrading to Update 1 with 3rd party management agents running.
The following information provides highlights of some of the enhancements available in this release of VMware ESX:
VMware View 4.0 support – This release adds support for VMware View 4.0, a solution built specifically for delivering desktops as a managed service from the protocol to the platform.
Windows 7 and Windows 2008 R2 support –This release adds support for 32-bit and 64-bit versions of Windows 7 as well as 64-bit Windows 2008 R2 as guest OS platforms. In addition, the vSphere Client is now supported and can be installed on a Windows 7 platform. For a complete list of supported guest operating systems with this release, see the VMware Compatibility Guide.