The virtual machine could not be started because the hypervisor is not running.
Where was I when they covered the Hypervisor? Apparently I my mind was wondering but, I looked here at social.technet.microsoft.com and see an explanation of this hypervisor thing. Seems it’s a low-level setting made available in the BIOS.
On the Dell, I press f2 as the machine boots and navigate down to CPU Info where there’s a Virtualization Technology setting set to…
yup, DISABLED.
I used the right arrow to change it to ENABLED and press escape, save and exit.
The machine reboots. But the article says do a “Cold” reboot which, to me, means unplug the damm thing. I shut down, pull the cord and count to 20, plug it back in and hit the on button.
After it starts, I open the Hyper-V manager, select the VM, right click and select Start. It seems to be working. It’s running; I click Connect, It’s applying settings.
Press CRTL + ALT + DELETE to log on.
I get an EULA and click OK. There’s a Warm Up program that bangs on all the pages and pre-compiles them.
I move away from the VM to my host and browse to http://intranet.contoso.com and in a moment… DORKS!
It’s not really an install but it’s running. Now, I wonder how I can get my dual monitors to work with my VM on my server that I’ve remoted to… It’s good to have goals.
hth
-robot
Tags: