Re: [Xen-devel] Test report: Migration from 4.1 to 4.2 works

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Fri, 2012-08-31 at 14:11 +0100, Jan Beulich wrote:
> >>> On 31.08.12 at 15:01, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> > On Fri, 2012-08-31 at 12:30 +0100, Jan Beulich wrote:
> >> >>> On 31.08.12 at 13:04, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> >> > Migration 4.1 xend -> 4.2 xl
> >> >   Needs to be done with xl
> >> >   Stop xend on source, which leaves domain running and manipulable by xl
> >> >   xl migrate -C /etc/xen/debian.guest.osstest.cfg domain potato-beetle
> >> >   Works.
> >> 
> >> Is that really an acceptable approach? What if you have multiple
> >> VMs running, and want to migrate just part of them? All the other
> >> would remain unmanageable at least for the duration of the
> >> migration(s). (And I also wonder if 4.1's xl is complete/stable
> >> enough to recommend such an approach as a general mechanism.)
> > 
> > The alternative I suppose would be to:
> >       * start xend on new host (running 4.2)
> >       * migrate the domains you want over to the new system
> >       * stop xend on the new host
> >       * xl migrate localhost for each domain.
> 
> So why is it that xend and xl can't talk to each other for a migration?

The wire protocol is different, also xend doesn't know how to start the
xl receive process on the other end.

I suppose we could implement xl migrate-receive-from-xend which the user
could manually run on the target. Bit late for 4.2 though.

Ian.


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