Hello Avi,
> >> Please try using 'taskset' to pin the VM to one cpu and report.
> > That works! This works especially well if I use taskset right from the
> > start of the vm...
> Well, that's not a good sign. Things should work even if not pinned.
Hmm, anything else I can try to debug?
Kind
Joris wrote:
> Helo Avi,
>
>
>
>>> This image works well half of the time (very responsive and no
>>> interruptions), but after some time it will completely freeze for a
>>> period of time (sometimes seconds, sometimes minutes it would seem).
>>> Both the network and the console are completely u
Helo Avi,
> > This image works well half of the time (very responsive and no
> > interruptions), but after some time it will completely freeze for a
> > period of time (sometimes seconds, sometimes minutes it would seem).
> > Both the network and the console are completely unresponsive.
> Please
Hi Avi,
> > Please CC me, I'm not a subscriber to the list.
> Please try using 'taskset' to pin the VM to one cpu and report.
That improves things significantly.
The first minute the symptoms are still present, after that the VM
appears to work smoothly.
This is really great, thanks!
Kind re
Joris wrote:
> Hi,
>
>
> Please CC me, I'm not a subscriber to the list.
>
> I have a Debian unstable 64bit host on an intel S3000 quad core xeon
> X3210. Kernel 2.6.22-2-amd64 (debian flavour) and KVM28 and KVM36.
>
> Linux guests run very well.
>
>
> I installed Win2003 EE SP2 with --no-kvm, and
Hi,
Please CC me, I'm not a subscriber to the list.
I have a Debian unstable 64bit host on an intel S3000 quad core xeon
X3210. Kernel 2.6.22-2-amd64 (debian flavour) and KVM28 and KVM36.
Linux guests run very well.
I installed Win2003 EE SP2 with --no-kvm, and disabled ACPI in the
windows se
