<![CDATA[XCP-ng 8.3 updates announcements and testing]]>This is a thread dedicated to testing update candidates for XCP-ng 8.3 before they are released to everyone.

We will announce it here everytime there is a new update candidate in our testing repositories, so that you can test them and give feedback before they are pushed to everyone through the updates repository.

Follow this thread

Use the bell on top of this thread to watch it, and make sure you enable email notifications in your forum settings. This way, you will be notified each time there's a new update candidate that needs feedback.

How to install the update candidate

This will be described in each announcement.

If a package breaks something, you can downgrade to the previous version:

yum downgrade package1 [package2 ...]

Then run any tests you find appropriate for the installed updates, and report here.

Most update candidates won't stay for long in the testing stage, so each update is to be tested as soon as possible.

What to test

The most important task is to make sure any update introduces no regressions. Test basic functionality related to the updated component, test that your setup is still functional. As a bonus, you can also test more complicated scenarios that involve the component.

If you can, when the update fixes a bug or security issue, try to reproduce before installing the update, then try to ensure the update does what it says it does.

If the update brings new features, it's good to test them too.

If you can only test parts of the above, it's still good. Just say so when you report here.

How to report

Say what and how you tested, and give the results, either positive or negative. When in doubt about your results, just ask!

Let's start

Now see you at the end of this thread, for any updates candidates currently being tested!

]]>https://xcp-ng.org/forum/topic/9964/xcp-ng-8-3-updates-announcements-and-testingRSS for NodeSun, 15 Mar 2026 08:26:21 GMTWed, 13 Nov 2024 15:44:18 GMT60<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Thu, 12 Mar 2026 15:09:20 GMT]]>@gduperrey Of course, the order matters. Now everything seems to be clear.

]]>https://xcp-ng.org/forum/post/103435https://xcp-ng.org/forum/post/103435Thu, 12 Mar 2026 15:09:20 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Thu, 12 Mar 2026 14:54:57 GMT]]>@abudef In case of a shutdown, I turn off the secondary servers first. Once they are off, I shut down the primary server. This ensures that if the secondary servers have information to send to the primary, they can do so, whereas otherwise, they can wait to shut down.

In case of a pool reboot, I reboot the primary server first, and once it is accessible, I reboot the secondary servers.

]]>https://xcp-ng.org/forum/post/103434https://xcp-ng.org/forum/post/103434Thu, 12 Mar 2026 14:54:57 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Thu, 12 Mar 2026 15:00:57 GMT]]>In my case, I gave the command to shut down all hosts, and the master "made it" first. The other hosts then got "stuck" at this point for a very long time:

ad65b000-f778-4ce2-aba2-0ea120457691-image.jpeg

EDIT: Apparently waiting for umount:

2154dd7d-a1a4-4e82-a834-de4cd149041c-image.jpeg

]]>https://xcp-ng.org/forum/post/103433https://xcp-ng.org/forum/post/103433Thu, 12 Mar 2026 15:00:57 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Thu, 12 Mar 2026 12:48:00 GMT]]>@gduperrey Absolutely understand. 🙂 I didn't now about the Escape key as Manilx mentioned. Next time, I will press Esc to see if there is any useful information and report it here. This was just new behavior and wanted to report it informally.

]]>https://xcp-ng.org/forum/post/103428https://xcp-ng.org/forum/post/103428Thu, 12 Mar 2026 12:48:00 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Thu, 12 Mar 2026 09:41:19 GMT]]>For XO, I suggest you start a separate thread.

Regarding the host issue, without more details or information, it's difficult to say anything at the moment, especially since I haven't been able to reproduce it myself.

]]>https://xcp-ng.org/forum/post/103421https://xcp-ng.org/forum/post/103421Thu, 12 Mar 2026 09:41:19 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Thu, 12 Mar 2026 09:32:27 GMT]]>@ph7 This I can confirm, with XO VM.
But discussion was about the host....

]]>https://xcp-ng.org/forum/post/103419https://xcp-ng.org/forum/post/103419Thu, 12 Mar 2026 09:32:27 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Thu, 12 Mar 2026 08:28:27 GMT]]>@gduperrey
In my homelab I've had the same problem for at least 18 month's
when shutting down the XO-VM it hangs for 2-3 minutes when it tries to umount the remotes

umount /run/xo-server/mounts/xxxxx (SMB and NFS)
umount /run/xo-server/mounts/yyyyy (SMB)

I did report this in an earlier thread

]]>https://xcp-ng.org/forum/post/103417https://xcp-ng.org/forum/post/103417Thu, 12 Mar 2026 08:28:27 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Thu, 12 Mar 2026 06:42:16 GMT]]>As explained, I haven't observed such a delay on our end during our testing.

As Maniix suggests, you can see what's happening by pressing "Esc" to see which step is taking longer.

From what I've heard internally, a common reason for this lengthy step is when a shared server was running on a VM and that VM was shut down. The host then takes a very long time to shut down or restart.

]]>https://xcp-ng.org/forum/post/103412https://xcp-ng.org/forum/post/103412Thu, 12 Mar 2026 06:42:16 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 22:00:58 GMT]]>@robertblissitt

Normal for the pool master to take a bit longer but never seen 15 minutes before.

]]>https://xcp-ng.org/forum/post/103403https://xcp-ng.org/forum/post/103403Wed, 11 Mar 2026 22:00:58 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 23:33:06 GMT]]>@robertblissitt Press ESC and you'll see what's happening

]]>https://xcp-ng.org/forum/post/103402https://xcp-ng.org/forum/post/103402Wed, 11 Mar 2026 23:33:06 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 19:59:32 GMT]]>@abudef After the excitement from the last update cycle (see my post above from ~January 29), I kicked off a Rolling Pool Reboot this time before considering a Rolling Pool Update. During this RPR, the first host is currently hanging on its shut down right now after about 10 - 15 minutes as shown in the screenshot. I am running the previous most recent version of XCP-ng, again from January 29, 2026. I'll revisit installing these most recent updates once I get clean reboots. 🙂
1ce1d34e-2a48-42fc-943d-86b66c2fd596-image.jpeg

]]>https://xcp-ng.org/forum/post/103399https://xcp-ng.org/forum/post/103399Wed, 11 Mar 2026 19:59:32 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 16:34:36 GMT]]>@gduperrey Restart happens normally, without any noticeable delay, but shutdown takes a long time. Which logs should I specifically check?

(It's not a real issue, but I just needed to move servers in the lab and had to shut them down, so I noticed it.)

]]>https://xcp-ng.org/forum/post/103391https://xcp-ng.org/forum/post/103391Wed, 11 Mar 2026 16:34:36 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 16:17:12 GMT]]>Can also confirm that I was able to apply this round of patches using rolling update method without any issues or slowdowns on a pool of 5 hosts.

]]>https://xcp-ng.org/forum/post/103390https://xcp-ng.org/forum/post/103390Wed, 11 Mar 2026 16:17:12 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 16:16:06 GMT]]>@abudef I've updated and rebooted numerous hosts with these updates and haven't noticed any significant slowdowns.

Do you have any additional information in the logs?

]]>https://xcp-ng.org/forum/post/103389https://xcp-ng.org/forum/post/103389Wed, 11 Mar 2026 16:16:06 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 16:14:08 GMT]]>Hi, it seems that shutting down the host is taking an extremely long time now. I tried it in two different environments; the shutdown process starts but gets stuck on the splash screen for several minutes before finally completing. There were no active virtual machines on the hosts being shut down.

Does anyone have the possibility to test this in a lab? Thanks!

]]>https://xcp-ng.org/forum/post/103388https://xcp-ng.org/forum/post/103388Wed, 11 Mar 2026 16:14:08 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 15:51:51 GMT]]>@semarie Hi,

Thanks for your help, I just created the user with the net-snmp-create-v3-user command, and definded SHA-256.

SNMP now works like before.

