And there it went again... GRMBL!! [52968.000183] clocksource/0: Time went backwards: delta=-6917295094804713137 shadow=52968000043427 offset=136671 [52968.000305] clocksource/0: Time went backwards: delta=-6917295094804588934 shadow=52968000043427 offset=260563 [52968.000367] clocksource/0: Time went backwards: delta=-6917295094804526915 shadow=52968000043427 offset=322560 [52968.000424] clocksource/0: Time went backwards: delta=-6917295094804470423 shadow=52968000043427 offset=379055 [52968.000480] clocksource/0: Time went backwards: delta=-6917295094804413766 shadow=52968000043427 offset=435720 [52968.000536] clocksource/0: Time went backwards: delta=-6917295094804357638 shadow=52968000043427 offset=491848 [52968.000592] clocksource/0: Time went backwards: delta=-6917295094804301540 shadow=52968000043427 offset=547946 [52968.000830] clocksource/0: Time went backwards: delta=-6917295094804064372 shadow=52968000043427 offset=785148 [52968.000891] clocksource/0: Time went backwards: delta=-6917295094804003241 shadow=52968000043427 offset=846275 [52968.000948] clocksource/0: Time went backwards: delta=-6917295094803946487 shadow=52968000043427 offset=902991
only xm destroy works to get the domU back on track.. Xen 3.1.1 is released, maybe that will help? I have the feeling we shouldn't get our hopes up for having this fixes through this bugreport, echo'ing in /dev/null will have more effect i'm afraid :) -- Xen guest suspend causes clock to stop https://bugs.launchpad.net/bugs/146924 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
