Not sure if this has been experienced yet or not as I haven't read thru all the posts on the subject. Our dev infrastructure is as follows: 54 hosts, 300+ VM's, ESX 3.5U2, VC 2.5U1, all local host storage...no shared storage thus no vmotion, HA or anything else. Update Manager worked like a charm. Updated all hosts tonight. One interesting observation is the fact that updated hosts that were NOT rebooted and have NO VM's on them seem to be running at about 60% avg CPU load. Updated hosts that were NOT rebooted WITH VM's on them seem to be ok, but the host still running "hot". Updated hosts with or without VM's on them that DID get a reboot are fine. Don't know if this is because VC is running U1 and ESX running U2, and the perf charts getting flawed, or whether this is a problem with not rebooting the hosts. As soon as I reboot a updated host with no VM's (previously running at 60% CPU) it flattens out and runs fine, typically at about 2-3%. Thought the guru's at VMware might want to test this out. Object "0" on the CPU perf chart is at near 100% until I reboot. I assume this is the Service Console? We run 800Mb RAM on the SC. If you don't max the RAM on the SC, cold migration is painfully slow. Can't wait for shared storage (coming soon!)
John
PS. Suggestion for the next release... provide a way to kick off automatic startup of VM's from the Service Console as provisioned in the VM Startup/Shutdown config.
