XCP-ng 8.3 updates announcements and testing
-
@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.
-
Ran into some issues with sdncontroller.py (XCP-ng 8.3 and xcp-ng-xapi-plugins-1.16.0-1) when creating traffic rules on VLAN VIFs (and networks) in XOA — same error on both Premium and Community. The problem turned out to be a line feed sent by XOA.
On line 236 of sdncontroller.py, I added a fix that solved the problem, and it now works perfectly managing traffic rules in XO on VLAN networks:
def update_args_from_ovs(args): # FIX: strip line feed (\n \X0a) sent by Xen Orchestra args["bridge"] = str(args["bridge"]).strip() # get parent...I had another problem when adding rules on networks that weren't connected on all hosts, because those hosts didn't have VMs running on that network (default). Manually connecting them worked fine.
I think it's more of an XO error than xapi plugin, but worked ok in my case.
Thanks for the great work!
-
Ah good catch @andersonalipio ! We'll check that
Ping @Team-XAPI-Network
-
@andersonalipio I would be interested to get some elements from your installation.
- your
/var/log/sdn-controller-plugin.logfile (on the host) in order to check the parameter passed by XO. - output of
xe network-param-list uuid=$UUID(for the network concerned) orxe network-list params=all(if uuid is unknown) - output of
xe pool-list params=other-config(forxo:sdn-controller:*elements) - output of
xe vif-list params=uuid,network-uuid,other-config(forxo:sdn-controller:*elements)
Feel free to share it privately via PM if you prefer, possibly using https://paste.vates.tech/ .
Cc @Team-XO-Backend too (as it could be from XO side)
- your
-
@andersonalipio can you also share the XOA version you're running? @semarie did a bunch of improvement on lifecycle of hosts and VM at some point XO side.
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