jgrammer42
asked on
Hyper-V and VM memory allocation
I am very new to Hyper-V configuration, so please forgive me if this question seems very easy and ignorant.
I have a Windows 2008 R2 server that I have setup as a Hype-V server with 5 VM instances on it.
The problem I am having is with the last, (5th), VM instance. No matter what I do to manipulate the memory of the server, I still get the error message of, "Not enough memory in the system."
Here is the configuration of the server:
- 16GB available RAM on host instance at boot
- 4 VMs x 2GB RAM (static) start w/o error; each has single disk of 127GB
- 6.6 GB RAM free on host instance after starting above VMs
- 5th VM configured at either 2GB, 3GB or 4GB RAM (static) will not launch -- "Not enough memory in the system"
Here is what I have done so far to try and fix the problem with no success:
- removed File Server role so that only role installed is Hyper-V
- disabled Print Spooler service
- created / set HKLM\SOFTWARE\Microsoft\Wi
Has anyone run into this issue? And if so, how did you rectify it. ANY suggestions would be greatly appreciated.
Thank you,
Jeff
I have a Windows 2008 R2 server that I have setup as a Hype-V server with 5 VM instances on it.
The problem I am having is with the last, (5th), VM instance. No matter what I do to manipulate the memory of the server, I still get the error message of, "Not enough memory in the system."
Here is the configuration of the server:
- 16GB available RAM on host instance at boot
- 4 VMs x 2GB RAM (static) start w/o error; each has single disk of 127GB
- 6.6 GB RAM free on host instance after starting above VMs
- 5th VM configured at either 2GB, 3GB or 4GB RAM (static) will not launch -- "Not enough memory in the system"
Here is what I have done so far to try and fix the problem with no success:
- removed File Server role so that only role installed is Hyper-V
- disabled Print Spooler service
- created / set HKLM\SOFTWARE\Microsoft\Wi
Has anyone run into this issue? And if so, how did you rectify it. ANY suggestions would be greatly appreciated.
Thank you,
Jeff
R_Edwards
do you have enough HD space for the VM?
ASKER
R_Edwards,
I believe so yes. As noted above each VM is allocated 127GB's. The server itself has 1TB of disk space.
Currently there is 665 GB's of used space, and 449 GB's of free space available. (And this is after all of the VM's had been allocated.)
Was there something else with regard to disk space I should be looking for?
Thank you,
Jeff G.
I believe so yes. As noted above each VM is allocated 127GB's. The server itself has 1TB of disk space.
Currently there is 665 GB's of used space, and 449 GB's of free space available. (And this is after all of the VM's had been allocated.)
Was there something else with regard to disk space I should be looking for?
Thank you,
Jeff G.
Jeff,
No i was just looking at other reasons for your error. Have you started the physical machine up with no running VM's (completely off, not paused) and started Task Manager, then onr by one started the VM's? This will tell you what each VM is doing on startup. if there is nothing odd, try reducing the sizes of each VM to 1GB and see if the 5th will start.
-=Richard
No i was just looking at other reasons for your error. Have you started the physical machine up with no running VM's (completely off, not paused) and started Task Manager, then onr by one started the VM's? This will tell you what each VM is doing on startup. if there is nothing odd, try reducing the sizes of each VM to 1GB and see if the 5th will start.
-=Richard
ASKER
Richard,
To your first question: Yes. I have booth the physical machine up with no VM's at all running. When I have TaskMgr running and starting each VM session one by one, here is what I am seeing after loading 4 VM's.
Total Mem 16358 (MB)
Cached 395 (MB)
Available 6660 (MB)
Free 6300 (MB)
When I start the 5th one, I get a window pop-up with the error: "Not enough memory in the system to start virtual machine QAHC with ram size of 2048 megabytes"
I will drop each VM to 1MB and see what happens, and report back here when I get the information.
Thank you,
Jeff
To your first question: Yes. I have booth the physical machine up with no VM's at all running. When I have TaskMgr running and starting each VM session one by one, here is what I am seeing after loading 4 VM's.
Total Mem 16358 (MB)
Cached 395 (MB)
Available 6660 (MB)
Free 6300 (MB)
When I start the 5th one, I get a window pop-up with the error: "Not enough memory in the system to start virtual machine QAHC with ram size of 2048 megabytes"
I will drop each VM to 1MB and see what happens, and report back here when I get the information.
Thank you,
Jeff
ASKER
Richard,
Ok, here is what happens with all five VM's set to 1024MB of RAM. Everything works great. All 5 VM's come up and run fine with all of them defined with only 1GB of RAM.
So, I shutdown all of the VM's again. Changed 4 of them to 2048MB's of RAM and left the 5th VM set to 1024MB of RAM.
Again all 5 VM's came up and were running then.
However, because of the applications that I am going to be running on these VM's I must have 2GB's of RAM for each VM.
Do you have any idea why the 5th VM has to have only 1GB of RAM when there is at least 6GB available as "free"?
(I should also note it does not matter WHICH of the VM's I designate as the 5th one, it will happen regardless of which one I randomly select to be the 5th one to bring up)
Thank you,
Jeff
Ok, here is what happens with all five VM's set to 1024MB of RAM. Everything works great. All 5 VM's come up and run fine with all of them defined with only 1GB of RAM.
So, I shutdown all of the VM's again. Changed 4 of them to 2048MB's of RAM and left the 5th VM set to 1024MB of RAM.
Again all 5 VM's came up and were running then.
However, because of the applications that I am going to be running on these VM's I must have 2GB's of RAM for each VM.
Do you have any idea why the 5th VM has to have only 1GB of RAM when there is at least 6GB available as "free"?
(I should also note it does not matter WHICH of the VM's I designate as the 5th one, it will happen regardless of which one I randomly select to be the 5th one to bring up)
Thank you,
Jeff
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Richard,
That DOES appear to have fixed the problem!!
Apparently, when I installed Hyper-V NUMA was disabled. I thought it was Enabled by default. Once I enabled NUMA, and then rebooted the physical server. ALL 5 VM's came up and were running with 2GB of RAM.
Thank you very, very much!
Jeff
That DOES appear to have fixed the problem!!
Apparently, when I installed Hyper-V NUMA was disabled. I thought it was Enabled by default. Once I enabled NUMA, and then rebooted the physical server. ALL 5 VM's came up and were running with 2GB of RAM.
Thank you very, very much!
Jeff
ASKER
Excellent support. Thank you very much!
My pleasure. Glad you are up and working