@stormi Thanks! @olivierlambert @TeddyAstie I am unable to test further since I don't have a 'passable'/'assignable usb controller which can be passed through. Have ordered one and would keep you guys posted once I get it and test it. Though I can confirm that the bug (dunno if it is the driver / xcp-ng) persists.

@gb.123 Interesting -- alert the XCP-ng team to take a closer look, if they haven't seen this already.

Adding @stormi

@gb-123 AFAIK the host doesn't call XO, if you shut XO off, the private network would continue to work but its state wouldn't change. It means if you restart an host etc the connection to this host would be lost. The logs depends on how your installed XO or XOA etc so you might want to go through our doc! Cheers

I think this would be awesome, if it's not too much work, would love to see it.

@john-c said in USB Passthrough Override Script - to ensure usb-policy.conf consistency: This is no longer needed if you have Xen Orchestra version 5.93 or later, alternatively if using in home lab and from source then any commit dated after 29th March 2024 (or current head on GitHub Main - Master). The reason being that Xen Orchestra from version 5.93 has official support for USB Passthrough and later from version 5.95 you can do PCI Passthrough. This is unfortunately still needed, as otherwise the XO simply does not show the PUSB in the host, so it cannot be assigned as a VUSB for the VM. @zeropointer thanks for the idea, this seems to be the most pragmatic solution.

Hi! The issue should be resolved on the branch fix-smb-storage

HA is enabled at the pool level. Read this blog post I wrote 9 years ago but still relevant: https://xen-orchestra.com/blog/xenserver-and-vm-high-availability/