Ferenc Wagner <wferi@niif.hu> writes:

quoted text
> Jeremy Fitzhardinge <jeremy@goop.org> writes:
> --text follows this line--
>> Ferenc Wagner wrote:
>>
>>> After upgrading a Xen virtual machine to Debian's 2.6.26-4 kernel, I
>>> noticed that the idle counter doubled its pace on one of the machines:
>>> [...]
>>> One out of three machines show this effect, with the exact same kernel
>>> and Xen versions (3.2.0, dom0 is Debian's stock Etch 2.6.18 kernel).
>>> They aren't hosted by the same machine, though: the misbehaving one is
>>> on a different installation with very similar hardware (3 vs 2 GHz).
>>> All the guest are paravirtual.
>>
>> So you're saying that they are identical Xen and guest kernel binaries,
>> but one of three is showing doubled idle time?
>
> Now I upgraded another domU, and that also shows this doubling effect,
> so I've got two domUs (running on xen2-ha) misbehaving, and other two
> (running on xen2) behaving correctly.

Possibly related: three out of the above four 2.6.26 domUs froze
yesterday afternoon.  The consoles don't show anything and are dead,
they don't react to sysrq, even.  According to xm list, the frozen
domains are constantly running (stuck in r state).

I haven't destroyed them yet, in case it is possible to extract any
info from the system.  If not, please tell me so I can restart them.

On the other hand, I'll have a look whether the same kernel running on
the bare metal produces this idle count discrepancy.
-- 
Thanks,
Feri.

Ps: Please note that xen-devel swallows my mails without a trace,
    probably because I'm not subscribed.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/