Tazatel
Hyper-V Failed to Change State Error Code 32788

-
I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor). When I try to start it with more than 4GB of RAM it fails with this error. I tried creating a new VM, using a different VHD file, all create the same error. Before I updated Hyper-V it used to report insufficient memory. What am I missing?
Thanks!
Mike
Dotaz
Všechny reakce
-
Hi Sir,
>>I have a Hyper-V machine running on a server with 20GB of RAM available (according to resource monitor).
This is a physical server ?
What is the version of OS ?
>>Before I updated Hyper-V it used to report insufficient memory.
Have you tried to use performance monitor with counter "hyper-v dynamic memory balancer system balancer " to check if there is free memory larger than 4GB :
Best Regards,
Elton
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Navržen jako odpověď Elton_JiModerator středa 10. května 2017 22:29
-
Hi Sir,
I'd like to check the current state of that issue .
Best Regards,
Elton
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. -
This happened to me just now. 12/7/17. I restored a Win 2012 R2 VM using DPM to a physical Windows 2012 R2 HV host like I always do. This time the VM would not start and I received error 32788 when I started the VM.
I forgot to assign the VM a network adapter in HV settings after it was restored but before starting it. I needed the VM it to have an internal network adapter in my case. Changed the VM NIC to an internal switch and VM started right up.
- Navržen jako odpověď lexschulz pátek 19. října 2018 7:19
-
-
Exactly, I had my Virtual Switch in Configuration Error in the HyperV Settings. Changing it to a valid virtual switch solved the problem.
-Mithun
- Navržen jako odpověď VWSurfer69 pátek 4. května 2018 16:22
-
I had exactly the same error with a virtual machine. The virtual switch was ok, even removing the network adapter and starting without network did not help. I solved it with stopping the VM Service on the server (VM continued to run) and starting it again - now the VM started without any error.
-
-
-