[vfio-users] Help Patching Qemu for Vendor

Alex Williamson alex.williamson at redhat.com
Sun May 8 22:58:15 UTC 2016


On Sun, 8 May 2016 17:28:14 -0500
Spam House <kthxplzdie at gmail.com> wrote:

> I will work on the proper cpu setup, thanks for the info. (I copied parts
> of the cpu config from the previous setup however after you showed me the
> issue with vendor id I should probably just redo it to be safe.)
> 
> I will say I don't think I have successfully gotten the HyperV part
> working.
> 
> Is it correct that if my hyperv is spoofed properly I no longer need this
> in my xml?
> 
>     <kvm>
>       <hidden state='on'/>
>     </kvm>
> 
> I can't boot currently without having that in the XML. It would seem
> changing the vendor ID would remove the need for this.

With Hyper-v incorrectly exposed, regardless of exposing KVM, the worst
you should get is a Code 43 in the guest.  It should still boot.
Unhiding KVM for a Windows guest isn't going to enable an performance
features.




More information about the vfio-users mailing list