I’ve got a vm configured to pass through a gpu and USB controller. I recently upgraded from a 1070 to a 1080 ti (Asus strix gaming) and as soon as I did that, the vm stopped launching. I’ve experienced this before, but I forget how I solved it in the past.
What’s odd, is libvirt launches a qemu process, and that process pins one thread at 100% until you kill the process. I’m using q35 and ovmf.
I’ve checked all my iommu groupings and they’re correct, and I’ve tried to manually specify a gpu rom file for the 1080 to no avail.
I remember a few years back that fedora provided a bad version of ovmf in the repositories, is that still the case?
I’m not seeing any issues in the logs, so I’m kinda stuck here. If someone can give me a pointer or two, I’ll love you forever.
I’ve seen that before as well, I think I have the same card as you. I haven’t had to specify a ROM file for it. I assume you made the necessary changes for vfio to grab it. Also trying to remember what I’ve done for this before…
[186172.966248] virbr0: port 2(vnet0) entered blocking state
[186172.966250] virbr0: port 2(vnet0) entered disabled state
[186172.966354] device vnet0 entered promiscuous mode
[186172.966671] virbr0: port 2(vnet0) entered blocking state
[186172.966673] virbr0: port 2(vnet0) entered listening state
[186174.999214] virbr0: port 2(vnet0) entered learning state
[186175.110390] vfio_ecap_init: 0000:08:00.0 hiding ecap 0x19@0x900
[186177.047112] virbr0: port 2(vnet0) entered forwarding state
[186177.047123] virbr0: topology change detected, propagating
I’m still looking through your dmesg and gathering info. In the mean time: do you pass a drive through directly to boot into Windows? Or is it a virtual drive? If the former, does the card work when booting directly into Windows? I’ve experienced a similar problem in the past where I needed to just load the card once in Windows natively, then the VM would work. Also, what is the GPU that you’re using for your host? I’m seeing some iffy stuff with linux nvidia drivers here.
I’m sorry I’m not being of much use, but maybe try making a new VM instance and seeing what happens? Oh yeah, and like you said a freshly booted dmesg would be good too.
Also a friend over in the passthrough discord is curious if you’re on the latest BIOS. The Discord invite link is: https://discord.gg/KEXfcc if you want to join. Some people smarter than me in there. I’m not seeing anything overt in the dmesg you provided, though. So I’m kind of at a “throw random things that might work at it stage”. They might have better insight.
Possibly. I did have the windows update ones installed prior to this though.
I’ve got a lot more work on this vm to do. It’s working, mostly, but I need to figure out why I need to kill the “windows device isolation graph” every time I launch a game or it’ll just hang there.
I also need to figure out why certain games simply refuse to launch.
I also need to set up audio passthrough so I don’t have to keep switching my headphones.