Comment 26 for bug 146924

Thanks Bart, setting clocksource to jiffies fixed "Time went backwards" error in my domU!
However, domU clock still goes back if I reboot dom0 (domUs are saved and restored by /etc/init.d/xendomains script).
But this time, nothing freezes, no kernel messages, just 'date' command and timestamps in the log files show the wrong time.
How long the clock goes back is related to uptime of dom0 (or maybe hypervisor).
When I reboot dom0 when uptime is 15 minutes , and domU restores at 30 seconds of uptime of rebooted dom0, the clock inside domU is 14m30s behind.

So I tried setting independent_wallclock to 1 too.
And now the clock does not goes back anymore!
Instead, clock is suspended while domU is suspended.
This is far better than clock going back.
Running ntpd in domU fixes the clock.