How to Configure Hyper-V v3 & Windows Server 2012 "8" 8250 nested inside ESXi 5.0

Here is an update to the previous blog http://goo.gl/II3gf regarding nested VMs inside ESX 5.0, I wanted to give an update on how to install the Beta of Windows Server 2012 “8” 8250 build and more importantly how to enable Hyper-V role inside the nested VM.
For the majority of the installation of this build the steps remain the same as with Windows 2008 R2 but with a couple of additions.
First make sure you are either runnning ESX 5.0 Update 1 or atleast have patch ESXi500-201112001 http://goo.gl/oWZXV installed against ESX 5.0
1. You need to enable hardware virtualization by modifying the etc/vmware/config file. Enable SSH via tech support mode and putty to the ESX5i server
2. Once connected with putty  :
# echo ‘vhv.allow = “TRUE” ‘ >> /etc/vmware/config
3. Next create your Virtual Machine hardware, I personally used hardware version 8 to make things easier with configuration.
4. Before you get to booting up the VM and installing Hyper-V you need to add three lines the virtual machines config file .vmx
You can either add these via the vSphere Client in the settings of the virtual machine > Configuration Parameters, or doing it from command-line
To add them using command-line move back in SSH > change into the directory where you Hyper-V VM is installed
For example config file where my VM is located is called Hyper-V.vmx. Type the following commands:
# echo ‘monitor.virtual_exec = “hardware” ‘ >> Hyper-V.vmx
# echo ‘hypervisor.cpuid.v0 = “FALSE” ‘ >> Hyper-V.vmx
# echo ‘mce.enable = “FALSE” ‘ >> Hyper-V.vmx
5. Next there are a couple of changes to be made with the CPU configuration.
in the VM settings > Options > CPU/MMU Virtualization make sure you select the option to pass the Intel EPT feature.

6. Next move to the Options area > CPUID Mask click on Advanced

Add the following CPU mask Level ECX: —- —- —- —- —- —- –H- —-

8. Finally you are now ready to install Beta Windows 2012 “8” and enable the Hyper-V role.
Additional Notes: Watch out for blank screens once VMtools are installed, if this happens then enable 3D support for your Video card in the VM settings  – See VMware KB http://kb.vmware.com/kb/2006859
Also when configuring your VM use the E1000 network driver type and not the VMXNET3 as this driver does not work.
Once the Windows server is installed, just enable the Hyper-V role and your all set to start exploring the world of Hyper-V v3.

Please follow and like us:

Installing Windows Server "8" Beta on VMware Workstation 8, It works, well sort of !!!

I had time this morning (while waiting for a problem to be fixed) to test the Beta Build of Windows Server “8” that dropped yesterday, initially I was having issues installing VMtools on a custom “Windows 2008 R2 x64” VM set at hardware compatability 8 and initially gave it from 2-4gb of memory, VMtools had issues installing TP drivers, VMCI and also SVGA drivers did not install, they actually caused a complete black screen which was similar to the Windows 8 Customer Preview MSFT released last year which SVGA issues were related to memory allocation issues.
I destoyed the VM and recreated a custom “Windows 2008 R2 x64” version 7 VM with 1gb Ram and installed the Windows image with no issues, VMtools presented no problems either, so I then shutdown the VM and reset the memory to 2gb and powered back up, there were no issues, all is working fine.
Next is to try and see if the same is true for ESXi 5.0, I especially want to see if I can get Hyper-V working the same as I did for Windows 2008 R2.
Update will follow…

Please follow and like us: