Re: [libvirt] [PATCH] conf: Don't use the current state in def-data.network.actual when migrate

2015-01-07 Thread Jiri Denemark
On Thu, Dec 25, 2014 at 11:38:00 +0800, Luyao Huang wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1177194 When migrate a vm, we will generate a xml via qemuDomainDefFormatLive and pass this xml to target libvirtd. Libvirt will use the current network state in def-data.network.actual to

Re: [libvirt] [PATCH] conf: Don't use the current state in def-data.network.actual when migrate

2015-01-07 Thread lhuang
On 01/07/2015 08:16 PM, Jiri Denemark wrote: On Thu, Dec 25, 2014 at 11:38:00 +0800, Luyao Huang wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1177194 When migrate a vm, we will generate a xml via qemuDomainDefFormatLive and pass this xml to target libvirtd. Libvirt will use the current

[libvirt] [PATCH] conf: Don't use the current state in def-data.network.actual when migrate

2014-12-24 Thread Luyao Huang
https://bugzilla.redhat.com/show_bug.cgi?id=1177194 When migrate a vm, we will generate a xml via qemuDomainDefFormatLive and pass this xml to target libvirtd. Libvirt will use the current network state in def-data.network.actual to generate the xml, this will make migrate failed when we set a