Rudi (ryjelsum)i can apparently eject my gpu??? hello????
it just disappeared completely and went outie but somehow the hdmi audio is still hanging on
the funny thing is this may actually be legitimately useful for me due to that issue i was just discussing with spice, because the root of the issue is essentially having two display adapters
now if i can just figure out how to reattach it... but knowing windows the answer is probably something insane
Baral'heia Stormdancer ΘΔ🐲@rudi Reboot ought to fix it tbh
@baralheia oh yeah rebooting makes it all show up again, dynamically reattaching it would just be useful for working around this issue in SPICE that makes the mouse cursor god damn disappear in windows when there's a secondary display alongside the QXL one.
but it's like, not really a huge issue lol, i can just turn off a lot of the spice fanciness and it's not really an issue, and trying to run the virtual display adapter alongside the gpu is a bit weird in the first place
since this post is escaping containment and what im referencing is long past: the issue i'm referencing is like.. spice basically isn't able to draw the mouse cursor over the virtual machine's screen for some reason when windows has more than one attached display adapter but it seems to do the guest-side hiding of the mouse cursor that it would normally do? something like that?
it caused an issue for citrix users and i think the fix for it that they implemented was to specifically blacklist/whitelist the citrix display adapter in some spice/virtio guest tools component which didn't address the root of the issue but they closed the issue nonetheless. i did not really want to register an account on their gitlab/whatever instance so i kinda just left it there at knowing what the problem even is
i had to do weird things to get the virtual display adapter to work alongside the passed through GPU in the first place though, i'm just kind of asking for problems with that
Tanganronpa@rudi Yes weirdly enough the audio device is its own PCI device, but in the same IOMMU group. I had to passthrough it as well in Proxmox.