We had a discussion today on how to workaround if you drive qmeu via libvirt. While discussions often and up at the correctness of such setups they exists, I think it is worth to document until libvirt supports that officially.
TL:DR: - no native libvirt feature yet - discussions if <shareable/> should set it - workaround available via cmdline Details on the workaround: - To use the workaround you have to check your log usually in /var/log/libvirt/qemu/<guestname>.log - Get the id of the device that matters to you - then use [1] to tweak qemu cmdline - example is from [2] to [3] [1]: http://blog.vmsplice.net/2011/04/how-to-pass-qemu-command-line-options.html [2]: https://gist.github.com/anonymous/a2ce3cbf7878995537212f0dafd06d99 [3]: https://gist.github.com/anonymous/07a357af9e34172b60c83d410fe63fdd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716028 Title: qemu 2.10 locks images with no feature flag To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1716028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
