CPU Spikes in a Hyper-V VM
-
Host is finally rebooting...
-
@garak0410 said:
@scottalanmiller said:
Spybot?
The program Spybot? I removed it once I used it to scan tonight. The DC VM is taking forever to shutdown too as I try to reboot the host...
I don't think that it removed completely.
-
@garak0410 said:
The domain controller VM is now at 10 minutes for waiting for it to shut down. This point more now toward the host? Because it just isn't the file server now.
VMs normally go in seconds. Have you installed anything out of the ordinary on both?
-
Rebooting the host has seemed to improved performance, even with Symantec running. The last time I rebooted the VM, it was at 99% CPU the entire time and took forever to do a thing...now, it seems "normal." Heck, even down to 1% at the moment.
SO troubleshooting is going to be on the host right?
-
@garak0410 said:
Rebooting the host has seemed to improved performance, even with Symantec running. The last time I rebooted the VM, it was at 99% CPU the entire time and took forever to do a thing...now, it seems "normal." Heck, even down to 1% at the moment.
SO troubleshooting is going to be on the host right?
Perhaps. Maybe the control environment. Do you have anything installed there?
-
@scottalanmiller said:
@garak0410 said:
Rebooting the host has seemed to improved performance, even with Symantec running. The last time I rebooted the VM, it was at 99% CPU the entire time and took forever to do a thing...now, it seems "normal." Heck, even down to 1% at the moment.
SO troubleshooting is going to be on the host right?
Perhaps. Maybe the control environment. Do you have anything installed there?
THis is what I look like now on the VM:
Nothing but Hyper-V installed on the host. Absolutely nothing. Just a Hyper-V role that that's it...
-
Odd, keep an eye on it but maybe something odd, like a driver failure happened or something had not updated yet and it was freaking out. Can happen.
-
@scottalanmiller said:
Odd, keep an eye on it but maybe something odd, like a driver failure happened or something had not updated yet and it was freaking out. Can happen.
Bad RAM perhaps? I did add some server certified RAM but not a "major" brand...
-
Thanks as always for the suggestions...I think I can sleep now...and perhaps take that 1/2 day off tomorrow too!
-
@garak0410 said:
@scottalanmiller said:
Odd, keep an eye on it but maybe something odd, like a driver failure happened or something had not updated yet and it was freaking out. Can happen.
Bad RAM perhaps? I did add some server certified RAM but not a "major" brand...
Possible, but unlikely. You can always use memcheck86 to run it through its paces.
-
@garak0410 said:
Thanks as always for the suggestions...I think I can sleep now...and perhaps take that 1/2 day off tomorrow too!
I wish that I could do that!
-
@garak0410 said:
The domain controller VM is now at 10 minutes for waiting for it to shut down. This point more now toward the host? Because it just isn't the file server now.
Hyper-V's a little slow, but it's not that slow. I'm still interested in seeing what the middle section of the disk part of Performance Monitor looks like. While CPU may be an issue, some of what you're describing sounds like storage latency. Do you have any snapshots going?
-
@Nara said:
@garak0410 said:
The domain controller VM is now at 10 minutes for waiting for it to shut down. This point more now toward the host? Because it just isn't the file server now.
Hyper-V's a little slow, but it's not that slow. I'm still interested in seeing what the middle section of the disk part of Performance Monitor looks like. While CPU may be an issue, some of what you're describing sounds like storage latency. Do you have any snapshots going?
Well, I can do another screen shot of the Performance Monitor if needed but it is running fine now and appeared to be a host issue but I've not found the root cause.
-
Still all good this morning?
-
Yeah...had a scare when someone called to say a 6MB file took 4 minutes to server but was a local PC issue. He rebooted and it was fine.
I'd like to find out why the host had problems before it happens again. All part of learning the Virtualization world. The ONLY thing that happened this week was a freak power surge on Monday (the debut of the new Virtual File Server) and we do have battery backups so I didn't reboot the host. I do not think that had ANYTHING to do with it but so far, it is the only factor.
-
Enjoy your half day!
-
So far, this hasn't returned though management had their concerns about it and virtualization. Praying it was just a fluke.
-
Fingers crossed then. Could have been almost anything.
-
@scottalanmiller said:
Fingers crossed then. Could have been almost anything.
That's what I told management...fingers crossed...the only thing I didn't turn back on was Unitrends Free (which I've not had time to use yet but will soon as you may see in another thread)...
