Comment 19 for bug 1633207

Thanks a lot Guido for your feedback - it helped me better "reading the case".

I see the same issue throughout latest libvirt upstream as of today.
So I'm gonna submit the fix upstream for discussion as I could easily overlook something here.
E.g. parseOpaque is quite close as it is passed up to virDomainDefParseXML, but I think that would be even more misuse than a new flag.

If accepted there (one way or the other) I intend to create a diff to upload for latest Debian and Ubuntu and consider SRUs from there.

The created domain while active has both seclabels and valid content in them just as it had back on libvirt 1.3:
[...]
  <seclabel type='dynamic' model='apparmor' relabel='yes'>
    <label>libvirt-956134c4-d91d-417e-b68f-1d8d492419d6</label>
    <imagelabel>libvirt-956134c4-d91d-417e-b68f-1d8d492419d6</imagelabel>
  </seclabel>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+112:+116</label>
    <imagelabel>+112:+116</imagelabel>
  </seclabel>

@AGX - I'll set you on cc on that upstream discussion.

@IBM - I have a new version (2.1.0-1ubuntu10~ppa5) in the ppa that works for me, It would be great if you could verify this one for you as well.