Unable to connect to the MKS: Internal error after cloning
or
vMotion fails with the error: A general system error occurred
This issue occurred for me after cloning a server in vSphere 5.5. Once the vm was powered on and the new configuration was applied I could not connect to the vm console. I received the "Unable to connect to the mks: internal error". No specific error message was given but I found a few post that lead me in the right direction.
After a failed vMotion attempt which gave me the "vMotion failed with the error: A general system error occurred" I found a fix that worked for me. I was able to access the server and save time from rebuilding another server from scratch. I hope this helps you too.
SIMPLE FIX
Remove the vm from inventory then register the .vmx file from the original data store.
-
In the vSphere 5.5 client;
-
Select "Hosts and Clusters" or VM's and Templates"
-
Select the affected vm then select "Summary"
-
Review the summary page at "RELATED OBJECTS" >>> STORAGE and find out what data store the vm files are located
-
Right click the vm or select "Actions"and select "Shut Down Guest OS"
-
Wait for the vm to power off
-
Right click the vm and select "All vCenter Actions" >>> "Remove from Inventory" and follow the prompts
-
After the vm has been "Removed from Inventory" in the vSphere Client select "Home" then "Storage"
-
Select the vm's database, right click then select "Register VM..."
-
Slect the vm's folder and the wizard wil lautomatically select the .vmx file. Click OK.
-
Go back to "VM's and Templates" and you rvm will now be visable.
-
Connect to the vm console.
