Choppy performance on HyperV Server R2

Hello,

I just received a new Dell PowerEdge R510. I setup HyperV Server R2.
Everything seemed to be working fine. I created 5 VMs and performance was
good.

Then I decided to get brave and downloaded the Demo for System Center VMM
which cam preconfigured on a VHD.
http://www.microsoft.com/downloads/d...displaylang=en

Ran though System Center config and it found my HyperV Server host. I added
it to the management group. At this point I received a warning that the
HyperV Role would be enabled if it was not already. A few seconds later my
entire HyperV Server Blue Screened.

After reboot, now the Hyper Server Console is running very choppy and not
very responsive. I'm not sure what System Center did to corrupt the HyperV
Server install. I'm almost certain that it is the cuprit somehow since thing
were working swell before I decided to experiment.

Any ideas out there?

Thanks,
Jason Levandoski

try sum total RAM used by Vm subtract from the actual physical host RAM. if
you have 1GB or more left , you are probably ok assuming the physical server
has only hyper-v role turn on

another thing, what if you put the System Center VMM VHD on a different
spindle ( physical drive), would that help?

sometimes even a separate plain 7200 rpm Sata drive can speed thing up when
the system is saturated with disk io

"JasonLev" <JasonLev@discussions.microsoft.com> wrote in message
news:A7E543CF-E969-4394-AD9A-3396928AA5DB@microsoft.com...
> Hello,
>
> I just received a new Dell PowerEdge R510. I setup HyperV Server R2.
> Everything seemed to be working fine. I created 5 VMs and performance was
> good.
>
> Then I decided to get brave and downloaded the Demo for System Center VMM
> which cam preconfigured on a VHD.
>
http://www.microsoft.com/downloads/d...displaylang=en
>
> Ran though System Center config and it found my HyperV Server host. I
added
> it to the management group. At this point I received a warning that the
> HyperV Role would be enabled if it was not already. A few seconds later
my
> entire HyperV Server Blue Screened.
>
> After reboot, now the Hyper Server Console is running very choppy and not
> very responsive. I'm not sure what System Center did to corrupt the
HyperV
> Server install. I'm almost certain that it is the cuprit somehow since
thing
> were working swell before I decided to experiment.
>
> Any ideas out there?
>
> Thanks,
> Jason Levandoski

btw, what happens when you put the scvmm VM to sleep(save state) after
backup the system?
if all other Vm runs happily, scvmm is definitely to blame
if the system crashes, you can try if the hyper-v can be repaired or
restored before you install the scvmm


"gg" <gg@Edm.noMail.net> wrote in message
news:LM52o.9766$z%6.1438@edtnps83...
> try sum total RAM used by Vm subtract from the actual physical host RAM.
if
> you have 1GB or more left , you are probably ok assuming the physical
server
> has only hyper-v role turn on
>
> another thing, what if you put the System Center VMM VHD on a different
> spindle ( physical drive), would that help?
>
> sometimes even a separate plain 7200 rpm Sata drive can speed thing up
when
> the system is saturated with disk io
>
> "JasonLev" <JasonLev@discussions.microsoft.com> wrote in message
> news:A7E543CF-E969-4394-AD9A-3396928AA5DB@microsoft.com...
> > Hello,
> >
> > I just received a new Dell PowerEdge R510. I setup HyperV Server R2.
> > Everything seemed to be working fine. I created 5 VMs and performance
was
> > good.
> >
> > Then I decided to get brave and downloaded the Demo for System Center
VMM
> > which cam preconfigured on a VHD.
> >
>
http://www.microsoft.com/downloads/d...displaylang=en
> >
> > Ran though System Center config and it found my HyperV Server host. I
> added
> > it to the management group. At this point I received a warning that the
> > HyperV Role would be enabled if it was not already. A few seconds later
> my
> > entire HyperV Server Blue Screened.
> >
> > After reboot, now the Hyper Server Console is running very choppy and
not
> > very responsive. I'm not sure what System Center did to corrupt the
> HyperV
> > Server install. I'm almost certain that it is the cuprit somehow since
> thing
> > were working swell before I decided to experiment.
> >
> > Any ideas out there?
> >
> > Thanks,
> > Jason Levandoski
>
>