-
-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code 43 in guest when passing through NVIDIA GPU #34
Comments
I see the split lock detection triggers in your dmesg log. That will cause issues for the VM, up to the point where it may not make any progress. I am not sure whether that is the root cause of your issue, but please try the recommendation from the README and see if it helps:
|
I was pretty sure I had already disabled it. But, either way, adding the command line parameter didn't do anything, although I now see this in
But I also see |
@snue is correct. Here we have it
Yes, this is expected.
Sounds about right. Did it solve your issue? |
Unfortunately, it didn't solve the issue. |
@AnErrupTion can you post new logs with split lock disabled? |
Ah yes, my bad. Here they are: |
It looks a little bit better and the guest is definitively trying to use the GPU:
and
I assume this card needs some kind of quirk. I can maybe look into this in a couple of weeks. Can you upload the output of |
I'm not sure if it does, since passing through the same GPU with QEMU works just fine (no additional quirks needed or shenanigans).
Alright, here's the output (when ran as root): lspci.log |
Qemu automatically applies the necessary quirks when it detects a card that needs them |
Is there a way of knowing which ones does it apply? I can fire up a QEMU VM if needed. |
Also, I guess I forgot to mention one interesting bit: when I went to check for updates in the VM, Windows Update did not download the NVIDIA driver and I had to download it manually (but then it installed fine afterwards). And, when I went to Device Manager, it said that the driver used is not the same one as the POSTed graphics driver, or something like this. None of this happened with QEMU either. |
There are quite some nvidia quirks in QEMU. Just maybe, you can force the GPU into legacy interrupt mode instead of MSI in the Windows VM to try and work around that? |
I have tried to disable MSI by setting |
Bug Description
When following the guide over here, adapting it to passthrough a dedicated GPU, a code 43 error can be observed after installing the GPU drivers in the guest system using Device Manager.
How to Reproduce
vfio-pci
is correctly bound to the GPU/etc/security/limits.conf
/dev/vfio/*
--attachvfio
VM configuration
Guest OS configuration details:
VirtualBox VMs/<guest VM name>/<guest VM name>.vbox
: Windows 11.vbox.zipHost OS details:
Linux shininglea 6.10.4-arch2-1 #1 SMP PREEMPT_DYNAMIC Sun, 11 Aug 2024 16:19:06 +0000 x86_64 GNU/Linux
Logs
The text was updated successfully, but these errors were encountered: