Bug#507785: xen-linux-system: Xen domU clock frozen on dom0 boot
When dom0 boots up, all restored domUs (2 x etch and 1 x lenny) have their clocks set to the time when they were restored and their
clocks are "frozen" in that time, with following error appearing in all domUs' dmesg:
clocksource/0: Time went backwards: ret=b01d2985eb delta=-929476120446 shadow=b00552031d offset=17d7f610
(ret, delta, shadow and offset vary over time)
"xm destroy domU && xm create domU.cfg" seems to fix the problem, but only until I reboot/shutdown dom0 again.
Manual "/etc/init.d/xendomains restart" doesn't fix the problem, but it doesn't reintroduce it either once the domUs have been manually
recreated with xm destroy/create.
This happens on every dom0 boot.
domU.cfg (Created with xen-tools, other domUs have pretty much similar config. "virtual" is the name of LVM VG.):