Changing RAM Allocation
I'm having a similar issue with RAM allocation. I can't increase the RAM allocation on any virtual machine - it gives an error indicating that there isn't enough resources. But the error actually shows that there is enough available. The only way to get it to start is to go back to the original memory amount allocated.
Error Message
'Server' is unable to allocate 1024 MB of RAM. Available memory is 4274 MB: Insufficient system resources exist to complete the requested service. (0x800705AA). (VMID 3B33021C-0FB5-4072-9AC0-539B4CE2454A)
Is there any way to update the resources available on the fly?
Answers
Take a look at Tony's post on a NUMA bug for which there is a patch: http://blogs.msdn.com/tvoellm/archive/2008/06/11/can-t-start-my-vm-when-there-is-plenty-of-memory.aspx
- Proposed As Answer byStephen Edgar Friday, July 11, 2008 4:07 AM
- Marked As Answer byChang Yin Monday, July 14, 2008 2:41 AM
New developments!
Managed to solve the problem. Once I disabled pagefile management in Windows and set a static pagefile size of my own choice - it started working!
Hope this helps!
All Replies
Interesting. We are having a problem attempting to do this programatically through WMI as well.
I am curious about watching this one...
Bruce Richards wrote: Is there any way to update the resources available on the fly?
I'm assuming the VM is powered off when you're attempting to do this, correct?
- Yes, the VM is powered off. The option to change the RAM is unavailable while the VM is on or in a saved state. I've also tried purging all the snap shots as well. No luck. It will not start unless I put the RAM back to the original level.
This is an issue that we are actually actively tracking. Could you open up Task Manager and tell us how much memory is in the cached pool?
while the system is in a running state (using 615MB)
The host machine has the following information
Physical Memory (MB)
Total 5114
Cached 1193
Free 2641
New developments!
Managed to solve the problem. Once I disabled pagefile management in Windows and set a static pagefile size of my own choice - it started working!
Hope this helps!
Did you change this setting on the Hyper-V host or within the VM in question?
The setting was changed on the host machine.
- Lucidia,
I am experencing this same issue, but adjusting the page file did not completely fix it. Have you had them problem come back?
I noticed it a couple of days ago, but thought I would update to RTM before I posted about the issue again. Well, after updating to RTM it only took one day for the problem to return.
RAM usage in task manager looks like the file system is caching almost all available RAM which is stopping Hyper-V from starting my machine after my script exports it for backup purposes. Here is the error message.
[Window Title]
Hyper-V Manager[Main Instruction]
An error occurred while attempting to change the state of virtual machine BCSLABHS.[Content]
'BCSLABHS' failed to initialize.Unable to allocate 2048 MB of RAM: Insufficient system resources exist to complete the requested service. (0x800705AA)
[Expanded Information]
'BCSLABHS' failed to initialize. (Virtual machine 27D90745-EABE-43D1-B1C3-1B0E54990446)'BCSLABHS' is unable to allocate 2048 MB of RAM. The available memory is 15682 MB: Insufficient system resources exist to complete the requested service. (0x800705AA). (Virtual machine 27D90745-EABE-43D1-B1C3-1B0E54990446)
[^] Hide details [Close]
- Is your backup script using 'Exporting the VM' or taking a VSS backupsnapshot?
Cheers, Stephen Edgar Take a look at Tony's post on a NUMA bug for which there is a patch: http://blogs.msdn.com/tvoellm/archive/2008/06/11/can-t-start-my-vm-when-there-is-plenty-of-memory.aspx
- Proposed As Answer byStephen Edgar Friday, July 11, 2008 4:07 AM
- Marked As Answer byChang Yin Monday, July 14, 2008 2:41 AM
- Stephen,
My backup script is using "Exporting the VM", I'm planning to convert to DPM once SP1 comes out with Hyper-V support.
Thanks,
Ryan - John,
Thanks for the link! I bet that is my issue.
Ryan
