HyperV new VM will not start

isthistaken 1 Reputation point
2022-11-18T15:16:24.957+00:00

Hi all.

Server 2019 core with HyperV role
4 VMs running fine
96GB free RAM
2. 8TB free storage

Create a new VM which will not start, gets to 10% then errors with unable to change state.
VMMS event id 15130
HyperV worker event id 3062.
No other errors
No recent updates
No AV running

This server is a production server, it will not be restarted or the HyperV role reinstalled/reconfigured

What has been tried:
Creating VM and VHDx in new directory with Everybody Full Access
Restarting VMMS service
Remove network, remove DVD
Lots of googling

Any help appreciated.

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,054 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jonathon Kindred 401 Reputation points
    2022-11-18T15:35:06.187+00:00

    I would move through this list and make sure you've double checked configurations:

    1. Storage Failure - Check your storage, make sure it is configured and spun up correctly. Is storage readable by your Hyper-V instance?
    2. Is there enough memory allocated for the VM to start up. Are the other VM's essentially taking up all the RAM and storage.
    3. Incorrect network configuration - Is it contained in the correct VNET or does it have any NSGs/Policies that are blocking it from starting it up.

    It might help to reinstall the HyperV role, I understand you've mentioned that it won't be reconfigured/reinstalled but in a lot of scenarios this actually fixes the error, this link will take you through the installation guide in case you need it: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server

    Although you are not receiving an access denied error, it might be that there is something setup in the VM that shouldn't be but the error message you are receiving is a result of that. check this guide from Microsoft: https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/hyper-v-virtual-machine-not-start-0x80070005

    Again, double/triple check the policies, roles, and NSGs to rule out any explicit deny errors. Also check if you have spun it up in a different location to the rest of the VM's sometimes this can happen by mistake especially if you are deploying VMs manually outside of Terraform/ARM.