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

Although virtual machine console sessions become blank, virtual machine applications and network connectivity are not affected.

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

virtual machine console; console; VirtualCenter; ESX Server; migration; host; VMotion;

Actions

Products:
VMware ESX
Product Versions:
VMware ESX 3.0.x
VMware ESX 3.5.x
VMware ESXi 3.5.x Embedded
VMware ESXi 3.5.x Installable
VMware VirtualCenter 2.5.x

Knowledge Base

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)