Re: [Xen-devel] DomU clock jumps forward then freezes after Dom0 reboot

[Cédric Schieli <cschieli@xxxxxxxxx>]

Hello,

I can confirm my problem reported here
http://lists.xensource.com/archives/html/xen-devel/2010-10/msg00057.html
is the same.
DomU kernels affected by the migration hang are also affected by the
save/restore hang. Reverting "x86, paravirt: Add a global
synchronization point for pvclock" also fix the save/restore hang.
After doing save/reboot/restore (which led to a hang), migrating it to
a host with a longer uptime will unblock the domain, but the wallclock
will be several hours forward. Migrating back will block again.

Regards,
Cédric Schieli

2010/10/19 Olivier Hanesse <olivier.hanesse@xxxxxxxxx>:
> Hello,
>
> I think I got exactly the same bug.
>
> After a reboot, all my DomU are stuck during X min ,  where X was the
> "uptime" of the dom0 before reboot.
>
> Save/Restore without reboot works perfectly.
>
> I am running Debian Lenny with backports :
>
> ii  xen-hypervisor-4.0-amd64                    4.0.1-1
> The Xen Hypervisor on AMD64
> ii  linux-image-2.6.32-bpo.5-xen-amd64          2.6.32-23~bpo50+1
> Linux 2.6.32 for 64-bit PCs, Xen dom0 suppor
>
> Any ideas ?
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel