sglee
asked on
CPU 100% on VM in VMWare
Hi,
I have SBS2011 running as virtual machine in ESXi 5.5 and it is showing 100% CPU utilization when there is no user working today.
I confirmed in snapshot manager that this VM is not running on a snapshot. Virtual machine backup has been performed on this VM hours ago. No user is connected to SBS2011 currently.
I know I can reboot this VM, but I like to find out what is causing this.
What is the best way to find out what is causing this constant high CPU%?
I have SBS2011 running as virtual machine in ESXi 5.5 and it is showing 100% CPU utilization when there is no user working today.
I confirmed in snapshot manager that this VM is not running on a snapshot. Virtual machine backup has been performed on this VM hours ago. No user is connected to SBS2011 currently.
I know I can reboot this VM, but I like to find out what is causing this.
What is the best way to find out what is causing this constant high CPU%?
Sort Task Manager by CPU Utilization High to Low and it should point to a process
ASKER
I've requested that this question be deleted for the following reason:
This question might be related to another question that I already posted.
This question might be related to another question that I already posted.
ASKER
I like to resume this question.
ASKER
@LockDown32
What you see in the screenshot is all there is and they are all 0s.
What you see in the screenshot is all there is and they are all 0s.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Process ExpandedHere it is.
I see that SqlServer is running upt ot 95%.
This is, I think, related to the problem that I experienced. Please see my other posting.
https://www.experts-exchange.com/questions/28949036/SBS-runs-very-slow-after-deleting-WSUS-folder.html
I see that SqlServer is running upt ot 95%.
This is, I think, related to the problem that I experienced. Please see my other posting.
https://www.experts-exchange.com/questions/28949036/SBS-runs-very-slow-after-deleting-WSUS-folder.html
Well that at least shows you what is eating the CPU alive and how to check it. I'll take a look at the other post.
Do you have any non default SQL applications running on the server?
If not then restart the following services one at a time and monitor the CPU usage to isolate which SQL service is causing the issue:
SQL Server (SBSMONITORING)
SQL Server (SHAREPOINT)
Windows Internal Database (MICROSOFT##SSEE)
If not then restart the following services one at a time and monitor the CPU usage to isolate which SQL service is causing the issue:
SQL Server (SBSMONITORING)
SQL Server (SHAREPOINT)
Windows Internal Database (MICROSOFT##SSEE)
Excellent. There was a case just the other day where WSUS was causing that ling of CPU utilization. Are you running WSUS?
ASKER
This problem was addressed by LockDown32 thru the following EE posting:
https://www.experts-exchange.com/questions/28949036/SBS-runs-very-slow-after-deleting-WSUS-folder.html
https://www.experts-exchange.com/questions/28949036/SBS-runs-very-slow-after-deleting-WSUS-folder.html
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for sglee's comment #a41647466
for the following reason:
This problem was addressed by LockDown32 thru the following EE posting:
https://www.experts-exchange.com/questions/28949036/SBS-runs-very-slow-after-deleting-WSUS-folder.html
Accepted answer: 0 points for sglee's comment #a41647466
for the following reason:
This problem was addressed by LockDown32 thru the following EE posting:
https://www.experts-exchange.com/questions/28949036/SBS-runs-very-slow-after-deleting-WSUS-folder.html
Hi Sglee, glad you got the issue resolved.
If LockDown32 provided the answer please award him the points.
LockDown32 - Good catch.
If LockDown32 provided the answer please award him the points.
LockDown32 - Good catch.
Unfortunately I am going to have to object. I gave hi the answer. I think he was just a little confused about how to close the question since it was a link to yet another question.
Unfortunately I am going to have to object. I gave hi the answer. I think he was just a little confused about how to close the question since it was a link to yet another question.