Image hide_hypervisor_id property helps libvirt set an xml instance file property, which will hide on guest host KVM hypervisor signature ("KVMKVMKVM\0\0\0"). According to the commit message in QEMU repository [1]:
"The latest Nvidia driver (337.88) specifically checks for KVM as the hypervisor and reports Code 43 for the driver in a Windows guest when found. Removing or changing the KVM signature is sufficient for the driver to load and work."
Some hypervisors add a signature to their guests. While the presence of the signature can enable some paravirtualization features on the guest, it can also have the effect of preventing some drivers from loading. Hiding the signature by setting this property to true may allow such drivers to load and work.
Although, isn't there a workaround for this?
https:/ /review. openstack. org/#/c/ 459753/
From that patch:
Image hide_hypervisor_id property helps libvirt set an xml instance file property, which will hide on guest host KVM hypervisor signature ("KVMKVMKVM\ 0\0\0") . According to the commit message in QEMU repository [1]:
"The latest Nvidia driver (337.88) specifically checks for KVM as the hypervisor and reports Code 43 for the driver in a Windows guest when found. Removing or changing the KVM signature is sufficient for the driver to load and work."
Also mentioned here:
https:/ /docs.openstack .org/python- glanceclient/ latest/ cli/property- keys.html
img_hide_ hypervisor_ id:
Some hypervisors add a signature to their guests. While the presence of the signature can enable some paravirtualization features on the guest, it can also have the effect of preventing some drivers from loading. Hiding the signature by setting this property to true may allow such drivers to load and work.