Planet Malaysia Blog

VMware Inc. released VMware ESX 3.5 Update 1 on 10 April 2008 and I made time to apply on my ESX development box today.

1. Download latest VMware ESX 3.5.1 from VMware web site.

2. Unzip the ‘upgrade-from-esx3.5-3.5.0_Update_1-82663‘ into one of my Apache web server.

3. VMotion existing VMware guest to another VMware Host and Enter Maintenance Mode.

4. Run

esxcfg-firewall -allowOutgoing
esxupdate -r http://webserver/esxupdate/upgrade-from-esx3.5-3.5.0_
Update_1-82663/ update
esxcfg-firewall -blockOutgoing

OR
you can use Update Manager by run update signature from scheduled task and apply critical & non-critical baseline for the particular ESX host from Update Manager.

5. Once the update completed, you can check using command
#cat /proc/vmware/version
VMware ESX Server 3.5.0 [Releasebuild-82663], built on Mar 18 2008
vmkernel build: 82663, vmkcall: 45.0 driver interface: 8.0 kernel: 61.0
vmnixmod build: 82663, interface: 2850028248vmksysinfo version: ffa98bbe1556b94447ee4055935ecc6f
Loadable module version info:vmkernelID: 0×45f7df95
vmklinux build 82663: Built on: Mar 18 2008
megaraid_sas build 82663: 00.00.03.09
bnx2 build 82663: 1.5.10b
lvmdriver build 82663: 3.16, built on: Mar 18 2008
vmfs3 build 82663: 4.31, built on: Mar 18 2008
etherswitch build Built on: Mar 18 2008
shaper build Built on: Mar 18 2008
tcpip build 82663: Built on: Mar 18 2008
cosShadow build 82663: Built on: Mar 18 2008
migration build 82663: protocol: 5.0
vmk interface: 3.0nfsclient build 82663: Built on: Mar 18 008
deltadisk build 82663: Built on: Mar 18 2008vmfs2 build 82663: 2.52, built on: Mar 18 2008
OR
#vmware -v"VMware ESX Server 3.5.0 build-82663
OR
#esxupdate -l query
Installed software bundles:
------ Name ------ --- Install Date --- --- Summary ---
3.5.0-64607 18:29:18 03/18/08 Full bundle of ESX 3.5.0-64607
ESX350-200802415-SG 13:02:05 04/07/08 Security Update to Samba Packages.
ESX350-200802303-SG 15:26:39 04/07/08 util-linux security update
ESX350-200802305-SG 15:28:22 04/07/08 openssl security update
ESX350-200802405-BG 16:56:04 04/07/08 Update to MegaRAID SCSI Driver.
ESX350-200802304-SG 17:16:09 04/07/08 perl security update
ESX350-200802306-BG 17:16:56 04/07/08 tzdata update
ESX350-200802408-SG 17:18:30 04/07/08 Security Updates to the Python Package .
ESX350-200803209-UG 12:29:31 04/14/08 Update to the ESX Server Service Console le
ESX350-Update01 12:29:31 04/14/08 ESX Server 3.5.0 Update 1
ESX350-200803201-UG 12:29:31 04/14/08 Upgrade the Openwsman Protocol Adapter
ESX350-200803208-UG 12:29:31 04/14/08 Update to the esxupdate utility
ESX350-200803204-UG 12:29:31 04/14/08 Update the VMware mptscsi_2xx driver
ESX350-200803207-UG 12:29:31 04/14/08 Update the VMware qla2300-v707 driver
ESX350-200803211-UG 12:29:31 04/14/08 Update to vmkernel and vmnix
ESX350-200803216-UG 12:29:31 04/14/08 Update to VMware-esx-drivers-net-tg3
ESX350-200803203-UG 12:29:31 04/14/08 Update to VMware-cim-esx
ESX350-200803213-UG 12:29:31 04/14/08 Driver Versioning Method Changes
ESX350-200803217-UG 12:29:31 04/14/08 Update to the mgmt-vmware Service
ESX350-200803202-UG 12:29:31 04/14/08 Update to VMware-esx-tools, others
ESX350-200803215-UG 12:29:31 04/14/08 Update to Virtual Infrastructure Client
ESX350-200803205-UG 12:29:31 04/14/08 Update to VMware-esx-drivers-net-ixgbe
ESX350-200803206-UG 12:29:31 04/14/08 Update the VMware lpfc_elx_v740 driver
ESX350-200803212-UG 12:29:31 04/14/08 Update VMware qla4010/qla4022 drivers
ESX350-200803210-UG 12:29:31 04/14/08 Update to VMware-esx-drivers-net-bnx2
ESX350-200803214-UG 12:29:31 04/14/08 Update to Third Party Code LibrariesNew packages:
VMware-vpxa-2.5.0-64192

6. Exit maintenance mode

Basically the whole upgrade process take about an hour to finish and so far so good.

Beside this, I found a VMware server problem that consist more than 64Gb pyhsical memory few weeks back. Said you have 128GB pyhsical memory in your ESX host but somehow the ESX host reserved > 60GB for System Memory  which show in Virtual Infrstructure Client. What? After check with VMware support and solution:

1.Log in to VirtualCenter as an administrator using the Virtual Infrastructure Client.
2.From the Inventory click the ESX Server.
3.Click the Configuration tab.
4.Click Advanced Settings link.
5.Navigate to VMKernel>Boot.
6.Deselect the option for VMkernel.Boot.force36BitMTRRMask.
Reboot the ESX Server host for the change to take effect. Once rebooted, I can see my ESX System Memory drop to around 8.xGB. Solved.

Lastly, VMware Server 1.0.5 is available for download now.

Possibly Related Posts:

• SSH Remote Access Authentication Tips
• Your Password is Disclose
• Ask Google Engineer a Questions
• Set a Good Password Policy On SuSE Linux
• How To Check Which Port Is Listern or Open on Linux