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]
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: libvirt/ qemu/<guestname >.log
- To use the workaround you have to check your log usually in /var/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 /gist.github. com/anonymous/ a2ce3cbf7878995 537212f0dafd06d 99 /gist.github. com/anonymous/ 07a357af9e34172 b60c83d410fe63f dd
[2]: https:/
[3]: https:/