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?
-
@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
-
@stormi Yes, I'm also affected in here, due to an USB device that's disabled by default.
-
I did post an alternative script here:
https://xcp-ng.org/forum/topic/8620/usb-passthrough-override-script-to-ensure-usb-policy-conf-consistencyBut it was later removed due to request by @stormi .
I'm currently using my script which basically backs up your settings and overrides the default one (after backing it up on first install) on every boot. I know its a crude way to handle but it was only meant to be temporary till you guys find a solution.
I have reposted it.
Please note : Issues caused by this script (if any) shall not be covered by the XCP-NG Support Team -
@gb.123 Please mention in your post that any issue caused by this script will not be covered by official support. The concerns I voiced then still hold.
-
Great Idea!
Post updated !
