I love VMware! There is almost nothing cooler than using vmotion to migrate a guest OS to another host, with zero downtime.

I am in the process of upgrading all of my ESX hosts to 3.5 update 1, and I wanted to post some of my notes to remind me (and help others) with some of the bumps I had along the way.

Updating Virtual Center

• After upgrading Virtual Center to 2.5, 3/4 of hosts received the the following error while attempting to connected them to Virtual Center. “Failed to install the VirtualCenter agent service”
  • This would typically happen after the process was around 80% complete
  • To resolve this issue I used the following steps (Thanks to VMwarewolf for the insight)
    1. Login to ESX Server via ssh client as root user
    2. cd /tmp
    3. mkdir vmware-root
    4. Try re-connecting the host to Virtual Center
• One of my hosts had the following error. “Unable to access the specified host, it either does not exist, the server is not responding or there is a network problem”
  • This was resolved by starting the “mgmt-vmware” process, using the following steps
    1. Login to ESX server via ssh client as root user
    2. service mgmt-vmware start

References

VMwarewolf

This entry was posted on Monday, April 21st, 2008 at 4:00 pm and is filed under VMware. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.