Hi All
I met really strange problem. On 1 host we have 3 instances running in VM
machine. Yes, it was not configured properly, but...
default instance would shout 100% cpu right after startup. I checked all
event log records, errorlogs, dump logs - all look inocent. No option
changes, nothing.
Other 2 instances are just fine.
Any clue?

Can you look at sys.dm_exec_requests or master..sysprocesses while the CPU
is pegged like this? How about running a lightweight trace on startup? Not
everything that consumes CPU will necessarily have anything at all to do
with error logs...





On 7/17/08 4:25 PM, in article
84F1D7DD-24A3-415F-927A-E043D540463A@microsoft.com, "Gene."
<Gene@discussions.microsoft.com> wrote:

> Hi All
> I met really strange problem. On 1 host we have 3 instances running in VM
> machine. Yes, it was not configured properly, but...
> default instance would shout 100% cpu right after startup. I checked all
> event log records, errorlogs, dump logs - all look inocent. No option
> changes, nothing.
> Other 2 instances are just fine.
> Any clue?

I think it was just unproportional load on the instance, no technical problem.

"Gene." wrote:

> Hi All
> I met really strange problem. On 1 host we have 3 instances running in VM
> machine. Yes, it was not configured properly, but...
> default instance would shout 100% cpu right after startup. I checked all
> event log records, errorlogs, dump logs - all look inocent. No option
> changes, nothing.
> Other 2 instances are just fine.
> Any clue?