net-snmp-create-v3-user -ro -A verrysecureauthenticationpassword-a SHA-256 -X verrysecureprivacypassword--x AES snmpusername
]]>https://xcp-ng.org/forum/post/103387https://xcp-ng.org/forum/post/103387Wed, 11 Mar 2026 15:51:51 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 15:41:20 GMT]]>after testing (with net-snmp-utils 5.9.3), I have no problem with snmpv3 and SHA/AES.

On my testing host, snmpd server (OpenBSD):

  • User: user1
  • auth: AES with password123
  • priv: AES with 321drowssap

From XCP-ng 8.3, with net-snmp-utils 5.9.3:
$ snmpbulkwalk -v3 -a SHA -A password123 -l authPriv -x AES -X 321drowssap -u user1 192.168.1.80

so the net-snmp client itself seems fine with SHA/AES.

could you share more elements ?

]]>https://xcp-ng.org/forum/post/103385https://xcp-ng.org/forum/post/103385Wed, 11 Mar 2026 15:41:20 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 15:22:55 GMT]]>SHA`is SHA1. so I assume it is that.
And it seems to be still accepted in authProtocol parameter.

]]>https://xcp-ng.org/forum/post/103382https://xcp-ng.org/forum/post/103382Wed, 11 Mar 2026 15:22:55 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 15:10:38 GMT]]>@Mitchel-APD SHA1 ? I am looking if it is still supported/activated-by-default. I saw that 5.8 added SHA-2 family for RFC-7860 compliance

]]>https://xcp-ng.org/forum/post/103381https://xcp-ng.org/forum/post/103381Wed, 11 Mar 2026 15:10:38 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 15:04:12 GMT]]>@semarie Hi,

We are using SNMPv3 with SHA AES

]]>https://xcp-ng.org/forum/post/103378https://xcp-ng.org/forum/post/103378Wed, 11 Mar 2026 15:04:12 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 15:01:21 GMT]]>@Mitchel-APD how do you auth on SNMP ? v1, v2, v3 ? and if v3, which authProtocol/privProtocol do you use ?

]]>https://xcp-ng.org/forum/post/103376https://xcp-ng.org/forum/post/103376Wed, 11 Mar 2026 15:01:21 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 14:23:29 GMT]]>

@Mitchel-APD said:

Just updated 1 pool with 3 hosts.
SNMP did not work anymore, config file was not changed.
Got the following error: Authorization Error (SNMP error # 16)

Thank you for your feedback, we're going to investigate, I see that there are many changes between both versions:

https://github.com/net-snmp/net-snmp/compare/v5.7.2...v5.9.3

]]>https://xcp-ng.org/forum/post/103371https://xcp-ng.org/forum/post/103371Wed, 11 Mar 2026 14:23:29 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 12:53:41 GMT]]>Just updated 1 pool with 3 hosts.
SNMP did not work anymore, config file was not changed.
Got the following error: Authorization Error (SNMP error # 16)
Did a yum downgrade net-snmp*

From:

  • net-snmp.x86_64 1:5.9.3-8.1.xcpng8.3
  • net-snmp-agent-libs.x86_64 1:5.9.3-8.1.xcpng8.3
  • net-snmp-libs.x86_64 1:5.9.3-8.1.xcpng8.3

To:

  • net-snmp.x86_64 1:5.7.2-52.1.xcpng8.3
  • net-snmp-agent-libs.x86_64 1:5.7.2-52.1.xcpng8.3
  • net-snmp-libs.x86_64 1:5.7.2-52.1.xcpng8.3

After a service restart, SNMP worked immediately.

]]>https://xcp-ng.org/forum/post/103366https://xcp-ng.org/forum/post/103366Wed, 11 Mar 2026 12:53:41 GMT<![CDATA[Reply to XCP-ng 8.3 updates announcements and testing on Wed, 11 Mar 2026 00:40:14 GMT]]>Updated work servers 3 pools 6 host with Rolling Pool Update.

]]>https://xcp-ng.org/forum/post/103338https://xcp-ng.org/forum/post/103338Wed, 11 Mar 2026 00:40:14 GMT