[libvirt] [RFC] Question regarding the validity of QEMU capabilities

Pavel Hrdina phrdina at redhat.com
Fri Oct 20 11:10:14 UTC 2017

On Fri, Oct 20, 2017 at 12:59:51PM +0200, Marc Hartmayer wrote:
> Hi all,
> the actual capabilities of QEMU are depending on the host. This
> includes dependencies like which kernel modules are loaded or which
> kernel parameters are used (e.g. kvm.nested). Therefore, after a
> restart we cannot be sure that the QEMU capabilities remain the same.
> How can we solve this problem?


thanks for bringing up this issue, we kind of already know about it
but it's good idea to discuss it publicly.

> I have come up with two ways:
>  - reprobe the capabilities with every host reboot

This is the solution that was agreed on but nobody was motivated enough
to write the code :).

>  - check for every possible change in virQEMUCapsIsValid... (this is
>    already done for KVM). In my opinion this is not the way to go.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20171020/79e601c6/attachment-0001.sig>

More information about the libvir-list mailing list