VM running on new Hyper-V host failing to start...

[Rawns]

We've just enabled Hyper-V on a Windows Server 2016 host. After creating a new VM and trying to boot it up, it hangs on boot with a status of "Starting (10%)" then finally errors out with the below:

 

 

Alas the error gives me nothing to go on, and the only other error I can find is in the Hyper-V-Worker event log: "Virtual Machine Worker Process initialization has timed out, and will terminate."

 

I've rebooted, removed hyper-v, re-installed it all to no avail. Any suggestions as I (and Google) have drawn a blank!

[Steve21]

Few things to try would be checking the bios has all the threading settings enabled etc, sometimes they have multiple ones rather than just VT etc.

 

Where's the storage for the VM? If it's not local have you checked permissions for the services?

 

Remove any NIC if you added one as that'd remove any faults if it's upset with a vswitch

 

Steve

[pantscat]

Have you got AV on the host? Check it's not scanning the VMs and locking them?

[Rawns]

Thanks for the suggestions guys, appreciated.

 

I've removed the virtual switch - same error.

The VHDX files are being stored on the local drive directly on the host and permissions to them have been checked.

AV is installed but rules are in place to exclude the Hyper-V storage locations.

 

Guess a BIOS check will be required which will require a site visit...

[Steve21]

I take it your VM has the right generation too? Not using G1/2 with the wrong OS etc?

 

I don't think it'll show as much as the bios, but if you run systeminfo in cmd it should show on the last few lines some of the settings and whether it's detected any missing.

 

Steve

[Rawns]

Thanks @Steve21, yep, using G2 to create a Server 2016 guest on the Server 2016 host. I did try a G1 too but exact same error.

 

Ran systeminfo and did get the following on Hyper-V:

 

Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.

[round2it]

sounds dumb but I have one that will not start unless I do a gpupdate /force on the host

 

give it a go

 

not had time to look into why but it works for me

 

this only happens on 2012 or higher server version for me 2008 is fine

Edited July 23, 2018 by round2it

[Rawns]

Server checked on site. All Virtualisation options in the BIOS are enabled.

[Steve21]

What happens if you just do a blank VM without any isos etc attached? Same thing or does that load?

 

Steve

[Rawns]

This is actually for a new (blank) VM. With or without the Server 2016 ISO mounted in the VM, it's the same thing: "Starting (10%)" then the above error. The server has not had any other VM's set up yet, this is actually the first one.

 

As a test, I have uninstalled Hyper-V again, rebooted and installed Oracle VirtualBox which is working perfectly.

[round2it]

is the host domain joined?

[Rawns]

Yes it is. It's the DC in fact.

[Davit2005]

Yes it is. It's the DC in fact.

 

I didn't think Installing Hyper-V role on a Domain Controller was supported/recomended.

Edited July 23, 2018 by Davit2005

[sted]

I didn't think Installing Hyper-V role on a Domain Controller was supported.

 

iirc it works but isnt supported

 

try disabling checkpoints/auto checkpoints theyve caused me issues before

[gjefferies]

Have a look in event viewer there are specific Hyper-v event logs if you drill down and these normally tell you why a VM won't start.

https://blogs.msdn.microsoft.com/virtual_pc_guy/2009/02/03/looking-at-the-hyper-v-event-log/

[Rawns]

Have a look in event viewer there are specific Hyper-v event logs if you drill down and these normally tell you why a VM won't start.

https://blogs.msdn.microsoft.com/virtual_pc_guy/2009/02/03/looking-at-the-hyper-v-event-log/

 

Thanks, but I've already been through these. It was under here (the Hyper-V-Worker event log) reporting "Virtual Machine Worker Process initialization has timed out, and will terminate."

 

That is the only error under all the Hyper-V specific logs.

[HTCPCP]

Not an ideal solution, but have you removed the Hyper-V role, and re-added it? I had a temperamental server that required that treatment a couple of times when we had problems with a faulting UPS.