@gduperrey Worked swell, thanks

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...

Sorry for not responding, I will look into it in a few hours.

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).

These are old PowerEdge R430 and R810 with iDRAC versions 6 and 8 and worked well before the upgrade, so I guess tihis may be due to a XAPI command failing.

Worth mentioning for this nice-to have feature.

Re: ️ XO 6: dedicated thread for all your feedback!

Read through OpenSSL3 support commit text. Didn't quite understand the implications:
When will a recompile (update) of XO from sources, implementing this commit, need new certs? Any risk of loosing "Intra-Pool" communications without generating new certs before implementing commit?

In Ubuntu 24.04 VM with two PIFs: XO6 report the same IP addresses on VIF #1 as VIF #0. IPv4 and IPv6s on VIF #0 are reported correctly.

XO5 reports both IPs correctly.

---

Xen Orchestra, commit 7399a
Guest tools 7.30.0-15

The Yarn repository is serving an InRelease file signed with an expired GPG key. -Anyone know how to fix this or where to report it to the correct recipient?
(XO built from sources)
Existing XO Yarn version: 1.22.22

I see, thanks

Re: ️ XO 6: dedicated thread for all your feedback!

Isn't there a plugin section in XO6?

OK, thanks for the quick response

Re: VM console borks with "Alt Gr" key

@oliverlambert

Writing characters @,£.$,{,[,],},´, and ~ on a nordic keyboard are done by pressing AltGr+<key>. This is not (straightforward) possible in XOA/ XO cosole. Is a fix for this planned?

Re: Ansible with Xen Orchestra

Solution.

Here, XO (built from sources) is orchestrating a pool of XCP-ng 8.2.1 hosts.
Pool master is xcp.admin.domain (edited). XO VM is xo.local.domain (edited) on debian 12.

I got this working, by generating certs on XO this way:

openssl genrsa -out xo.local.domain.key 4096
openssl req -new -nodes -key xo.local.domain.key -out xo.local.domain.csr
openssl x509 -signkey xo.local.domain.key -in xo.local.domain.csr -req -days 3650 -out xo.local.domain.crt
openssl req -x509 -sha256 -days 3650 -newkey rsa:4096 -keyout xo.rootCA.key -out xo.rootCA.crt
openssl x509 -req -CA xo.rootCA.crt -CAkey xo.rootCA.key -in xo.local.domain.csr -out xo.local.domain.crt -days 3650 -CAcreateserial -extfile xo.local.domain.ext

When generating the above certs and certs for the ansible master node,
CN=<hostname>.local.domain
The file <hostname>.local.domain.ext specifies (SAN) <hostname>.local.domain as one DNS

Do not use snakeoil certs on XO, the standard debian snakeoils use only hostname in CN / SAN fields, not domain.

'xo.xen_orchestra.yml' on the CM VM:

plugin: community.general.xen_orchestra
api_host: xo.local.domain:443
user: <hidden>
password: <hidden>
validate_certs: true
use_ssl: true

'ansible.cfg' need NOT specify enable_plugins = community.general.xen_orchestra

XO inventory may now be pulled from CM/IaC VM and listed this way

ansible-inventory -i xo.xen_orchestra.yml --list

References:
https://xen-orchestra.com/blog/virtops3-ansible-with-xen-orchestra/
https://www.baeldung.com/openssl-self-signed-cert