On Mon, 2012-10-08 at 22:31 +0200, Peter Viskup wrote:
>
> xm vcpu-pin 0 all 0
>
> This explains the CPU Affinity and where the issue is coming from.
> Anyway this was working before (don't know when exactly this issue
> raised). Could it be related to move to pv_ops kernels?
I don't think so,
Hello Ian,
On 10/08/2012 05:31 PM, Ian Campbell wrote:
I'm afraid I don't have any particularly dazzling insights here. One
thing you could try is asking on the upstream xen-users@ list in case
someone else has seen this, although it doesn't ring any bells for me.
Another experiment might be to
On Sun, 2012-10-07 at 12:52 +0200, Peter Viskup wrote:
> Package: linux-image-2.6.32-5-xen-amd64
> Version: 2.6.32-45
>
> I am experiencing issues with Xen once all CPUs are available to dom0.
> There is high "steal time" shown once I do not set one CPU available for
> dom0 (doesn't matter what
Package: linux-image-2.6.32-5-xen-amd64
Version: 2.6.32-45
I am experiencing issues with Xen once all CPUs are available to dom0.
There is high "steal time" shown once I do not set one CPU available for
dom0 (doesn't matter what way is used - xend-config, Linux or Xen
hypervisor boot argument)
4 matches
Mail list logo
