CPU Spikes in a Hyper-V VM
-
Important to consider that malware is a possibility. Do a scan with some third party scanners to improve confidence. Such a new system, unlikely to be infected but you never know.
-
If you bring up performance monitor, what files are being written/read? Even if the disk activity is relatively low, it gives you an idea of what the process is doing by the files it's interacting with.
-
It had no malware.
So, powered it off and took away a virtual CPU.
It took forever and a day to boot up and even when I finally got a login screen, it takes forever to get its services started (Welcome, Policy Registration, Local Session Manager takes forever to come up). Then a black screen for a good while and finally the desktop. And waiting and waitng for it to let me input. Server Manager creeps to a start. The right click I did on the task bar so I could get the task manager took over a minute to give me the context menu...finally got task manger up and for sure, back to 99% CPU with Symantec and Service Host taking most of it.
This is terrible It has to be some kind of VM setting wrong. But it wasn't this bad yesterday.
I am about to bring up resource monitor but it is taking forever as well...
-
@Nara said:
If you bring up performance monitor, what files are being written/read? Even if the disk activity is relatively low, it gives you an idea of what the process is doing by the files it's interacting with.
-
Expand the middle row and sort by total.
-
THis is at night with no one using it?
-
And what is SDtray?
-
@scottalanmiller said:
THis is at night with no one using it?
Yes... Right now, I am attempting to reboot the host...but the file server VM is not shutting down well.
-
Spybot?
-
@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...
-
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.
-
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!
