Showing posts with label Nested Virtualization. Show all posts
Showing posts with label Nested Virtualization. Show all posts

Wednesday, 28 November 2018

VMware ESXi 6.7 fails to connect VM web console with "You have reached the maximum number of connected consoles: 40. Please contact your administrator."

VMware ESXi 6.7 fails to connect VM web console with "You have reached the maximum number of connected consoles: 40. Please contact your administrator."

I tried disconnecting all the open session to vCenter which never helped. 

I also tried to restarting the VM which also never helped. I managed to narrow it down to being a problem with the VM and not vCenter, because the web console was working for other VM's. 

The fix for me was to shutdown the VM, remove the VM from the vCenter inventory (don't delete from disk), then Register it from the datastore again. Then the error disappeared. 

Tuesday, 17 June 2014

Using VMware Workstation 10 to Run Hyper-V 2012 R2 Nested Instances

In order for this to work correctly there is a small hack that must be put in place. For every Virtual Machine created under VMware Workstation there is a (.vmx) file which contains configuration settings for the guest machine. This files is stored along with the virtual hard disk files by default.

You can open the (.vmx) file with Notepad and edit it freely provided the Virtual Machine is powered off. The following lines must be added to the (.vmx) file;
 
hypervisor.cpuid.v0 = "FALSE"
mce.enable = "True"



 

Save the changes to the (.vmx) file.

You must also edit the Processors setting on the VM, set the Preferred Mode to Automatic and ensure Virtualize Intel VT-x/EPT or AMD-V/RVI and Virtualize CPU performance counters are ticked.

 


 

Now start the machine and you will now be able to run "nested" Virtual Machines inside Hyper-V. The hypervisor.cpuid.v0 = "FALSE" line tricks the guest operating system into thinking it’s not running as a virtual instance.