> This sounds like the classic issue seen on laptops (can search this
> newsgroup for tons of posts):
> 1. Turn off SpeedStep.
> 2. Turn off network offloading/jumbo.
> 3. Increase Min CPU of the VM to something higher than 1. I use something
> like 25-50 depending on how many concurrent VMs I want to run.
>
>
> I usually send PING -t <IP> from one machine into the VM and have a process
> inside the VM PING -t <IP> to another machine, and then things stay smooth
> on both client and host. I've only had to do this on laptops; desktop
> servers tend to run with default configuration.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Phil" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> When I try to interact with the Virtual Server it constantly freezes/locks
> up
> for anywhere from a few seconds to a minute or two. When it unfreezes it
> then runs at an accelerated rate, as if trying to catch up. I've even
> watched the clock on the server and seen the second hand spin around the
> clock face to try to catch up to the real time. This process repeats
> constantly, making it near to impossible to use the virtual server.
>
> The host is an Intel Pentium M 2g with 1gb ram. I've allocated 256mb to the
> guest. The guest is Windows Server 2003.
>
> Any help will be greatly appreciated.
>
> Thanks,
> Phil
>
>
>

> This sounds like the classic issue seen on laptops (can search this
> newsgroup for tons of posts):
> 1. Turn off SpeedStep.
> 2. Turn off network offloading/jumbo.
> 3. Increase Min CPU of the VM to something higher than 1. I use something
> like 25-50 depending on how many concurrent VMs I want to run.
>
>
> I usually send PING -t <IP> from one machine into the VM and have a
> inside the VM PING -t <IP> to another machine, and then things stay smooth
> on both client and host. I've only had to do this on laptops; desktop
> servers tend to run with default configuration.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> //
> "Phil" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> When I try to interact with the Virtual Server it constantly freezes/locks
> up
> for anywhere from a few seconds to a minute or two. When it unfreezes it
> then runs at an accelerated rate, as if trying to catch up. I've even
> watched the clock on the server and seen the second hand spin around the
> clock face to try to catch up to the real time. This process repeats
> constantly, making it near to impossible to use the virtual server.
>
> The host is an Intel Pentium M 2g with 1gb ram. I've allocated 256mb to
> guest. The guest is Windows Server 2003.
>
> Any help will be greatly appreciated.
>
> Thanks,
> Phil
>
>
>

> I believe you need to go into the BIOS to set #1 (at least, that's what I
> had to do on my Dell). I've also seen some laptops that come with system
> tray applets that toggle SpeedStep settings as well.
>
> I've never done #2, but people have said it is in the network card's
> configuration settings. Control Panel\Network Connections->Network Card
>
> #3 can be done in the VS Admin Web app. On the initial home page, left
> sidebar, there is "Virtual Server\Resource Allocation". Now you can choose,
> on a per-VM basis, the minimum CPU (i.e. Reserved Capacity) it can use.
>
> Please use google groups to search this newsgroup for more details on this
> frequently reported issue.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Phil" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> sweet! thanx for the reply. i hate to sound like a newb, but how do u
> perform steps 2 and 3. i've done step 1, even though i had power scheme set
> to "presentation". i changed it to "always on", but set everything to never
> [turn off]. so, how do i change the networking and cpu settings? thanx a
> bunch bro!
>
> -phil
>
> "David Wang [Msft]" wrote:
>
> > This sounds like the classic issue seen on laptops (can search this
> > newsgroup for tons of posts):
> > 1. Turn off SpeedStep.
> > 2. Turn off network offloading/jumbo.
> > 3. Increase Min CPU of the VM to something higher than 1. I use something
> > like 25-50 depending on how many concurrent VMs I want to run.
> >
> >
> > I usually send PING -t <IP> from one machine into the VM and have a
> process
> > inside the VM PING -t <IP> to another machine, and then things stay smooth
> > on both client and host. I've only had to do this on laptops; desktop
> > servers tend to run with default configuration.
> >
> > --
> > //David
> > IIS
> > http://blogs.msdn.com/David.Wang
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > //
> > "Phil" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> > When I try to interact with the Virtual Server it constantly freezes/locks
> > up
> > for anywhere from a few seconds to a minute or two. When it unfreezes it
> > then runs at an accelerated rate, as if trying to catch up. I've even
> > watched the clock on the server and seen the second hand spin around the
> > clock face to try to catch up to the real time. This process repeats
> > constantly, making it near to impossible to use the virtual server.
> >
> > The host is an Intel Pentium M 2g with 1gb ram. I've allocated 256mb to
> the
> > guest. The guest is Windows Server 2003.
> >
> > Any help will be greatly appreciated.
> >
> > Thanks,
> > Phil
> >
> >
> >
>
>
>

