Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

Upgrading from VMFS-2 to VMFS-3 Can Make VI Client on ESX Server System Unresponsive

Details

Why did the VI Client on my ESX Server system become unresponsive during an upgrade from VMFS-2 to VMFS-3?

Solution

Note: Before you begin please refer to KB1003490 for important information on restarting the mgmt-vmware service.

 
If two VMFS-2 partitions are upgraded simultaneously or close to one another, the host agent on the ESX Server system might sometimes deadlock and cause the VI Client to become unresponsive.

To work around this issue, always upgrade one VMFS-2 partition at a time. You should wait at least ten seconds before upgrading the next partition. If the server becomes unresponsive, log in to the service console and restart the host agent using the /etc/init.d/mgmt-vmware restart command.

Other options for this command are stop and start.

If hostd fails to restart for any reason, use killall -9 vmware-hostd to kill it. A watchdog script automatically restarts it.
 
Note: This issue is resolved in ESX Server 3.0.1.

Keywords

2233

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 2233
  • Updated: Aug 14, 2009
  • Products:
    VMware ESX
  • Product Versions:
    VMware ESX 3.0.x