[vfio-users] GTX1060 Passthrough Error Code 43

Robert Coldbird gentleman.trilby at gmail.com
Sun Oct 30 01:03:47 UTC 2016

Turns out that some host mainboards are extremely picky about interrupts.
After several days of investigating and debugging, I've discovered that to
get the GTX1060 going in my VM, I had to do a trifold of things:

1. Hide KVM in my virtxml.
2. Rename the hyperv cpu id to "none".
3. Right after installing the NVidia driver, I had to mod the registry for
both the GPU and the HDMI sound card to use MSI interrupts.

The deciding factor, or rather the unknown in this situation was number 3,
as the first two are well documented and known to be required for NVidia
graphic cards to operate properly on the NVidia proprietary driver.

Didn't think though that number 3 would be yet another requirement, as its
often just mentioned as an optional thing to do to get rid of HDMI audio

Fact remains though, without number 3 the graphic card would not come up
successfully, and instead bluescreen.

I guess this thread can be considered as solved now, although I really wish
that this hint would of been part of the vfio blog's mentions.

On Sun, Oct 30, 2016 at 2:17 AM, Eddie Yen <missile0407 at gmail.com> wrote:

> IME, it's easily get Code 43 if you also included virtual display in you
> VM. No matter what kind of virtual display you use.
> Also which guest OS you're using? It also happened if using Windows 7.
> 2016-10-29 2:45 GMT+08:00 Robert Coldbird <gentleman.trilby at gmail.com>:
>> I've followed the usual suggestions for making the NVidia drivers comply,
>> and none yielded useable results so far.
>> I've disabled the kvm tag, changed the hyperv cpu id tag and even dumped
>> the cards vbios and attached it to the passthrough.
>> All of these changes showed no visible change to the way the driver
>> reacted to my VM.
>> The gpu works fine as long as I run the windows VGA default driver but
>> the instant the NVidia driver is installed it bluescreens in the usual code
>> 43 fashion.
>> Code 43 was verified afterwards using a spice / qxl display.
>> In addition to that I've written a small C++ tool in Visual Studio to
>> verify that the kvm tag and hyperv cpu id tags are hidden, and indeed, they
>> are.
>> This shows me that, despite all of the usual options being enabled and
>> proven working, there is still something left in the setup that allows the
>> NVidia driver to detect the VM environment.
>> Does anyone of you guys have a clue as to what might be wrong here?
>> _______________________________________________
>> vfio-users mailing list
>> vfio-users at redhat.com
>> https://www.redhat.com/mailman/listinfo/vfio-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20161030/8ad887ae/attachment.htm>

More information about the vfio-users mailing list