Hi, I''m running some Xen systems with CentOS 5.1 on dom0 (latest 2.6.18-53.1.14.el5xen kernel, xen-3.0.3-41.el5). I have the problem that after rebooting machine (with shutdown -r now) the time in domUs (CentOS 5.1 or Fedora 8 installed using virt-install) that are automatically started is frozen (i mean it stops, when I run ''date'' multiple times you always get the same result). This makes a lot of problems because all sleeps takes forever so processes are hanging. I can''t even shut them out, the only solution is to use ''xm destroy''. What i''ve found out so far is that /etc/init.d/xendomains script is using ''xm pause'' when stopping and ''xm restore'' when starting. This means that all active domUs are paused just before reboot and restored when system is started. Indeed, doing the same manualy gives the same issue. I can pause and restore domUs as many times as I wan''t and it works great but only if I won''t reboot machine between pause and restore. I have this problem on many different machines (from AMD Duron 1200 to Intel Quad Core 2). The only workaround I''ve found is to force /etc/init.d/xendomains script not to pause but shutdown machines when stopping. But i consider my problem as a bug in Xen. Am I the only one having this issue? Is this known issue? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hitting https://bugzilla.redhat.com/show_bug.cgi?id=426861 ? Can be worked around by configuring the guest to sync to ntp after setting up xen.independent_wallclock = 1 to /etc/sysctl.conf and running "sysctl -w" in the guest. --Sadique Krzysztof A. Adamski wrote:> Hi, I''m running some Xen systems with CentOS 5.1 on dom0 (latest > 2.6.18-53.1.14.el5xen kernel, xen-3.0.3-41.el5). I have the problem > that after rebooting machine (with shutdown -r now) the time in domUs > (CentOS 5.1 or Fedora 8 installed using virt-install) that are > automatically started is frozen (i mean it stops, when I run ''date'' > multiple times you always get the same result). This makes a lot of > problems because all sleeps takes forever so processes are hanging. I > can''t even shut them out, the only solution is to use ''xm destroy''. > > What i''ve found out so far is that /etc/init.d/xendomains script is > using ''xm pause'' when stopping and ''xm restore'' when starting. This > means that all active domUs are paused just before reboot and restored > when system is started. Indeed, doing the same manualy gives the same > issue. I can pause and restore domUs as many times as I wan''t and it > works great but only if I won''t reboot machine between pause and > restore. > > I have this problem on many different machines (from AMD Duron 1200 to > Intel Quad Core 2). The only workaround I''ve found is to > force /etc/init.d/xendomains script not to pause but shutdown machines > when stopping. But i consider my problem as a bug in Xen. Am I the only > one having this issue? Is this known issue? > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sadique Puthen wrote:> > Hitting https://bugzilla.redhat.com/show_bug.cgi?id=426861 ? > > Can be worked around by configuring the guest to sync to ntp after > setting up xen.independent_wallclock = 1 to /etc/sysctl.conf and > running "sysctl -w" in the guest.wrong, run "sysctl -p" not "-w".> > --Sadique > > Krzysztof A. Adamski wrote: >> Hi, I''m running some Xen systems with CentOS 5.1 on dom0 (latest >> 2.6.18-53.1.14.el5xen kernel, xen-3.0.3-41.el5). I have the problem >> that after rebooting machine (with shutdown -r now) the time in domUs >> (CentOS 5.1 or Fedora 8 installed using virt-install) that are >> automatically started is frozen (i mean it stops, when I run ''date'' >> multiple times you always get the same result). This makes a lot of >> problems because all sleeps takes forever so processes are hanging. I >> can''t even shut them out, the only solution is to use ''xm destroy''. >> >> What i''ve found out so far is that /etc/init.d/xendomains script is >> using ''xm pause'' when stopping and ''xm restore'' when starting. This >> means that all active domUs are paused just before reboot and restored >> when system is started. Indeed, doing the same manualy gives the same >> issue. I can pause and restore domUs as many times as I wan''t and it >> works great but only if I won''t reboot machine between pause and >> restore. >> >> I have this problem on many different machines (from AMD Duron 1200 to >> Intel Quad Core 2). The only workaround I''ve found is to >> force /etc/init.d/xendomains script not to pause but shutdown machines >> when stopping. But i consider my problem as a bug in Xen. Am I the only >> one having this issue? Is this known issue? >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Krzysztof A. Adamski
2008-May-05 10:59 UTC
Re: [Xen-users] Time freeze in domU after reboot
On Fri, 02 May 2008 18:18:20 +0530 Sadique Puthen <sputhenp@redhat.com> wrote:> > Hitting https://bugzilla.redhat.com/show_bug.cgi?id=426861 ? > > Can be worked around by configuring the guest to sync to ntp after > setting up xen.independent_wallclock = 1 to /etc/sysctl.conf and > running "sysctl -w" in the guest. >Thanks for your answer. The woraround is not working for me however. I did set xen.independent_wallclock = 1 on both dom0 and domU but the problem is still there (the time is frozen). It is very easy to reproduce as it is happening almost each time i reboot dom0. Do you have any other suggestions? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users