Can anybody help me with this error
"Unable to connect to the MKS: Internal error"
It's appear on my console, when i want to install my first Host.
I'm using Vmware ESX
Here you have other post
check this kb, might help: VMware Knowledge Base
When this happen ?
check firewall of vcenter if is disable to test. And check if all hosts and vcenter response to ping with FQDN.
other option: restart services of this host VMware.
service mgmt-vmware restart
service vmware-vpxa restart
I had a same issue, i am able to view VM console from vcenter server, i installed vsphere client on my desktop and i used same vcenter credentials, but i couldn't see VM console, showing same error unable to connect to the MKS: internal error.
finally i found the error is with DNS. Name resolution is not happening. Use nslookup command and check proper DNS connectivity, and also do following changes from this site http://www.gkhan.in/mks-internal-error-on-vmware-console/
Can you tell me if your root Ramdisk on ESXi appears to be full? From ESXi Shell or ssh run `vdf -h` Output should look similar to:
Ramdisk Size Used Available Use% Mounted on
root 32M 3M 28M 12% --
etc 28M 292K 27M 1% --
tmp 192M 28M 163M 14% --
hostdstats 834M 10M 823M 1% --
If your Use% is at 99-100% or Available space is 0 this can cause problems with multiple features, like vMotion (if your using vSphere). None of the VM KB Articles I have seen seem to mention this as a possibility for the mks internal error when attempting to console a VM.
I got this issue on vCenter 5.5/ESXi 5.5 and took me quite time googling with different solution with no luck. Luckily, I tried remove VM from inventory and add it back. Now it works. Thanks.
Met same issue on ESXi 6.0 after i added host to VC server. All VMs refused to open console with this error.
I tried to re-add first VM, and it works.
Then i shutdown second VM, open config and increase Video Memory from 4 MB up to 64MB. And it helps too. So it can be some bug with video resolution error.
Try the below steps
Do not panic, if you see the hosted virtual machines as “orphaned” in your vCenter. It will take some minutes till they are connected back as normal.
The restart of the Management Agents will not kill the virtual machines – they will continue to run.