VMworld

This Question is Answered

2 "helpful" answers available (2 pts)
7 Replies Last post: Sep 26, 2008 6:36 AM by jlieberman  
Click to view jlieberman's profile Candidate 4 posts since
Sep 10, 2007

Sep 17, 2008 11:08 AM

High processor utilization after SQL server vMotions


I was wondering if anyone has ever had an issue where processor utilization goes through the roof after it is vMotioned? We are getting crushed when this happens, but the issue resolves when the VM is rebooted. So how do I get the system to work properly without having to reboot?

Click to view Stefan Rush's profile Candidate 6 posts since
Sep 17, 2008
1. Sep 17, 2008 3:50 PM in response to: jlieberman
Re: High processor utilization after SQL server vMotions
Wow, not sure what you did here but this has never been a problem with the 20 odd SQL servers I had running at IndyMac Bank. Make sure you are using RDM LUN's for the DB and a minimum of 2 CPU's if this is production.
Click to view Jeff Brown's profile Candidate 1 posts since
Aug 27, 2008
3. Sep 23, 2008 12:09 PM in response to: jlieberman
Re: High processor utilization after SQL server vMotions

Had the same problem, added the following from a posting i found. Go to your cluster settings, under VMWare DRS, go to Advanced options and add this "MemOverheadGrowth" the value is "4".

This completely fixed my issue.

Click to view Jeff Adams's profile Candidate 3 posts since
Aug 29, 2008
4. Sep 23, 2008 2:07 PM in response to: jlieberman
Re: High processor utilization after SQL server vMotions
Stefan,

Would you mind sharing the info on the updates? I occasionally see this on my VC VM when it is migrated. Sometimes the CPU stays pegged for up to an hour after the VMotion. I've 'resloved' this by stopping/starting the VC service, but even that takes a while to perform when the CPU is at 100%.

-Jeff
Click to view mreves's profile Candidate 2 posts since
Sep 10, 2007
6. Sep 25, 2008 4:29 PM in response to: jlieberman
Re: High processor utilization after SQL server vMotions
Hi Josh, just to let you know, we are having the same problem. I hit up VM at the Tech Bar while I was at VMWorld and I'm working with Keith Farkas on trying to resolve the issue. My issue started once I upgraded to 3.5 and I didn't have the problem before. I could vMotion all day long and my performance would not be affected.