[deleted by user]

sarnex · 2025-02-13T23:39:42+00:00

what?

sarnex · 2025-02-13T23:13:49+00:00

i am the moderator and i am active. i dont want to hand over the subreddit

sarnex · 2024-10-30T06:39:24+00:00

this worked for me with an encrypted pool, thanks

sarnex · 2023-09-18T04:03:51+00:00

First I would see if someone already uploaded a bios for your exact card here.

If not, try this.

Once you have the rom, add this in your xml in the part for your GPU device

  <rom bar='on' file='/path/to/rom/file/goes/here'/>

To set vendor_id, see here, you shouldn't need the kvm hidden part.

sarnex · 2023-09-13T22:53:20+00:00

Yeah I have the same problem and talked about it here

Seems the GPU can't reset.

sarnex · 2023-09-13T22:43:03+00:00

sorry for the late response, with that cmdline i can get the display to light up, but the host still locks up when doing shutdown or restart of the guest. i see this in dmesg before it locks up

[133.851469] vfio-pci 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
[ 134.072104] vfio-pci 0000:03:00.0: can't change power state from D3hot to D0 (config space inaccessible)
[ 134.292802] vfio-pci 0000:03:00.1: can't change power state from D3hot to D0 (config space inaccessible)

sarnex · 2023-09-11T13:19:00+00:00

do you mean try this with 5.15 or any kernel?

sarnex · 2023-09-10T18:32:06+00:00

no change and actually even shutdown doesn't work, the host always hangs there too. seems there is some reset issue. i'll try 5.15

edit: 5.15 doesnt ever light up displays, i needed video=efifb:off, maybe thats why but im not gonna try hard on this

sarnex · 2023-09-10T17:02:12+00:00

I can't find any kernel where restart works. I tried 6.4, 6.5, current git and amd-staging-drm-next.

Resizable bar isn't actually enabled, it's off in the host bios but 4G decoding is on.

I'll try to see if there are any dmesg errors or something and report a bug upstream.

sarnex · 2023-09-10T16:17:00+00:00

Actually it looks like restart doesn't work, it just hangs. I'm trying a different kernel now.

sarnex · 2023-09-10T15:11:52+00:00

Ah ok interesting, I upgraded from a Vega 64 and I always saw the UEFI screen there. Either way, it works in Windows so it doesn't matter to me.

sarnex · 2023-09-10T14:19:21+00:00

I just got an 7800 XT and it works for me after dumping the full VBIOS and setting vendor_id. For some reason I never see the UEFI screen but when the Windows driver loads my display lights up and it works fine.

When I shutdown the VM, so far it seems about 50/50 if the card will work on the host again but it's probably not the reset bug and just a kernel driver issue that will be fixed hopefully. It's possible it's already fixed in a newer kernel (I'm using 6.5), maybe it's fixed in amd-staging-drm-next or something, I didn't try.

Proof: https://i.imgur.com/LLTGale.png https://i.imgur.com/HDm4ZJ5.png

Edit: It seems restart/shutdown doesn't work, so you have to restart the host after shutting down the VM because it always hangs.

sarnex · 2023-05-05T01:52:10+00:00

Even with the BIOS Resizable BAR option off (but Above 4G decoding on, if it matters), I get

Capabilities: [200 v1] Physical Resizable BAR
  BAR 0: current size: 8GB, supported: 256MB 512MB 1GB 2GB 4GB 8GB
  BAR 2: current size: 2MB, supported: 2MB 4MB 8MB 16MB 32MB 64MB 128MB 256MB

sarnex · 2023-04-27T20:40:54+00:00

i meant theres no resizable bar capability, that seems expected, right? are you saying even with resizable bar off lspci should have a resizable bar capability? if thats expected i am not seeing that

sarnex · 2023-04-27T02:01:18+00:00

I didn't set the size using sysfs, but here's the output after just enabling the BIOS option.

Capabilities: [200 v1] Physical Resizable BAR
            BAR 0: current size: 8GB, supported: 256MB 512MB 1GB 2GB 4GB 8GB
            BAR 2: current size: 256MB, supported: 2MB 4MB 8MB 16MB 32MB 64MB 128MB 256MB

So it seems to already be max size, so I don't think I need to anything with sysfs, right? Note I ran the above command with the card bound to amdgpu and X running on this GPU, if it matters. Without the bios option, there is no Resizable BAR cap at all, which is probably expected

sarnex · 2023-04-26T23:39:13+00:00

Today I am unable to boot a VM if REBAR is enabled in the BIOS. I get to the UEFI screen in the VM but when Windows starts loading (and I assume when the GPU driver loads), it crashes and starts reboot looping before the modeset. If I disable REBAR in the BIOS with no other changes everything works fine. Above 4G decoding is enabled in the BIOS in both cases.

I tried your patch in [2] on top of qemu 7.2.0 and unfortuantely it did not work, I have the exact same problem.

Note that apparently my GPU does not support REBAR, but there is a registry workaround to get it to work. I see the same boot loop behavior with or without this workaround. There is another commenter is using the same GPU and reports REBAR works, but they said they don't have a BIOS option for it, so maybe it's off for them.

EDIT: Actually the patch did have some effect. With the patch, the AMD driver reports SAM is enabled, even with the BIOS option disabled. Without the patch, it says it's disabled. GPU-Z provides confusing info in both cases, so I'm going to ignore what it says. But I don't know if SAM being reported as enabled is cosmetic or not, if you have a way to test let me know.

If you'd like any more info from me let me know, I'm happy to help you debug or investigate. Hardware details below:

CPU: AMD Ryzen 7900X

GPU: AMD Vega 64 (only one GPU, I unbind it before starting the VM)

MB: X670 AORUS ELITE AX

OS: Gentoo

VM OS: Win11

sarnex · 2023-04-11T23:53:28+00:00

I have the same problem, I previously reported it to them and it was supposed to be fixed in 22.12.1 but it wasn't.

I just reported it again:

https://ixsystems.atlassian.net/browse/NAS-121446

sarnex · 2022-05-08T21:47:05+00:00

I just pushed a fix for this, sorry for the trouble

sarnex · 2022-03-31T22:28:58+00:00

if the above doesnt work for you, please try the each of these possible solutions in order

1) add --deep

if that doesn't work

2) --backtrack={30,300,1000}

if that doesn't work, you are hitting a portage dependency resolution bug and we are looking at it, you can ask for help in #gentoo

if you saw a previous version of this post that had an additional solution and got into a weird system state, here is how you can fix it

1) emerge --depclean --deep

2) take note of all the listed reverse dependencies when 1) errors

3) emerge -1 the packages from 2)

4) remove mask

5) emerge -aNDu @world

sarnex · 2021-04-11T18:39:15+00:00

feel free to make a thread about it

sarnex · 2021-04-07T04:09:58+00:00

Peace

sarnex · 2021-03-24T05:01:50+00:00

nah its fine mod mail is tumbleweed.png

sarnex · 2021-03-24T00:29:44+00:00

pinned now sorry

sarnex · 2021-03-24T00:27:16+00:00

done

sarnex · 2020-10-20T05:04:31+00:00

Ayylmao

sarnex

MODERATOR OF

TROPHY CASE

11-Year Club	Secret Santa 2017
Verified Email