Hyper-V servers tank when VMs use more than 150gb out of 288gb of RAM
-
Montag, 21. Januar 2013 19:57
I am having a problem with two Hyper-V servers (Win2k8R2 Ent). They each have 288Gb of RAM.
The problem is .... when the VMs collectively use more than about 150Gb of RAM, the servers grind to a halt.
Network connections drop....VMs freeze or run extremely slow etc.
The problem does not appear to be CPU related...it is totally memory....if I give one server an extra 5gb RAM, the next day the whole system will tank out.
Any ideas?
I also have problems with VMs failing to shutdown...they get stuck on "Turning off" indefinitely, until i restart the server.
Alle Antworten
-
Montag, 21. Januar 2013 22:03Moderator
1) are any of the VMs Server 2012 / Win8?
2) have you updated / reinstalled the Integration Components in the VMs to ensure they match the host?
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
Dienstag, 22. Januar 2013 00:09
There are about 5x Windows Server 2008 R2 VMs on each server and the other VMs (about 100) are Win7 64.
Everything is SP1 and I am using dynamic memory allocation on the VMs.
-
Dienstag, 22. Januar 2013 00:32Moderator
Okay then.
Question #2 above. Have you consciously updated the Integration Components in the VMs?? It is a manual process.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
Dienstag, 22. Januar 2013 01:36
No I havent manually updated the Integration Components. I did not think that this would be necessary as they are all SP1...looking in Device Manager it says the version is 6.1.7601.17514, which looks like it is the latest....
But could updating these Integrated Components anyway help out??
I don't care if it only improves performance 1%, I will go through every VM and do it!
EDIT: I have just finished updating all the VMs Integrated Components.
- Bearbeitet 8o43hoieriohjr Dienstag, 22. Januar 2013 02:33
-
Dienstag, 22. Januar 2013 03:00
make sure all virtual machines have integration components installed
now for each virtual machine, i use the dynamic RAM allocation feature. I start with the minimum 512 MB and install the desired stack, repeat for each VM
now depending on the load each VM will be given a varying amount of RAM as needed
this is the best strategy, now if a load needs more than 64 GB I suggest using a dedicated machine
Windows MVP, XP, Vista, 7 and 8. More people have climbed Everest than having 3 MVP's on the wall.
Hardcore Games, Legendary is the only Way to Play
Developer | Windows IT | Chess | Economics | Vegan Advocate | PC Reviews
- Als Antwort markiert Lawrence LvMicrosoft Contingent Staff, Moderator Mittwoch, 30. Januar 2013 07:11
-
Dienstag, 22. Januar 2013 04:11Moderator
Yes, Integration Components in the VMs should always be updated. And the only way is to insert the Integration Services setup disk and logon to the VM and respond to the prompts.
Without this, at the best you run in a compatibility mode and the mileage varies greatly by OS and the degree of being out of sync. Most problems manifest in the networking stack first. But they can manifest differently.
As far as dynamic memory settings, it depends on the application in the VM and the purpose of the VM as to what a good minimum is.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.- Als Antwort markiert Lawrence LvMicrosoft Contingent Staff, Moderator Mittwoch, 30. Januar 2013 07:10
-
Dienstag, 22. Januar 2013 19:07
Yes, Integration Components in the VMs should always be updated. And the only way is to insert the Integration Services setup disk and logon to the VM and respond to the prompts.
Without this, at the best you run in a compatibility mode and the mileage varies greatly by OS and the degree of being out of sync. Most problems manifest in the networking stack first. But they can manifest differently.
As far as dynamic memory settings, it depends on the application in the VM and the purpose of the VM as to what a good minimum is.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.The Win7 VMs are set to start with 768MB of RAM and can use up to a maximum of 3GB. They normally do not use more than 2GB of RAM.
The WinSvr VMs use between 1gb and 4gb of RAM. I have three servers tho which use 15GB, which I am considering moving to physical machines, because the server tanks when a lot of memory is used.
- Bearbeitet 8o43hoieriohjr Dienstag, 22. Januar 2013 19:08
-
Dienstag, 22. Januar 2013 20:16
mine are set to 512 MB minimum and 64 GB max
demanding loads are better in a blade box which can reduce the amount of rack used a bit
rack blades are limited to dual CPU so if you need more then the 2U box is the best bet
if you need to use a GPU then a 4U box is needed due to the height of the compute cards
Windows MVP, XP, Vista, 7 and 8. More people have climbed Everest than having 3 MVP's on the wall.
Hardcore Games, Legendary is the only Way to Play
Developer | Windows IT | Chess | Economics | Vegan Advocate | PC Reviews
-
Montag, 28. Januar 2013 06:40Moderator
Hi,
I would like to confirm what is the current situation? Have you resolved the problem or do you have any further progress?
If there is anything that we can do for you, please do not hesitate to let us know, and we will be happy to help.
Lawrence
TechNet Community Support
- Als Antwort markiert 8o43hoieriohjr Freitag, 1. Februar 2013 00:42
.png)
.png)
