@Andrew that's planned

yann said:

@kawreh said:

After updating to XCP-ng 8.3 (March 2026), IPMI / iDRAC information fails in both XO5 stable and XO6 stable (built from sources).
It is thrown a XENAPI_PLUGIN_FAILURE log line for failure of the "ipmitool lan print" which works fine on the (DELL) node(s).

Thanks for this report!

Can you please check if just yum downgrade xcp-ng-xapi-plugins-0:1.12.0-1.xcpng8.3.noarch makes the plugin work again, and it does can you please provide the output of ipmitool lan print for both package versions?

Actually, don't bother with the plugins, the regression comes from the ipmitool package. You can downgrade that one to get the functionality back, we're on it.

People with FreeBSD 13.2 or later as a guest are also now able to use Netlink to get their IP address changes reported instantly (rather than having to wait for as much as 1 minute).

This is however not yet part of our CI jobs, as we rely on cross-rs, which for now only provides FreeBSD 12 cross-build support. Your choices to try it:

• build it yourself
• manually-prebuilt binary

Don't forget to kldload netlink first, the Netlink support is not active by default!

@sb2014 this address reporting looks buggy, can you please share some guest information (OS type and version, guest agent version reported by XO)?

@Dataslak can you please request a commandline from GRUB (hit c on the boot menu), and issue the following commands:

echo $root
search --label --set root root-eqjpzg
echo $root

Raised this on IRC, resulting in:

I'll see what I can do, we may still have some time to include this before the release

I guess that's pretty much all we can do on our side (and that's nice from them ).

Catching up with the subject...

The good news first: the patch is already in the 6.8 stable branch (as c8b7b2f158d9d4fb89cd2f68244af154f7549bb4), and part of v6.8.5.

The Ubuntu situation is:

• master kernel branch OTOH has been at v6.8.4 for 12 days, with only minor packaging adjustments since then
• latest tag on master is 6.8.0-25 (only used for lowlatency kernel as of today), based on v6.8.1
• they also have a 6.8.0-26 and changelog entries for -27 on master-next (all about s390)
• standard kernel at 6.8.0-22, based on v6.8.1 too

I'm not familiar with their internal processes, but I suspect they're probably in a validation cycle for upcoming upcoming version right now, and any such fix would have to wait for next one.

The tracker ticket for 6.8.0-27 seems to imply -27 packaging is "in progress". Still digging...

Adding this to our topics to discuss

Since GPU passthrough is involved I'd ping @Team-Hypervisor-Kernel

@hoehnp we're aiming at sharing a very first public version before end of year, but don't hope for it to be anything complete or stable

@kawreh said:

So, it seems not an easy task downgrading due to dependencies. -Fixed some, but more coming up..
Anyway, thanks for replying @yann. I will put it to rest and just wait a bit...

Downgrading just ipmitool should not cause dependency issues. Maybe you tried to apply my original suggestion of downgrading xcp-ng-xapi-plugins?

HI @andrew,

Thanks for the report. Would you mind opening an issue in https://gitlab.com/xen-project/xen-guest-agent/-/work_items?

yann said:

@kawreh said:

After updating to XCP-ng 8.3 (March 2026), IPMI / iDRAC information fails in both XO5 stable and XO6 stable (built from sources).
It is thrown a XENAPI_PLUGIN_FAILURE log line for failure of the "ipmitool lan print" which works fine on the (DELL) node(s).

Thanks for this report!

Can you please check if just yum downgrade xcp-ng-xapi-plugins-0:1.12.0-1.xcpng8.3.noarch makes the plugin work again, and it does can you please provide the output of ipmitool lan print for both package versions?

Actually, don't bother with the plugins, the regression comes from the ipmitool package. You can downgrade that one to get the functionality back, we're on it.

@kawreh said:

After updating to XCP-ng 8.3 (March 2026), IPMI / iDRAC information fails in both XO5 stable and XO6 stable (built from sources).
It is thrown a XENAPI_PLUGIN_FAILURE log line for failure of the "ipmitool lan print" which works fine on the (DELL) node(s).

Thanks for this report!

Can you please check if just yum downgrade xcp-ng-xapi-plugins-0:1.12.0-1.xcpng8.3.noarch makes the plugin work again, and it does can you please provide the output of ipmitool lan print for both package versions?

@jsajous26 xolite n'est pas un service, c'est juste une appli web servie par XAPI, qui est owner du port 80 (le port 443 est lui servi par stunnel@xapi).
Si xapi n'a pas démarré, il doit y avoir un gros soucis. Je commencerais par un systemctl list-units --failed pour voir l'étendue des dégats. Si xapi a échoué à démarrer, xensource.log devrait avoir des détails.

@Tristis-Oris yes it is likely you're using a newer kernel, we likely need to rebuild the agent using a newer version of the netlink crate.

@wlp94114 for example, did you get any warnings in the kernel logs about the firmware version mismatch?

@wlp94114 said in Intel x710-t2l Problems:

The x710 series has a reputation for being picky about driver and nvram versions.

Out of curiosity, is there anything reported by the linux driver that would allow make the situation obvious?

@hoehnp we're aiming at sharing a very first public version before end of year, but don't hope for it to be anything complete or stable

Adding this to our topics to discuss