VMware administrators may not have much day-to-day need for a virtual machine console, but when it is needed — it is needed.
You can think of the VM console like a remote KVM for virtual machines — similar to HP iLO on a physical machine. Most of the time there are more efficient network-based remote access techniques like RDP or SSH. However, there are some circumstances — like network misconfiguration — that absolutely require the use of a remote console.
Have you ever wondered what would happen if you were connected to a VM console while it automatically migrated with VMotion to another physical host? If you are a long-time VMware admin, you would probably expect things to keep on working. And that is exactly right — the console connection is seamlessly transferred to the new VMware ESX host. This behavior is especially important when VMware DRS is dynamically moving virtual machines to optimize cluster resources.
Need to check the network settings of a VM? No problem — you may not even notice if that VM migrates to another host while you are connected.
Here is a quick video of the situation in action:
Does Microsoft Hyper-V and System Center Virtual Machine Manager 2008 handle this scenario the same way? Not exactly.