May 10 08:50:30 bullseye kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vif16.0: link becomes ready May 10 08:50:30 bullseye kernel: vif vif-16-0 vif16.0: Guest Rx ready May 10 08:50:03 bullseye kernel: pciback 0000:00:02.0: xen_pciback: vpci: assign to virtual slot 2 May 10 08:50:03 bullseye kernel: pciback 0000:00:14.0: xen_pciback: vpci: assign to virtual slot 1
May 10 08:50:03 bullseye kernel: pciback 0000:00:1b.0: xen_pciback: vpci: assign to virtual slot 0 Start a bullseye Xen HVM configured for PCI/VGA passthrough using the bullseye Xen and Qemu packages for bullseye on Dom0 (Haswell Intel IGD + audio device + USB 3.0 controller): May 9 10:52:20 bullseye kernel: Command line: placeholder root=/dev/debian/bullseye ro reboot=bios quiet console=tty1 console=hvc0 Kernel logs (problems reported in Dom0's syslog when trying to start this Debian bullseye Xen HVM DomU with Xen VGA/PCI passthrough configured): On Dom0, the Xen commandline and version (from xl dmesg):ĭom0_mem=2G,max:2G smt=false pv-l1tf=false iommu=1 no-real-mode edd=off
Qualcomm atheros ar9287 upstream range windows#
I would expect both Windows and Linux HVMs to work comparably well. But with buster and bullseye running as the Dom0, I can only get the VGA/Passthrough feature to work with Windows Xen HVMs. I have been using Xen's PCI and VGA passthrough feature since wheezy and jessie were the stable versions, and back then both Windows HVMs and Linux HVMs would function with the Intel Integrated Graphics Device (IGD), the audio device, and the USB 3 controller passed to them.