Re: [Xen-devel] HVM Migration of domU on Qemu-upstream DM causes stuck system clock with ACPI

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2013-05-29 at 17:16 +0100, Alex Bligh wrote:
> --On 28 May 2013 16:06:19 +0100 Diana Crisan <dcrisan@xxxxxxxxxxxx> wrote:
> 
> >>>>> FWIW it's reproducible on every host h/w platform we've tried
> >>>>> (a total of 2).
> >>>> Do you see the same effects if you do a local-host migrate?
> >>> I hadn't even realised that was possible. That would have made testing
> >>> live migrate easier!
> >> That's basically the whole reason it is supported ;-)
> >>
> >>> How do you avoid the name clash in xen-store?
> >> Most toolstacks receive the incoming migration into a domain named
> >> FOO-incoming or some such and then rename to FOO upon completion. Some
> >> also rename the outgoing domain "FOO-migratedaway" towards the end so
> >> that the bits of the final teardown which can safely happen after the
> >> target have start can be done so.
> >>
> >
> > I am unsure what I am doing wrong, but I cannot seem to be able to do a
> > localhost migrate.
> >
> > I created a domU using "xl create xl.conf" and once it fully booted I
> > issued an "xl migrate 11 localhost". This fails and gives the output
> > below.
> >
> > Would you please advise on how to get this working?
> 
> Any ideas?

The usual questions: What does "xl -vvv ... " say? Is there anything of
interest under /var/log/xen/* (any variant of the domain's name)?

It might also be useful to patch tools/libxl/xl_cmdimpl.c:main_migrate()
to add -vvv to the receive side as well (yes, we should plumb that in
properly).

Ian




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel