Oh,
On Apr 16, 2010, at 9:37 , Pim van Riezen wrote:
> Another datapoint. This customer has similarly loaded VPS machines on a
> number of different hardware nodes. Not all of them had the lockup problem. I
> applied the jiffies clocksource to all his machines, regardless of their
> current problem status. After a day without lockups, the customer complained
> about time drift (ntp was not activated). The guest that had experienced the
> soft lockups earlier had major clock drift and were way ahead:
>
> 16 Apr 09:29:26 ntpdate[11236]: step time server 194.109.22.18 offset
> -7337.731686 sec
>
> That's over 2 hours accumulated in less than 24 hours of uptime. The guests
> that hadn't been excperiencing the lockup issues berfore switching to the
> jiffies clocksource hadn't drifted that much after the switch and were, at
> most, 120s behind after the same amount of runtime.
There's more correlation between the guests that had the lockups and those that
didn't: the guests that locked up (and now have a way speedy jiffies clock)
were all on the same hardware platform, with an older Xeon CPU than on the
guests that had no issues. I attached cpuinfo for both the broken and the
non-broken dom0s. All are on Xen-3.4.1 (hypervisor-version doesn't seem to
affect this issue) and the latest CentOS 2.6.18 dom0-kernel.
Cheers,
Pim
cpuinfo_lockups.txt
Description: Text document
cpuinfo_nolockups.txt
Description: Text document
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home