@Andrew thanks for your reply. I have more than enough cores and memory slots for one CPU so I guess I’ll put one of the CPUs in the drawer.

@andyhhp well I took way longer than I said I would, but I promise I still wanna work on this lol. Here is the link to the thread that shows my crash reports. As a reminder, this crash happened on this host randomly and didn't seem directly related to PCI passthrough, or at least not the driver install part which I was having issues with. https://xcp-ng.org/forum/topic/5900/host-crash-once-in-a-long-while

@Darkbeldin let hope I am lucky

@olivierlambert thank you Olivier. Indeed you are right, we need to change also the max vcpu limits in advanced. [image: 1653224017629-0cc87b88-9234-4671-bf18-4280acd996cd-image.png] Then is booting normally.

Hey thanks for the feedback

Sure, Another thing is that included iPXE is a version that does not support multipath SAN boot (I guess it would be nice to update it)

@AndreS That’s great thanks very much AndreS!

If you have a valid XOA license, then you always have the option of opening a support ticket. Anything unusual / different about this VM? How many disks attached? P.S. I assume that you're aware that Windows 2008 isn't officially supported any longer.

@alejandro-anv I have had problems like this on my NFS and iSCSI SR's previously. One thing that might help is to shutdown the VM's before doing a re-scan. If my memory serves me, it does a different kind of coalesce (online vrs offline) and this has a better chance of success. Also, be aware that from the time you re-scan and the time it actually starts to do work on the drives is 5 minutes. When I have a problem like this, I normally ssh into the pool master and tail the logfiles to watch it work. IE: tail -f /var/log/SMlog | grep SMGC Its boring.. But.. it gives me a bit of comfort between prayers 8-)

@olivierlambert said in XCP-ng 8.2 hangs on shutdown: Yes that's what he said (ISO SR in a VM) Ah yes. I see that. Oups.

@Danp I will try to install latest updates

OK @olivierlambert was correct, I mistakenly had enabled secure boot previously before the update so it was already on when I did the reboot. Just tested things in my home lab again and they did NOT change from disabled to enabled, so good to go! Thanks!

@Kaiz I am very much guessing here, but: I don't think you're looking at a single card in this case. Rather must be a switch of some kind involved, which translates between PCI and PCIe and also allows more than one PCI device to be connected to the PCIe bus. And you'd have to remove all devices from the Dom0 (host) add all devices to the DomU (guest) VM (as a list in a single command) lshw may help you figure out the bus topology and device IDs, although none of the Linux tools seem to come close to how HWinfo displays things on Windows. It should definitely help you see things more clearly on the Windows VM, once devices arrive there. If you have any other device, say a spare NIC to test on first, you may be able to save yourself pulling from pulling your hair out.

lshw *-cpu description: CPU product: AMD Ryzen 5 1600 Six-Core Processor vendor: Hynix Semiconductor (Hyundai Electronics) physical id: 13 bus info: cpu@0 version: AMD Ryzen 5 1600 Six-Core Processor serial: Unknown slot: AM4 size: 3200MHz capacity: 3700MHz width: 64 bits clock: 100MHz capabilities: x86-64 fpu fpu_exception wp de tsc msr pae mce cx8 apic mca cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cmp_legacy abm sse4a misalignsse 3dnowprefetch bpext ssbd ibpb vmmcall fsgsbase bmi1 avx2 bmi2 rdseed adx clflushopt sha_ni xsaveopt xsavec xgetbv1 clzero xsaveerptr arat configuration: cores=6 enabledcores=6 threads=12 *-memory description: System Memory physical id: e slot: System board or motherboard size: 32GiB *-bank:0 description: DIMM Synchronous 2667 MHz (0.4 ns) product: 3200 C16 Series vendor: Unknown physical id: 0 serial: 02080314 slot: DIMM 0 size: 8GiB width: 64 bits clock: 2667MHz (0.4ns) *-bank:1 description: DIMM Synchronous 2667 MHz (0.4 ns) product: 3200 C16 Series vendor: Unknown physical id: 1 serial: 11040A1F slot: DIMM 1 size: 8GiB width: 64 bits clock: 2667MHz (0.4ns) *-bank:2 description: DIMM Synchronous 2667 MHz (0.4 ns) product: 3200 C16 Series vendor: Unknown physical id: 2 serial: 020409D2 slot: DIMM 0 size: 8GiB width: 64 bits clock: 2667MHz (0.4ns) *-bank:3 description: DIMM Synchronous 2667 MHz (0.4 ns) product: 3200 C16 Series vendor: Unknown physical id: 3 serial: 11040A26 slot: DIMM 1 size: 8GiB width: 64 bits clock: 2667MHz (0.4ns)

@olivierlambert https://github.com/cert-ee/cuckoo3 you are right. Seems that they are preparing next version. I don't know what hypervisors will work with this. Edit: qemu and kvm.

Hello, Can you with a support client for XCP-ng? (like XO). You can also use xe to see the output.

@stormi Hi, its good to know. Thanks for the answer i think now its solved and explained.