@TeddyAstie I hadn't seen anything special was needed in a VM other that a kernel new enough for support which 6.17 has, is there more to the story with adding things to Ubuntu?

@JamesG I'll have to pickup another one to test, I did check all my BIOS settings, rebar was enabled, and everythign else was set right, me and another guy both tried for weeks and nowhere, both of us have Threadripper 7xxx series on Supermicro boards for xcpng hosts. I don't think I ever updated the firmware on the card, I picked up the card right when it launched.

@olivierlambert I'm willing to go procure another to try to troubleshoot, 2 of us tried 3 different cards on different servers and spent a lot of time and never got anywhere with the cards. This is some messages I still have have from back when I was trying. More or less, XCPNG could see the cards, they could be passed to a VM either in XO or CLI, we tried a couple different linux VM's on 6.17 kernel and would get errors like below, I also tried a windows VM and it couldn't identify the card at all, tried latest intel drivers, etc.

[    3.109115] xe 0000:00:08.0: [drm] Found battlemage (device ID e212) discrete display version 14.01 stepping B0
[    3.110277] xe 0000:00:08.0: Direct firmware load for xe/bmg_guc_70.bin failed with error -2
[    3.110281] xe 0000:00:08.0: [drm] GuC firmware xe/bmg_guc_70.bin: fetch failed with error -2
[    3.110283] xe 0000:00:08.0: [drm] GuC firmware(s) can be downloaded from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
[    3.110284] xe 0000:00:08.0: [drm] *ERROR* GT0: GuC init failed with -ENOENT
[    3.110299] xe 0000:00:08.0: [drm] *ERROR* GT0: Failed to initialize uC (-ENOENT)
[    3.110526] xe 0000:00:08.0: probe with driver xe failed with error -2

@sanjay Kinda bringing this back, does anyone know if or when support for newer Intel cards like B60+ will be added in XCP-NG? I can only assume there's something that doesn't support these cards in the kernel possibly?

Me and another user bought B50's on release day and tried them and neither of us could get them to function, you could kinda see them in the VM passed through but they were non-functional, even on the latest ubtuntu developer kernels. It felt like the cards simply weren't supported on xcpng.

[{"name": "CPU Temp", "value": "39 degrees C", "event": "ok"}, {"name": "System Temp", "value": "31 degrees C", "event": "ok"}, {"name": "Peripheral Temp", "value": "46 degrees C", "event": "ok"}, {"name": "NIC Temp", "value": "59 degrees C", "event": "ok"}, {"name": "CPU_VRM0 Temp", "value": "43 degrees C", "event": "ok"}, {"name": "CPU_VRM1 Temp", "value": "34 degrees C", "event": "ok"}, {"name": "SOC_VRM Temp", "value": "44 degrees C", "event": "ok"}, {"name": "VDDIO_VRM Temp", "value": "48 degrees C", "event": "ok"}, {"name": "DIMMA~C Temp", "value": "45 degrees C", "event": "ok"}, {"name": "DIMME~G Temp", "value": "44 degrees C", "event": "ok"}, {"name": "MB 12V", "value": "12.08 Volts", "event": "ok"}, {"name": "MB 5VCC", "value": "5.10 Volts", "event": "ok"}, {"name": "MB 3.3VCC", "value": "3.35 Volts", "event": "ok"}, {"name": "VBAT", "value": "0x04", "event": "ok"}, {"name": "MB 5VSB", "value": "5.06 Volts", "event": "ok"}, {"name": "MB 3.3VSB", "value": "3.39 Volts", "event": "ok"}, {"name": "MB 1.8VSB", "value": "1.84 Volts", "event": "ok"}, {"name": "BMC 2.5V", "value": "2.47 Volts", "event": "ok"}, {"name": "BMC 1.8V", "value": "1.77 Volts", "event": "ok"}, {"name": "BMC 1.2V", "value": "1.19 Volts", "event": "ok"}, {"name": "BMC 1.0V", "value": "0.99 Volts", "event": "ok"}, {"name": "BMC 3.3VSB", "value": "3.28 Volts", "event": "ok"}, {"name": "CPU_SOC", "value": "1.22 Volts", "event": "ok"}, {"name": "CPU_VDDIO", "value": "1.12 Volts", "event": "ok"}, {"name": "FAN1", "value": "2100 RPM", "event": "ok"}, {"name": "FAN2", "value": "1960 RPM", "event": "ok"}, {"name": "FAN3", "value": "2100 RPM", "event": "ok"}, {"name": "FAN4", "value": "no reading", "event": "ns"}, {"name": "FANA", "value": "no reading", "event": "ns"}, {"name": "FANB", "value": "no reading", "event": "ns"}, {"name": "FANC", "value": "no reading", "event": "ns"}, {"name": "M2_SSD1 Temp", "value": "no reading", "event": "ns"}, {"name": "M2_SSD2 Temp", "value": "no reading", "event": "ns"}, {"name": "Chassis Intru", "value": "0x00", "event": "ok"}, {"name": "NVMe_SSD1 Temp", "value": "no reading", "event": "ns"}, {"name": "NVMe_SSD2 Temp", "value": "no reading", "event": "ns"}, {"name": "GPU4 Temp", "value": "49 degrees C", "event": "ok"}, {"name": "GPU6 Temp", "value": "34 degrees C", "event": "ok"}]

@olivierlambert

computed "cpuHighestTemp" thrown TypeError: r.forEach is not a function
    cpuHighestTemp tab-general.js:45
    get factory.js:219
    o factory.js:112
    get factory.js:50
    default tab-general.js:80
    React 36
    _unsubscribes add-subscriptions.js:35
    p index.js:269
    Lodash 4
    p index.js:264

