Re: [libvirt] IPv6 migration

2013-03-21 Thread Daniel P. Berrange
On Thu, Mar 21, 2013 at 01:16:35PM +0100, Ján Tomko wrote: > On 03/21/2013 11:52 AM, Daniel P. Berrange wrote: > > On Tue, Mar 19, 2013 at 03:21:31PM +0100, Jiri Denemark wrote: > >> On Mon, Mar 11, 2013 at 19:40:52 +0100, Ján Tomko wrote: > ... > >> > >> Yeah, I think using an explicit flag would

Re: [libvirt] IPv6 migration

2013-03-21 Thread Ján Tomko
On 03/21/2013 11:52 AM, Daniel P. Berrange wrote: > On Tue, Mar 19, 2013 at 03:21:31PM +0100, Jiri Denemark wrote: >> On Mon, Mar 11, 2013 at 19:40:52 +0100, Ján Tomko wrote: ... >> >> Yeah, I think using an explicit flag would be the best approach. As we >> learnt several times, implementing autom

Re: [libvirt] IPv6 migration

2013-03-21 Thread Daniel P. Berrange
On Tue, Mar 19, 2013 at 03:21:31PM +0100, Jiri Denemark wrote: > On Mon, Mar 11, 2013 at 19:40:52 +0100, Ján Tomko wrote: > > Hello. > > > > We can only tell QEMU on the destination to listen either on IPv6 or on > > IPv4. > > > > If we're supplied with a numeric v6 address, that's the only thing

Re: [libvirt] IPv6 migration

2013-03-19 Thread Jiri Denemark
On Mon, Mar 11, 2013 at 19:40:52 +0100, Ján Tomko wrote: > Hello. > > We can only tell QEMU on the destination to listen either on IPv6 or on > IPv4. > > If we're supplied with a numeric v6 address, that's the only thing we > need to know to set the listen address to [::]. > > For hostnames, we

[libvirt] IPv6 migration

2013-03-11 Thread Ján Tomko
Hello. We can only tell QEMU on the destination to listen either on IPv6 or on IPv4. If we're supplied with a numeric v6 address, that's the only thing we need to know to set the listen address to [::]. For hostnames, we can either assume this based on how it resolves by default on the destinati