[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] Migration API broken for xenmigr://

On Fri, Jan 30, 2009 at 11:36:16AM -0500, John Levon wrote:
> On Fri, Jan 30, 2009 at 04:19:06PM +0000, Daniel P. Berrange wrote:
> > > > I'm not sure I understand why this is impossible ?
> > > 
> > > I thought the purpose of xenmigr:/// was to allow live migration the
> > > traditional way without needing a remotely accessible libvirtd. At
> > > least, that's how we're using it. If it's the intention of libvirt that
> > > you must always have a listening remote API, then we'll have to work out
> > > a private fix for our tree.
> Could you answer this bit? It sounds like from your other comment that
> the above is true.

Yes, the migrate API requires a connection to both libvirtd daemons,
source and destination.

> We're not going to *require* libvirtd to listen across the network when
> there's an existing mechanism, so it sounds like we'll have to fork this
> part.

You can use the xen+ssh://hostname/  URI for the destination if you don't
want libvirtd to listen publically

|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]