Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
VMotion from ESX Server 3.5 Hosts to ESX Server 3.0.x Hosts Causes the Console Sessions of the Migrated Virtual Machines to Become Blank (1003038)
Details
Solution
Workaround 1
-
Revert the virtual machine to ESX Server 3.5.
-
Locate the virtual machine's .vmx file as described below.
-
From the service console, change to the directory containing the .vmx file.
#cd /vmfs/volumes/<datastore name>/<directory path>/ - Change the virtual machine's .vmx file permission to -rwxr-xr-x.
#chmod 755 <vmx file name> -
Perform the VMotion again. You do not need to restart the virtual machine.
Workaround 2
-
Power off the virtual machine from ESX Server 3.0.x.
-
Locate the virtual machine's .vmx file as described below.
-
From the service console, change to the directory containing the .vmx file.
#cd /vmfs/volumes/<datastore name>/<directory path>/ -
Change the virtual machine's .vmx file permission to -rwxr-xr-x .
#chmod 755 <vmx file name> -
Power on the virtual machine.
To locate the virtual machine's .vmx file:
-
In the VI Client inventory, select the virtual machine and click the Summary tab.
-
Click Edit Settings.
-
Click the Options tab and select General Options. The Virtual Machine Configuration File text box displays the location of the .vmx file. in the following format:
[<datastore name>] <directory path>/<configuration_file>.vmx
Keywords
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.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

