vSphere 4u1 - any issues?

[AntonVZhbankov]

Please post any issues with 4u1 here

---

MCSA, MCTS, VCP, VMware vExpert '2009

http://blog.vadmin.ru

[BHLSupport]

I have an ESXi host thats 4.0.0 - build 193498 and when I try a patch it says its uptodate.

I try an upgrade with the zip and it says to use the patch feature and won't let me upgrade.

I'm using the latest host update package.

[HenrikElm]

Right. If you already are on v7 you are all set.

/H

[HenrikElm]

Do you see the U1 patch in your patch inventory? It may not be downloaded yet. Default is once a week I think.. I always set it to daily after install..

/H

[BHLSupport]

I'm using the host update tool and can't see the patch inventory in that. We don't have vcenter. I've manually upgraded our other machine with a fresh install, but would like to update this other one rather than have to re-install it.

[HenrikElm]

Aha. Never used that one.. Only did it with UM..

/H

[rewalt]

I have not successfully upgraded vmware tools on any VM migrated to vSphere 4, Update 1. Every single attempt at upgrading tools hangs when it tries to update the vmxnet drivers. I have to kill all of the VMWare Tools processes and msiexec. Many times, I lose network connectivity completely. Sometimes a reboot of the VM will fix it, sometimes I have to remove the NIC completely, add a new NIC with vmxnet2 or 3, reconfigure the IP info. In no case has the VMWare Tools upgrade succeeded, even after manipulating the NICs. I have a case open with VMWare, but have not heard back yet. I might understand if this was an isolated case, but it's not. It is every single VM I have tried to upgrade tools on under Update 1.

[dougdavis22]

What version did you upgrade from? Was it a 3.5 to vSphere 4 U1 or vSphere 4 to vSphere 4 U1?

[rewalt]

I upgraded from vSphere 4 , 181792 or 193498

VM Hardware was upgraded to version 7 during vSphere 4 upgrade a couple of months ago, after the Tools upgrade, per recomendations. Have not had any issues until the Update 1 upgrade. So far, all the VMs I have tried the upgrade on are WS2K3 SP2. Either Std. or R2 Std. Even after I get the NIC working again, the Tools upgrade hangs the VM and never completes. Does not matter if it is E1000, vmxnet 2 or vmxnet 3.

My worry is, we have been running ESX since the 1.5 days. None of these VMs are that old, but most were built either in the 2.5 or 3.x days. I have not tried upgrading tools in a VM built fresh on vSphere 4. I'll try that on Tuesday.

[mikannet]

Hi!

I have problem after upgrading vCenter to 4u1 from 4. I have some ESXi 4.0u1(208167) hosts wish I upgraded from 4.0 before I upgraded the the vCenter and now I can't reconnect a host. I read an KB (1014554) about some kind of memory problem. Another host had the same symptom but after turning of a vm I could reconnect it. I have turned of some VMs on the failing host, but it doesn't help. It's possible to connect to the failing host with the vSphere client and it's memory usage of 14GB of 32GB, so it shouldn't be an out of memory problem.

In the exported system logs I found the following lines:

2009-12-02 18:03:41: Logging to /var/log/vmware/vpx-iupgrade.log

2009-12-02 18:03:41: Removing /opt/LGTOaam leftovers if any

2009-12-02 18:03:41: extracting vpx-upgrade-installer/VMware-vpx-eesx-1-linux-208111.tar.gz...

2009-12-02 18:03:41: exec rm -f /tmp/vmware-root/ha-agentmgr/upgrade

2009-12-02 18:03:41: status = 0

2009-12-02 18:03:41: exec cd vpx-upgrade-installer

2009-12-02 18:03:41: status = 0

2009-12-02 18:03:41: exec gunzip VMware-vpx-eesx-1-linux-208111.tar.gz

2009-12-02 18:03:42: status = 0

2009-12-02 18:03:42: exec mv VMware-vpx-eesx-1-linux-208111.tar vpxa.tar

2009-12-02 18:03:42: status = 0

2009-12-02 18:03:42: exec /sbin/vmtar -c vpxa.tar -o vpxa.vmtar

2009-12-02 18:03:42: status = 0

2009-12-02 18:03:42: exec rm -f vpxa.tar

2009-12-02 18:03:42: status = 0

2009-12-02 18:03:42: exec gzip vpxa.vmtar

2009-12-02 18:03:49: status = 0

2009-12-02 18:03:49: exec mv vpxa.vmtar.gz vpxa.vgz

2009-12-02 18:03:49: status = 0

2009-12-02 18:03:49: exec rm -f vpxa.vmtar.gz

2009-12-02 18:03:49: status = 0

2009-12-02 18:03:49: exec /sbin/BootModuleConfig.sh --add=vpxa.vgz --verbose

Acquiring lock /tmp/bootbank.lck

Copying vpxa.vgz to /bootbank/vpxa.vgz

Editing /bootbank/boot.cfg to add module vpxa.vgz

2009-12-02 18:03:49: status = 0

2009-12-02 18:03:49: exec /sbin/vmkramdisk vpxa.vgz

Failed to mount archive: Out of memory

2009-12-02 18:03:50: status = 12

2009-12-02 18:03:50: exec rm -f vpxa.vgz

2009-12-02 18:03:50: status = 0

2009-12-02 18:03:50: exec rm -f VMware-vpx-eesx-1-linux-208111.tar.gz

2009-12-02 18:03:50: status = 0

2009-12-02 18:03:50: Build: 208167 Installing tarball..

2009-12-02 18:03:50: All done! Status: 201

Any clues? I have some running VMs on the host so I don't want to restart it...

Mikael Sennerholm

[BrunoP]

Just updated vSphere server 4 to Update1 and updated Update manager & Converter. Works as it was expected.

Created a new upgrade baseline and tried to update an ESX4.0.0. 175625 .... Bummer!

"Upgrade is not supported from host version 175625 to release version 4.0.0 Update 1 Build 208167"

Why??? It looks like a normal 'upgrade' to me.

I have the exact same problem. Even created a separate thread on this problem () but I got no answer so far

[DSeaman]

VMware support has confirmed the VUM 4.0 U1 SSL certificate workaround on my blog is the official workaround until update 2 comes out, which should provide a real fix to the solution.

http://derek858.blogspot.com/2009/11/vcenter-update-manager-40-ssl.html