Team - Hypervisor Kernel group | XCP-ng and XO forum

yannsionneau

Hi,

Someone from the Hypervisor & Kernel team will have a look shortly, we'll get back to you with our findings.

Thanks a lot for the very detailed report!

Yann

TeddyAstie

@sluflyer06 said:

@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

The driver is telling you that you are missing the Intel Xe firmwares (that are probably in linux-firmware package).

TeddyAstie

@tsukraw Can you give the output of xen-cpuid -p (in Dom0) ?

dinhngtu

Hi, it's a known issue on newer CPUs: https://docs.xcp-ng.org/troubleshooting/windows-pv-tools/#bsod-0x3b-system_service_exception-on-newer-intel-cpus

~~What's your CPU Vendor value shown in xl dmesg?~~

Never mind, I missed your log: CPU Vendor: Intel, Family 6 (0x6), Model 143 (0x8f), Stepping 8 (raw 000806f8)

dinhngtu

@kagbasi-wgsdac Blind guess, your ISO SR is not connected to one of the hosts?

dinhngtu

@archw XenClean is not needed when upgrading; it's only needed when switching tools vendor, or when switching from the old XCP-ng 8.2 tools.

The XCP-ng 9.1 tools installer will block installation and indicate an error whenever XenClean is needed.

dinhngtu

@probain Yes, that's expected as there were only changes in the installer and XenClean/XenBootFix, the drivers and guest agent binaries included in 9.1.145 and 9.1.146 are the exact same. As a result, the version information in the guest agent (which does the reporting) was not updated.

dinhngtu

Hello all,

Version 9.1.146 Release of the Windows PV tools has been released.

Download the latest release here: https://github.com/xcp-ng/win-pv-drivers/releases

It will be integrated into the XCP-ng built-in tools ISO after a test period of 2 weeks.

This is a small revision to fix issues when installing on certain Windows installations. Only the installer and XenClean were changed; the binaries inside stay the same.

If you're already on 9.1.145, upgrading is optional.

Changes since 9.1.145

Fixed: Fix issues when installing on certain Windows installations.

dinhngtu

Recent Windows patches also changed the exit code of schtasks.

A new package will be released to address this.

Team - Hypervisor Kernel

Posts

Changes since 9.1.145

Member List