[Pkg-libvirt-maintainers] Bug#778235: Bug#778235: libvirt0: Migration drops elements from XML

[Martin Sofaru]

On 12/02/15 16:02, Guido Günther wrote:
> On Thu, Feb 12, 2015 at 02:54:20PM +0100, Martin Sofaru wrote:
>> Package: libvirt0
>> Version: 1.2.9-9
>> Severity: important
>> Tags: patch
>>
>> Dear Maintainer,
>>
>>
>> when migrating a VM the actual XML "virsh dumpxml <vm>" is copied to the
>> target host. This drops important elements like portgroups out of a
>> network configuration.
> 
> You don't provide much information. Which elemnts are wrong for you
> (e.g. provide a diff and the original configuration).

The origin XML (--inactive) looks like this:

    <interface type='network'>
      <mac address='52:54:00:12:34:56'/>
      <source network='ovs' portgroup='foo'/>
      <target dev='bar'/>
      <model type='virtio'/>
      <driver name='vhost'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
    </interface>

After migration the origin XML (--inactive) becomes the same as the
actual XML (without --inactive):

    <interface type='bridge'>
      <mac address='52:54:00:12:34:56'/>
      <source bridge='br0'/>
      <virtualport type='openvswitch'>
        <parameters interfaceid='60cd8a2e-c182-44d1-b613-32a8a042bf9e'/>
      </virtualport>
      <target dev='bar'/>
      <model type='virtio'/>
      <driver name='vhost'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
    </interface>

The information about the portgroup is lost after migration!

> Did you check that the patch fixes your problem?

No. I originally reported the issue to libvirt upstream and was told the
issue was fixed with that commit.

I am trying to verify if this single commit is enough to fix the issue.

Kind regards,

Martin