> This sounds like the classic issue seen on laptops (can search this
> newsgroup for tons of posts):
> 1. Turn off SpeedStep.
> 2. Turn off network offloading/jumbo.
> 3. Increase Min CPU of the VM to something higher than 1. I use something
> like 25-50 depending on how many concurrent VMs I want to run.
>
>
> I usually send PING -t <IP> from one machine into the VM and have a
> process
> inside the VM PING -t <IP> to another machine, and then things stay smooth
> on both client and host. I've only had to do this on laptops; desktop
> servers tend to run with default configuration.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "Phil" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> When I try to interact with the Virtual Server it constantly freezes/locks
> up
> for anywhere from a few seconds to a minute or two. When it unfreezes it
> then runs at an accelerated rate, as if trying to catch up. I've even
> watched the clock on the server and seen the second hand spin around the
> clock face to try to catch up to the real time. This process repeats
> constantly, making it near to impossible to use the virtual server.
>
> The host is an Intel Pentium M 2g with 1gb ram. I've allocated 256mb to
> the
> guest. The guest is Windows Server 2003.
>
> Any help will be greatly appreciated.
>
> Thanks,
> Phil
>
>

> This sounds like the classic issue seen on laptops (can search this
> newsgroup for tons of posts):
> 1. Turn off SpeedStep.
> 2. Turn off network offloading/jumbo.
> 3. Increase Min CPU of the VM to something higher than 1. I use something
> like 25-50 depending on how many concurrent VMs I want to run.
>
>
> I usually send PING -t <IP> from one machine into the VM and have a process
> inside the VM PING -t <IP> to another machine, and then things stay smooth
> on both client and host. I've only had to do this on laptops; desktop
> servers tend to run with default configuration.
>

> 1. Turn off SpeedStep.
> 2. Turn off network offloading/jumbo.
> 3. Increase Min CPU of the VM to something higher than 1. I use something
> like 25-50 depending on how many concurrent VMs I want to run.
> I usually send PING -t <IP> from one machine into the VM and have a process
> inside the VM PING -t <IP> to another machine, and then things stay smooth
> on both client and host. I've only had to do this on laptops; desktop
> servers tend to run with default configuration.

> I am experiencing problems running Linux machines on my Windows 2003 host. I
> am running the following hardware:
>
> Compaq ML-530 G2 server, 1GHz proc, 1.75GB RAM, RAID 5 with 2 arrays on a
> smart array 5300 controller.
>
> The timing that I am seeing in my syslogs seems to be running about 2 - 3
> muinutes slow. I also see a slow response from the keyboard at a commnad
> prompt. I type in characters, and it takes a few seconds to show up on the
> screen.
>
> Any ideas?

> The first thing you could try (if you haven't already) is install the
> Virtual Server 2003 Service Pack 1 beta. It supports several flavours
> of Linux, so that might give you some general improvements (and could
> potentially fix your current problems as well). Remember that it's a
> beta version so not supported by MS, but since you're running Linux as
> guest OS (which is unsupported anyway) this might not be a big problem.
> <cut>