Comment 2 for bug 1718133

@James, I found and fixed some of these issues, just look at "fixed in RC" on [1].
Since then all migrations I had worked, we need to find what is special in this case.

When reproducing watch out for:
- do you have the latest qemu /libvirt matching artful or is something left to be promoted to pike?
  Just report libvirt and qemu level and we can compare.
- any apparmor denials to the locking (we generate a k into the rules, but need to check)
- as usual the guest XML as we also found multi-use of an image can be an issue locking it
- as much as possible on the migration type, if you can pull out the virsh migrate (equivalent) command that would be nice
- does it use shared storage or any of the copy-storage options?

[1]: https://wiki.qemu.org/Planning/2.10