High CPU on Hyper-V VM
-
@coliver said:
I had this issue on Hyper-V when I first got our new VM host. It turned out to be several bad memory modules. Got them replaced under warranty and haven't had an issue since.
Really? High CPU on a VM related to RAM? That is interesting and something I may look at...any recommendations on memory? (Brand or Store) Or I could get it from Dell...
-
@garak0410 said:
@coliver said:
I had this issue on Hyper-V when I first got our new VM host. It turned out to be several bad memory modules. Got them replaced under warranty and haven't had an issue since.
Really? High CPU on a VM related to RAM? That is interesting and something I may look at...any recommendations on memory? (Brand or Store) Or I could get it from Dell...
Yep, I have no idea why it was the case but it resulted in high CPU usage and the console being locked up like you are mentioning. No RAM recommendations.
-
@coliver said:
@garak0410 said:
@coliver said:
I had this issue on Hyper-V when I first got our new VM host. It turned out to be several bad memory modules. Got them replaced under warranty and haven't had an issue since.
Really? High CPU on a VM related to RAM? That is interesting and something I may look at...any recommendations on memory? (Brand or Store) Or I could get it from Dell...
Yep, I have no idea why it was the case but it resulted in high CPU usage and the console being locked up like you are mentioning. No RAM recommendations.
Thank you...it is worth a try and got approval to purchase RAM...
-
This is across all VMs on the host or just one of them? Sorry, my situation was across all VMs. Made it impossible to use the host for 15-20 minutes at a time. Then it would... cycle... or something... to release the bad RAM? and everything would go back to normal. Then it would happen again at random intervals. Thankfully I was just testing the host so it wasn't in production yet.
-
@coliver said:
This is across all VMs on the host or just one of them? Sorry, my situation was across all VMs. Made it impossible to use the host for 15-20 minutes at a time. Then it would... cycle... or something... to release the bad RAM? and everything would go back to normal. Then it would happen again at random intervals. Thankfully I was just testing the host so it wasn't in production yet.
The main VM affected is our FILE SERVER VM...it will peg out at 100%...the other servers not so much but however, this most recent time, the Virtual Host did "lock up' and described above...I could not get it to clock on anything or get into task manager...after I was able to remote in and gracefully shut down the VM's and waited until I felt like they were down, I fat fingered the Virtual Host...and it is running perfectly now...the thing is, this will return again in a few days and power down seems to help each time for a few days...
-
This post is deleted! -
I am calling Dell just as a backup option...I want this resolved..
-
makes me think about a possible caching problem... something fills up in a few days and then all hell breaks loose.
-
They wanted to make sure our system BIOS and iDRAC firmware were all up to date...they said the system BIOS I was on was reported to eventually have less wattatage going to the system CPU...so, I got both of them updated and loaded Open Manage (yes, never got around to loading it)...going to monitor this for a few days...
-
What does open manage do?
-
@Dashrender said:
What does open manage do?
Dell's OpenManage Server Administrator...for one, without it, I had issues upgrading the firmware for both BIOS and iDRAC...shows health, summary, asset information, etc...loaded it on the Virtual Host...
-
Update...the HIGH CPU problems have not returned thus far after BIOS and iDRAC firmware updates...fingers crossed...
-
Still good news to report...going on 8 days and this problem has not reappeared...getting more hopeful...
-
Well, this problem came back over the weekend. I just couldn't believe it. So got back on the phone with Dell...this time, they noticed in the BIOS we had a setting enabled called Performance Per Watt (DAPC)...they had me change that to just PERFORMANCE and the tech was almost certain this problem will be gone.
I crossed check through some searches and I do see a lot of posts where Performance Per Watt (DAPC) had an affect on Hyper-V, so feeling a little better about this now.
