XCP-ng 8.3 updates announcements and testing
-
Applied the latest pushed updated to production, no major issues.
Thank you for testing
The only thing to note is my backup XCP config failed Sunday, (...) This morning the backup ran without issues.
Glad it has finally to work, if problem occurs again feel free to ask about this feature in this subforum:
-
XCP-ng 8.3 LTS Updated installer ISO
The installer ISO has been refreshed with up date packages already published.
The image can be downloaded from:
https://repo.vates.tech/tmp/xcp-ng-8.3.0-20260709.testing.iso
The procedure to install XCP-ng 8.3 remains the same.
The refreshed installer ships updated Xen, Linux kernel and some drivers/firmware, which help with deploying XCP-ng 8.3 on hardware that needs changes introduced by updates not present in previous ISO image releases.
This refreshed ISO has been validated on a subset of supported hardware. Additional testing on any hardware from the community would be greatly appreciated.
As with previous installer releases, it can be used to upgrade XCP-ng from a previous major release (8.0, 8.1 or 8.2). Refer to the Upgrade documentation. For existing XCP-ng 8.3 installations, thereβs no need to use this ISO image. Regular yum updates achieve the same results as a fresh installation with that ISO image.
Installer improvements include minor enhancements related to software RAID1 support for the system disks, including support for more than 2 disks in the RAID1 array if anyone really wants that.
New maintenance update candidates for XCP-ng 8.3 LTS
This release batch includes a VBD leak regression fix in XAPI and minor changes needed to build the installer ISO.
A regression was introduced to the
VM.revertoperation inxapi-26.1.4-3.3, which left VBDs attached to the VM when they are not present in the reverted-to snapshot (instead of destroying such VBDs, as was done before).VMs that were reverted to their snapshots after
xapi-26.1.4-3.3may have such "leftover" VBDs. Advanced users can use the leaked_vbds script to detect possible cases in your pools. Sadly, there is no way to automatically distinguish a VBD that was created after a VM.revert from a VBD that survived the VM.revert, so this script relies on the user to determine if the suspicious VBDs are indeed affected or not.What changed
Control Plane
xapi: Fix non-snapshotted VBDs staying attached after VM.revert
Versions
xapi: 26.1.11-1.2.xcpng8.3 -> 26.1.11-1.3.xcpng8.3xcp-ng-release: 8.3.0-37 -> 8.3.0-38
Test on XCP-ng 8.3
yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates rebootThe usual update rules apply: pool coordinator first, etc.
What to test
As usual, normal use and anything else you want to test.
Test window before official release of the updates
~5 days
We would like to thank users who shared feedback since our last call for testing: @Andrew, @XCP-ng-JustGreat, @acebmxer, @bufanda, @flakpyro , @marcoi.
-
Just tried to apply update. Unable to put master host into maintenance mode - not enough memory...
https://xcp-ng.org/forum/post/106814
Edit - Updated both host after manually migrating the vms. Also noticed when i thought i was updating the master host first it might not have been.
With Twinstore installed and enabled HA was also enabled. After first host came back on line i looked at the pool advanced settings and saw host 2 was master not host 1.
Both host have been updated and rebooted. @olivierlambert would this change post master from one host to the other? XO did loose access to the VMs while the first host rebooted. So i am alittle confused...
Once host 2 came back online pool master is switched back to host 1 again...
will look for any other odd things.
-
Is there something specific needed for the leaked_vbds script?
When i run it i get:
[09:37 xcpng-prd-01 ~]# ./leaked_vbds Traceback (most recent call last): File "./leaked_vbds", line 23, in <module> snap = xapi.VM.get_parent(snap) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 317, in __call__ return self.__send(self.__name, args) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 198, in xenapi_request result = _parse_result(getattr(self, methodname)(*full_params)) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 292, in _parse_result raise Failure(result['ErrorDescription']) XenAPI.Failure: ['HANDLE_INVALID', 'VM', 'Ref:29'] -
@flakpyro I'll add some additional error-checking, but looks like you're affected by the
snapshot_ofissue and should run another script (yes, I know...) to fix these stale references: https://github.com/xcp-ng/xcp/blob/master/scripts/snapshot-fixer.py -
Thanks
I ran that second script on the master and it did indeed find entries:
./snapshot-fixer.py rewrite INFO:root:Check HA... INFO:root:Shutting down xapi... INFO:root:Regenerating database... INFO:root:The VM d6befe36-fea7-04f3-25f1-feada684702b has Ref:9 as its "snapshot_of" value, changing to null. INFO:root:The VM e013d9ed-63b1-9c9f-a228-d48a6047688c has Ref:89 as its "snapshot_of" value, changing to null. INFO:root:The VM 060df7ee-8af4-4c93-8265-bfa3024ccacd has Ref:1 as its "snapshot_of" value, changing to null. INFO:root:The VM da7b6ff6-d722-2120-7cc4-a1e0038a216e has Ref:307 as its "snapshot_of" value, changing to null. INFO:root:The VM 4178b057-efee-427e-bcad-67323419ac7a has Ref:9 as its "snapshot_of" value, changing to null. INFO:root:The VM 8d624e49-ca99-4af6-b17c-38cad0646194 has Ref:1 as its "snapshot_of" value, changing to null. INFO:root:The VM dc72da43-f144-3343-5ee5-a0dbffd209f6 has Ref:251 as its "snapshot_of" value, changing to null. INFO:root:The VM e8c6376b-49e1-422b-551a-35420f70af2a has Ref:8 as its "snapshot_of" value, changing to null. INFO:root:The VM 25eb14ab-e943-0d18-2137-c681e1191346 has Ref:11 as its "snapshot_of" value, changing to null. INFO:root:The VM 6f819166-b008-4a03-a692-fcbd75018be9 has Ref:1 as its "snapshot_of" value, changing to null. INFO:root:The VM 9d1a57e8-3531-4b55-9682-f775215866df has Ref:1 as its "snapshot_of" value, changing to null. INFO:root:The VM 0ac88f7c-d79b-281e-cf1f-a2392ba594ed has Ref:29 as its "snapshot_of" value, changing to null. INFO:root:The VM 1f3541c4-8c81-4959-9cbe-edbec9481220 has Ref:1 as its "snapshot_of" value, changing to null. INFO:root:Writing database to /var/lib/xcp/state.db INFO:root:Starting up xapi...after which it shows clean now:
./snapshot-fixer.py dry-run INFO:root:Regenerating database...However i am still getting the same error when trying to run leaked_vbs:
./leaked_vbds Traceback (most recent call last): File "./leaked_vbds", line 23, in <module> snap = xapi.VM.get_parent(snap) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 317, in __call__ return self.__send(self.__name, args) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 198, in xenapi_request result = _parse_result(getattr(self, methodname)(*full_params)) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 292, in _parse_result raise Failure(result['ErrorDescription']) XenAPI.Failure: ['HANDLE_INVALID', 'VM', 'Ref:29'] -
@rzr Updates installed and running. I also run the
snapshot-fixer.pyandxapi_leaked_vbds.pyscripts... The fixer found/fixed lots on many pools...@andriy.sultanov I have the same error... On one pool, I ran
snapshot-fixer.pyand it fixed about 50 of them, butxapi_leaked_vbds.pystill returns an error (before and after fix):Traceback (most recent call last): File "./xapi_leaked_vbds.py", line 23, in <module> snap = xapi.VM.get_parent(snap) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 317, in __call__ return self.__send(self.__name, args) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 198, in xenapi_request result = _parse_result(getattr(self, methodname)(*full_params)) File "/usr/lib/python3.6/site-packages/XenAPI.py", line 292, in _parse_result raise Failure(result['ErrorDescription']) XenAPI.Failure: ['HANDLE_INVALID', 'VM', 'Ref:119'] -
@Andrew @flakpyro I've updated the script, could you try running it again?
https://gist.github.com/last-genius/edf7dab3b1847ec5bb1d9917996eba41
-
@andriy.sultanov No error... returns nothing.
-
@Andrew That means you likely don't have any "leaked" VBDs
-
Running it now shows no error! And no output so looks like i have no issues!
-
@rzr Since the targeted test window is over by now, I wonder: what are your plans regarding this set of patches? Will it be released soon?
-
@rzr Since the targeted test window is over by now, I wonder: what are your plans regarding this set of patches? Will it be released soon?
yes this is the plan, we're a bit slower this time because the iso publication is a longer process, but afaik no issue are spotted so far, thank you for your patience.
-
We pushed the tested packages along a xen security update to the xcp-ng-updates repository, check blog post for summary and related advisories:
https://xcp-ng.org/blog/2026/07/28/july-2026-updates-1-for-xcp-ng-8-3-lts/ -
@rzr Thanks! How long does it take for these patches go be available?
[17:00 xcpng01 ~]# yum update Geladene Plugins: fastestmirror Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org No packages marked for update//EDIT: Nevermind. After running yum clean metadata they are being picked up.
-
We pushed the tested packages along a xen security update to the xcp-ng-updates repository, check blog post for summary and related advisories:
https://xcp-ng.org/blog/2026/07/28/july-2026-updates-1-for-xcp-ng-8-3-lts/Just updated my homelab hosts.
[10:45 xcp-ng-disjqdnc ~]# yum clean metadata Loaded plugins: fastestmirror Cleaning repos: xcp-ng-base xcp-ng-updates 6 metadata files removed 4 sqlite files removed 0 metadata files removed [10:45 xcp-ng-disjqdnc ~]# yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org xcp-ng-base/signature | 473 B 00:00:00 xcp-ng-base/signature | 3.0 kB 00:00:00 !!! xcp-ng-updates/signature | 473 B 00:00:00 xcp-ng-updates/signature | 3.0 kB 00:00:00 !!! (1/2): xcp-ng-base/primary_db | 3.9 MB 00:00:00 (2/2): xcp-ng-updates/primary_db | 1.6 MB 00:00:01 Resolving Dependencies --> Running transaction check ---> Package xen-dom0-libs.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated ---> Package xen-dom0-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update ---> Package xen-dom0-tools.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated ---> Package xen-dom0-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update ---> Package xen-hypervisor.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated ---> Package xen-hypervisor.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update ---> Package xen-libs.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated ---> Package xen-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update ---> Package xen-tools.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated ---> Package xen-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update --> Finished Dependency Resolution Dependencies Resolved ============================================================================================================================================ Package Arch Version Repository Size ============================================================================================================================================ Updating: xen-dom0-libs x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 704 k xen-dom0-tools x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 2.0 M xen-hypervisor x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 2.4 M xen-libs x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 66 k xen-tools x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 47 k Transaction Summary ============================================================================================================================================ Upgrade 5 Packages Total download size: 5.2 M Is this ok [y/d/N]: y Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. (1/5): xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 2.0 MB 00:00:00 (2/5): xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 704 kB 00:00:00 (3/5): xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 66 kB 00:00:00 (4/5): xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 2.4 MB 00:00:00 (5/5): xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 47 kB 00:00:00 -------------------------------------------------------------------------------------------------------------------------------------------- Total 2.9 MB/s | 5.2 MB 00:00:01 Running transaction check Running transaction test Transaction test succeeded Running transaction Updating : xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64 1/10 Updating : xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64 2/10 Updating : xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64 3/10 Updating : xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64 4/10 Updating : xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64 5/10 Cleanup : xen-dom0-tools-4.17.6-9.3.xcpng8.3.x86_64 6/10 Cleanup : xen-tools-4.17.6-9.3.xcpng8.3.x86_64 7/10 Cleanup : xen-dom0-libs-4.17.6-9.3.xcpng8.3.x86_64 8/10 Cleanup : xen-hypervisor-4.17.6-9.3.xcpng8.3.x86_64 9/10 Cleanup : xen-libs-4.17.6-9.3.xcpng8.3.x86_64 10/10 Verifying : xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64 1/10 Verifying : xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64 2/10 Verifying : xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64 3/10 Verifying : xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64 4/10 Verifying : xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64 5/10 Verifying : xen-libs-4.17.6-9.3.xcpng8.3.x86_64 6/10 Verifying : xen-dom0-tools-4.17.6-9.3.xcpng8.3.x86_64 7/10 Verifying : xen-hypervisor-4.17.6-9.3.xcpng8.3.x86_64 8/10 Verifying : xen-tools-4.17.6-9.3.xcpng8.3.x86_64 9/10 Verifying : xen-dom0-libs-4.17.6-9.3.xcpng8.3.x86_64 10/10 Updated: xen-dom0-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-dom0-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-hypervisor.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 -
Working fine latest update into DL360G7
-
Installed these patches on a pool of 4 hosts, can confirm everything looking good!
-
Just installed these onto my test systems including my twinstor guinea pigs and all seems good so far.
-
went well with test systems. going to do prod soon.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better π
Register Login