- Remove From My Forums
-
Question
-
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
Answers
-
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.-
Proposed as answer by
Wednesday, May 10, 2017 10:29 PM
-
Marked as answer by
Hamid Sadeghpour SalehMVP
Saturday, December 14, 2019 10:49 PM
-
Proposed as answer by
- Remove From My Forums
-
Question
-
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
Answers
-
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.-
Proposed as answer by
Wednesday, May 10, 2017 10:29 PM
-
Marked as answer by
Hamid Sadeghpour SalehMVP
Saturday, December 14, 2019 10:49 PM
-
Proposed as answer by
При попытке запустить витруальную машину в Hyper-V получил такую ошибку:
Не удалось изменить состояние.
Не удалось выполнить операцию; код ошибки «32788»
(Failed to Change State. Error Code 32788)
Из найденных на форумах и блогах советов по устранению данной ошибки, пробовал:
- удаление сетевого адаптера — не помогает
- перезапуск служб Hyper-V — не помогает
Само решение как-то пришло ко мне случайно. Оказалось, не хватало оперативной памяти — закрыл приложения, отъедающие много памяти — помогло!
Как вариант также — уменьшить объем используемой VM памяти (убедитесь, что VM не находится в состоянии «сохранена»)
I recently got an error saying failed to change state with error code 32788 in Hyper-V while attempting to power on a particular virtual machine. This could be one of the unexpected issues you may face while managing the Hyper-V environment for a long time. There are several reasons for this problem, and let’s analyze each.
Below is the screenshot of the error related to this case, ‘the operation failed with error code 32788.’ It appeared when I tried to power on a virtual machine. Meanwhile, other virtual machines on the same Hyper-V host work fine.
Reasons For Error Code 32788 on Hyper-V
The main cause is the conflict in the virtual machine configuration/settings. Something has changed or missing from the configuration settings, which leads to the Hyper-V failed to change state error. Here are the potential settings you must check for the particular virtual machine that is not powering on.
- The network configuration of the VM
- The ISO file attached to VM
- Low disk space on the volume the VM is stored
- The virtual machine management service is not properly working (or needs restart) on the host computer.
In my example, it was related to the network settings (Virtual switch) conflict. I recently changed the name of the virtual switch on the host server but missed updating this particular virtual machine settings.
1) Virtual Machine Network Configuration Error
Open the settings of the virtual machine from the Hyper-V console or cluster.
Go to the Network Adapter settings and verify it is in a good state. You may see the Configuration Error as shown below if this is causing the VM to change the state.
Mismatch or nonexistence of the correct virtual switch name will prevent the virtual machine from starting with the Failed to Change State error in Hyper-V. Selecting the correct virtual switch from the drop-down will solve the issue. Make sure you attach the right virtual switch to the host server and save the settings. Power on the VM now to see how it works.
2) ISO File Mounted on the VM is Not Available
There could be a possibility that the ISO file mounted to the VM/guest OS is not available at the correct location now. This may prevent the VM from powering and showing failed to change the state error. You might have moved or deleted the ISO file from the original location. In other cases, you might have migrated this VM from a different host where the ISO file path differs.
Since the actual error doesn’t give clear details about it, we need to check the DVD Drive settings of the VM.
Open the virtual machine settings, and click on DVD Drive. You can see the path of the ISO file here.
If you need the ISO file inside the virtual machine, you need to attach the correct file from the correct location. If you don’t want, select the ‘None’ option to boot the VM without an ISO file. The VM should power on without any issues now.
3) Disk Space Issue
The volume/partition which is hosting the VM should have enough disk space. Snapshots, dynamically expanding disk type, and maintenance tasks consume space on the Hyper-V host regularly. It is always better to immediately check the disk space when you get an error starting the virtual machine.
You can easily see the disk warning and usage if it is a cluster environment. If it is hosted on local disks or partitions, the Windows explorer will give a clear idea of the disk space usage. Either you need to free up some space or extent the volume (increase the disk size) before powering on the Virtual Machine.
4) Check the Virtual Machine Management Service
If none of the above 3 steps helps solve failed to change state error with code 32788 in Hyper-V, try this 4th step. If the other virtual machines work fine and you can connect them from the Hyper-V manager or Cluster manager, the Virtual Machine Management (VMM) service is probably running fine on the host server. But in our case, we can try restarting the service to see whether it helps.
Open the Services console on the server and restart the below service.
NOTE: Restarting the Hyper-V Virtual Machine Management service in the production environment while VMs are working may interrupt the Hyper-V services on the particular host. You must take all precautions while doing the service restart.
Reboot the Hyper-V host server if the service restart doesn’t help.
We believe one of the solutions will work in solving this issue and start the virtual machine in Hyper-V.
Summary- Today we will be discussing on Virtual Machine, corruption reasons, and techniques to fix Virtual Machine error code 32788.
Someday back I was going through my emails and I found one of my reader’s emails with a question and the exact query was ” how to resolve Virtual Machine error 32788″.
I guess many of us face this issue so, today I will be sharing with you the ways to resolve/fix VM error 32788. Before that let us understand what is actually a Virtual Machine.
What is a Virtual Machine?
Virtual Machine is basically a software program that behaves like a Virtual Computer. It runs on your (host operating system)and allows Virtual hardware to the guest Operating system. And the guest operating system runs as just another program on your computer.B ut these Virtual Machines are not error-free and if you have used it on your own then you must have encountered an error stating” failed to change state with error code 32788 on Hyper V” host while attempting to start the selected virtual machine right?
Now, what could be the possible reason behind this error 32788. Let’s find out
Reason/Cause for “Failed to change State error code 32788 on Hyper V”
It may happen due to the conflict in Virtual Machine configuration if you have recently changed the name of a virtual switch and it is not yet properly configured in the Virtual Machine Settings.
How to Resolve Virtual Machine error code 32788?
Method 1
To fix this error follow the steps mentioned below:
- Go to the Virtual Machine and open the settings of VM from Hyper V console
- Now, go to Network adapter Settings option and a check is there any Conflict (Configuration error).
- Change the Virtual Switch and attach the correct Virtual Switch.
- Now Power on the Virtual Machine without any warnings.
METHOD 2
The other thing you can do to decode VM error 32788 is
- Just copy the Old VHD file on a separate path.
- Now, generate a New Virtual Machine
- On the user existing generate a new VHD file with the same configuration.
- Now, power on the machine.
- It will show the Virtual Machine as it is
USING AUTOMATED METHOD.
This is how you can resolve Failed to change state error code 32788 and if the above method didn’t work for you then you should prefer automated method one of the preferred tools I know is the Virtual Machine Data Recovery Toolkit. I have used it on my own and it worked for me that is why I am suggesting to try this tool once, as it has many prominent features some of them are:
- It is the ideal solution to recover corrupt VHD, VMDK, VDI and VMDK files.
- Virtual Machine recovery toolkit supports MBR and GPT both the partition tables.
- It has two modes of Scanning Standard and Advanced.
- It supports all the famous standard files such as FAT, FAT16, FAT32, FAT64, NTFS, HFS+ and EXTX.
- Users are allowed to add new custom value settings to restore missing or lost files.
CONCLUSION
So, I have described all the possible manual or automated techniques or ways to fix Virtual Machine error code 32788 for both the technical and non-technical users. Hope it helps.
You can also read: How to repair VHD file Manually