Weird it is not showing CPU temperatures, that was shown in the test command. (H13SRA-TF super micro board)

[{"name": "CPU Temp", "value": "37 degrees C", "event": "ok"}, {"name": "System Temp", "value": "30 degrees C", "event": "ok"}, {"name": "Peripheral Temp", "value": "46 degrees C", "event": "ok"}, {"name": "NIC Temp", "value": "59 degrees C", "event": "ok"}, {"name": "CPU_VRM0 Temp", "value": "43 degrees C", "event": "ok"}, {"name": "CPU_VRM1 Temp", "value": "34 degrees C", "event": "ok"}, {"name": "SOC_VRM Temp", "value": "44 degrees C", "event": "ok"}, {"name": "VDDIO_VRM Temp", "value": "48 degrees C", "event": "ok"}, {"name": "DIMMA~C Temp", "value": "45 degrees C", "event": "ok"}, {"name": "DIMME~G Temp", "value": "44 degrees C", "event": "ok"}, {"name": "MB 12V", "value": "12.08 Volts", "event": "ok"}, {"name": "MB 5VCC", "value": "5.10 Volts", "event": "ok"}, {"name": "MB 3.3VCC", "value": "3.35 Volts", "event": "ok"}, {"name": "VBAT", "value": "0x04", "event": "ok"}, {"name": "MB 5VSB", "value": "5.06 Volts", "event": "ok"}, {"name": "MB 3.3VSB", "value": "3.39 Volts", "event": "ok"}, {"name": "MB 1.8VSB", "value": "1.84 Volts", "event": "ok"}, {"name": "BMC 2.5V", "value": "2.47 Volts", "event": "ok"}, {"name": "BMC 1.8V", "value": "1.77 Volts", "event": "ok"}, {"name": "BMC 1.2V", "value": "1.19 Volts", "event": "ok"}, {"name": "BMC 1.0V", "value": "0.99 Volts", "event": "ok"}, {"name": "BMC 3.3VSB", "value": "3.28 Volts", "event": "ok"}, {"name": "CPU_SOC", "value": "1.22 Volts", "event": "ok"}, {"name": "CPU_VDDIO", "value": "1.12 Volts", "event": "ok"}, {"name": "FAN1", "value": "1960 RPM", "event": "ok"}, {"name": "FAN2", "value": "1960 RPM", "event": "ok"}, {"name": "FAN3", "value": "1960 RPM", "event": "ok"}, {"name": "FAN4", "value": "no reading", "event": "ns"}, {"name": "FANA", "value": "no reading", "event": "ns"}, {"name": "FANB", "value": "no reading", "event": "ns"}, {"name": "FANC", "value": "no reading", "event": "ns"}, {"name": "M2_SSD1 Temp", "value": "no reading", "event": "ns"}, {"name": "M2_SSD2 Temp", "value": "no reading", "event": "ns"}, {"name": "Chassis Intru", "value": "0x00", "event": "ok"}, {"name": "NVMe_SSD1 Temp", "value": "no reading", "event": "ns"}, {"name": "NVMe_SSD2 Temp", "value": "no reading", "event": "ns"}, {"name": "GPU4 Temp", "value": "51 degrees C", "event": "ok"}, {"name": "GPU6 Temp", "value": "35 degrees C", "event": "ok"}]

This is on a H13SRA-TF board.

I'm def willing to test and provide feedback from mine. I have a newer threadripper SM build I can test with. (H13 board)

Reading the email today about what's in new release of XO with the added Lenovo support being the 3rd vendor now supported. Is SuperMicro planned for the same type of support?

Thanks and great update, as always.

@chicagomed there's no need to be editing grub for pass thru, I would use the standard commands and avoid corrupting grub in the process.

@manilx is your nas virtualized on the host, or a separate physical box?

@Seneram ah well excuse my ignorance then, I thought people said the limits were much lower. I can see what you are saying and the big issue with that.

Here's a little test I just ran between VM's over SMB on my Threadripper 7960x build on a Supermicro H13SRA-TF motherboard, def not too bad, these VM's are on different SR's.

ah ok, thanks for the information.

This is pretty minor cleanup question but after removing a NIC, in Xen Orchestra on the host stats page, it still has legend for pifs that don't exist anymore, is there any easy way to clean that up?

@Andrew Thank you Andrew and Olivier, the 4 channel usb card shifted each of its controllers down 2 digits, i removed all the passthroughs, removed the hideback, booted without the card and then re passed the hardware and the box is happy again.

Thanks for the inputs in few threads lately Olivier, appreciate the learning opportunities,

@olivierlambert

I never passed that card to any VMs, there is 2 quadros passed to other VMs and 2 USB channels from a 4 channel card.

Good Evening,

I had some issues with a NIC so I had installed a dual 10GbE Intel X540 PCI-E card, I have since remove all associated networks from VM's and removed the PIF's from the Host.

I ran xe pif-list and confirmed it does not show up there but upon shutdown of the host , remove the card and then power on, it starts to boot, and then shows the normal EFI mapping not available but then instead of showing the splash screen for a second it hangs for a extended period of time and then ends up at a dracut command prompt.

I read the documentation here but this is as far as i can get. (https://xcp-ng.org/docs/networking.html#manage-physical-nics)

The last initqueue message is /dev/disk/by-label/root-yylygk does not exist...starting emergency shell....if I reinstall the card it boots fine.

Anthony

Thank you, low on sleep and of course you were right...