@gb.123 said in XCP-ng 8.3 updates announcements and testing:
Here is the summary:
If USB Keyboard & Mouse is passed-through along-with GPU:
The GPU gets stuck in D3 state (on Shutdown/Restart of VM) (Classic GPU reset problem)
If no vUSB is passed but GPU is passed through:
The GPU works correctly and resets correctly (on Shutdown/Restart of VM)
I have no clue what vUSB may change regarding GPU passthrough.
When I run :
$> lspci
Extract of Output (Partial):
07:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b8
However, this controller does not show up when I run :
xe pci-list
Is it a bug that lspci & xe pci-list have different number of devices ?
How can I pass this controller since xe pci-list does not show it so I can't get the UUID ?
Will kernel parameters (like XCP-ng 8.2) work in this case ?
Question for @Team-XAPI-Network regarding the filtering on PCI IDs.
I don't think XAPI allows using arbitrary BDF, but I may be wrong.
Is it safe to run on XCP-ng host ?
echo 1 > /sys/bus/pci/rescan
(I'm trying to find a way where the PCI card is reset by the host without complete reboot, though I am aware that the above command will not reset it.)
Probably. But it's not going to change anything as the device doesn't completely leave the Dom0 when passed-through.
FYI a function-level-reset is systematically performed by Xen when doing PCI passthrough, thus your device should be reset before entering another guest (aside reset bugs like you may have).
Also is it advisable to use :
xl pci-assignable-add 07:00.0
in XCP-ng 8.3 ? or is this method deprecated ?
I don't think XAPI supports this PCI passthrough approach.
This is a command which allows dynamically to remove a device from Dom0 and put it into "quarantine domain", so that it will be ready to passthrough it.
Current XAPI uses the approach of having a set of "passthrough-able" devices at boot time by modifying the xen-pciback.hide kernel parameter, which does the same but at boot time.
