Comment 17 for bug 1643911

Is this the same bug we saw the other week? I thought Dan B had found a couple of patches missing from the libvirt shipped in Ubuntu which are likely candidates for fixing this. Kashyap, do you have those to hand?

I don't think we're likely to get much traction on this from upstream libvirt because:

* This is not the latest stable release of libvirt.
* They looked anyway, and they think it's fixed in the latest stable release of libvirt.

IOW it's a downstream Ubuntu issue. We need to report this as a bug to Canonical in their package, providing the 2 patches recommended by upstream.