Prior to installing vCenter, I had been using vSphere (local thick client) and was able to authenticate to the ESXi host and click "Open Console" to control guest VMs.
After installing a vCenter appliance server, I'm unable to view the console on some guest VMs, either from vSphere local client or the vSphere web client hosted on the vCenter server.
Attempting to use either console view I receive the following error:
Unable to connect to the MKS
Since I was able to remote console through the vSphere local client prior to installing vCenter, I suspect that vCenter somehow alters the way the vSphere local client/ESXi host would remote console to guest VMs.
I am certain there have been no changes to the VMs I am unable to access.
tl;dr; How does installation of vCenter alter ESXi Host console access to guest VMs?
Answer
I was able to successfully "open console" (view console) on my VMs after completely reinstalling ESXi, and re-adding the VMs on the datastore.
This doesn't completely answer the question of what vCenter installation does to an existing ESXi installation that prevents console access, but does provide a workaround.
No comments:
Post a Comment