As probably one of the most weird ways to solve this problem, I've decided to chainload #grub2 from iPXE and learned a bit! 🧵
I wish this post by the Xen Project existed years ago when I was trying to understand the differences between Xen and KVM. Would have been a great jumping point to dig deeper.
https://xenproject.org/blog/xen-at-fosdem-real-world-conversations-about-xen-and-kvm/

We just wrapped up a weekend at FOSDEM 2026 where Xen and XCP-ng both had dedicated booths. This was my first time at FOSDEM and the legend lived up to the hype. It was an insightful weekend full of interesting folks who were genuinely interested in the Xen Project. Everything
til alpine has setup-xen-dom0
So back on #QubesOS / #Xen. There is definitely something wrong with how it forwards the A380 into the #windows VM.
Now that I've remote desktop enabled (and can conenct with the A380 disconnected just fine) I now can also see a black screen via RDP when the A380 is passed into it.
(Note: passing the two end devices, aka the one for the video and the one for the audio of the A380 worked just fine in KVM on #NixOS. So it is something Xen/QubesOS does that breaks it...
So rebooted into NixOS and after having compiled some food I've tried passing through the end devices using KVM. And well it works with KVM. So what is wrong with my #QubesOS aka. #Xen config then?
Also because I thought it was funny I also tried attaching the Intel A380 to a windows XP VM.
The generic driver for the video card doesn't work.
It has a generic audio driver that almost works. It matches the device but fails to start :p
Sooo are we just going to ignore the vulnerability qsb-091-2023 "Xen Security Notice 1: winpvdrvbuild.xenproject.org potentially compromised"?
I do not see any more recent build of the XEN Windows PV Drivers.
Even the ones linked on the website https://xenproject.org/resources/downloads/ right now are only from 2023-07-13. Which is 11 days before that vulnerability was published.
Also the part that they replaced the executables with a warning text doesn't seem to apply to that website either...