Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)   View by Article ID

VMotion Disabled After ESX Server Patch Upgrade or Boot into Linux (1808)


I used a patch to upgrade my ESX Server. I booted into Linux, then booted back to vmnix. My VMotion is now disabled. What happened?


VMotion may become disabled after you use an ESX Server patch upgrade, or after you boot an ESX Server host into Linux mode and boot it back to vmnix mode while VirtualCenter is connected to the host.

There are two workarounds:

  • Disconnect the ESX Server host from VirtualCenter before applying the ESX Server patch upgrade or booting the ESX Server host in Linux mode.
  • Disable xinetd before upgrading or booting to the plain Linux mode, and enable xinetd after.

To disable xinetd:

  1. Turn off run level 3 of the xinetd daemon using chkconfig when you boot into Linux mode.
  2. Set xinetd to not start after booting.
    Set chkconfig level 3 xinetd to off.
    Boot into Linux mode.
  3. Set xinetd to start after booting.
    Set chkconfig level 3 xinetd to on.
    Boot into vmnix mode.
These workarounds apply to ESX Server versions 2.5.3, 2.5.1, 2.5, and 2.0.1.


RELNOTES; VC130; 61662; 1808; VC131

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 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? (4000 or fewer characters)
  • 0 Ratings