Virtual Center Upgrade

I recently upgraded from Virtual Center 2.0.1 to 2.0.2. Now a week later have found the first real issue while attempting to import a VM from VMWare Converter. The import would hang at 1%, if you viewed the job in Virtual Center it would show creating the VM. If you connected directly to the ESX host with the VI client, you would see the VM had completed creation. Basically the communication looked like it would get to the ESX host but not come back to Virtual Center. I was able to run convert directly to the ESX host and start the VM. But none of this translated into Virtual Center. To solve this we had to restart the management services. Due to some bugs in the hostd service you have to kill the process rather than restarting it. There is a known issue in some versions of ESX that when you restart the hostd process (service vmware-hostd restart) any VMs set to shutdown on a reboot the host, may shut down. So first we have to find the pid's of the hostd services. [root@xxxxx24 root]# ps -auxwww | grep hostd root 1933 0.0 0.0 4260 4 ? S Jan30 0:00 /bin/sh /usr/bin/vmware-watchdog -s hostd -u 60 -q 5 -c /usr/sbin/hostd-support /usr/sbin/vmware-hostd -u root 1939 0.4 11.5 58636 31060 ? S Jan30 462:02 /usr/lib/vmware/hostd/vmware-hostd /etc/vmware/hostd/config.xml -u root 21729 0.0 0.2 3696 664 pts/1 S 16:04 0:00 grep hostd [root@xxxxx24 root]# Then kill the two hostd services. [root@xxxxx24 root]# kill -9 1933 1939 Now we can start mgmt-vmware and restart the vpxa service [root@xxxxxx24 root]# service mgmt-vmware start Starting VMware ESX Server Management services: VMware ESX Server Host Agent (background) [ OK ] Availability report startup (background) [ OK ] [root@ivpesx24 root]# service vmware-vpxa restart Stopping vmware-vpxa: [ OK ] Starting vmware-vpxa: [ OK ] [root@xxxxxx24 root]# This causes the host to disconnect from Virtual Center for a bit and when it reconnects everything synced up correctly. One caveat to this. In ESX 3.5, there are some logfiles of the pids stored in /var/run that may need to be cleaned out before starting the mgmt-vmware service.