XCP-ng 8.3 updates announcements and testing
-
Is there any intent to publish the latest xcp-ng 'release' with an XOSTOR iso ? There's an iso for the non-XOSTOR version (xcp-ng-8.3.0-20250606.2.iso) released on 18 Dec 2025, but the latest iso with xostor comparability is xcp-ng-8.3.0-20250616-linstor-upgradeonly.iso released in 16 June 2025.
Reason for asking is the last incremental upgrade on 18th Dec partially failed on our pool master and so we need to do a 'clean' upgrade, however there are XOSTOR disks on that machine, and doing a network upgrade after a partial failure and regardless with xostor - is not advised / achievable.
Thank you!
-
@shorian Do you mean that you have hosts with XOSTOR that can't boot the installer due to broadcom drivers crashing? That's the only issue the updated ISO addresses.
-
@stormi All our hosts were fully patched. We then went through the upgrade of Dec 19th. Two (single server) pools updated fine, the master for the primary pool then failed after patching but on reboot - this machine happens to have XOSTOR so doing the upgrade manually and recovering via the ISO is not an option as the ISO is not XOSTOR compatible and the other options available to us (network update etc) are not permitted by the installer due to XOSTOR. We're not using the Broadcom drivers.
Installer recognises the old installation, that install was patched and it was the reboot after that caused the problem (no idea why or how) so reluctant to 'upgrade' to the previous install given the patch had completed except for the final reboot.
It might be that we can 'refresh' the install using the older version but was nervous of doing so given we'd end up with (potentially) a mash-up of versions of drivers versus data.
-
@stormi The original thread is here
https://xcp-ng.org/forum/topic/10374/xcp-with-opnsense-vm-running-att-bypass-is-vlan-0-network-possible/14?_=1766094991961 -
also noticed a new issue- seems like changes i had in the /etc/xensource/usb-policy.conf file for usb was lost during the upgrade.
I have some usb comm devices i use with a home assistant VM and they were gone post the upgrade.
anyway to make those change last post upgrade? Maybe make then options in gui so a config file can always be reflective of gui settings?
-
@stormi As a footnote to earlier message, we tried using the previous iso image (xcp-ng-8.3.0-20250616-linstor-upgradeonly.iso) to see if things would magically work out but it results in an unrecoverable error - "Cannot upgrade host with LINSTOR 1.29.2-1.e17_9, upgrade repository has versions 1.29.0-1.e17_9. Please make sure your pool is uptodate [sic - typo in error message] and use the latest dedicated ISO."
So yes, afraid I'm after an iso with 1.29.2...
-
@shorian I might have one for you. Can you open a new thread?
-
@marcoi Let's move the discussion back there then
-
@marcoi said in XCP-ng 8.3 updates announcements and testing:
also noticed a new issue- seems like changes i had in the /etc/xensource/usb-policy.conf file for usb was lost during the upgrade.
I have some usb comm devices i use with a home assistant VM and they were gone post the upgrade.
anyway to make those change last post upgrade? Maybe make then options in gui so a config file can always be reflective of gui settings?
This one is known. I had opened an issue about it, but it didn't get much traction yet. We also have a related item in our backlog, but it's a matter of finding resources to handle it.
-
@stormi https://xcp-ng.org/forum/post/101015 V kind, thanks
