Pages

Tuesday, September 21, 2010

Resolving the echo messages displayed in the Xen VM ' Console

Error :  452 messages suppressed clocksource/0: Time went backwards

Check out the links,

http://xen.1045712.n5.nabble.com/Time-went-backwards-td2594614.html 

http://wiki.debian.org/Xen 


Please read this :
If a domU crashes or freezes while uttering the famous lasts words
'clocksource/0: Time went backwards', your domU is likely using the
xen clocksource instead of its own clock ticks. In practice, this
seems to be the cause of infrequent lockups under load (and/or
problems with suspending). A workaround is to decouple the clock in
the domU from the dom0:

In your dom0 and domU /etc/sysctl.conf add the line:
xen.independent_wallclock=1. On the dom0, edit the configuration file
of the domU (e.g. /etc/xen/foobar.cfg and add (or expand) the
extra-line: extra="clocksource=jiffies".

These settings can be activated without rebooting the domU. After
editing the configuration files, issue sysctl -p and echo "jiffies">
/sys/devices/system/clocksource/clocksource0/current_clocksource on
the domU prompt.

Because the clock won't be relying on the dom0 clock anymore, you
probably need to use ntp on the domU to synchronize it properly to the
world.
 

No comments:

Post a Comment