XCP-ng 8.3 betas and RCs feedback 🚀
-
We have 2 packages updated for the first 8.3 security update, a bit late to be part of the final ISO but they will be available at release time. For people willing to test them and provide feedback, see the announcement below.
New security update candidates (xen, intel-microcode)
A new XSA was published on September 24th 2024.
Intel published a microcode update on the September 10th 2024.
- XSA-462 a malicious HVM or PVH guest can trigger a DoS of the host.
SECURITY UPDATES
xen-*:
* Fix XSA-462 - x86: Deadlock in vlapic_error(). The handling of x86's APIC (Advanced Programmable Interrupt Controller) allows a guest to configure an illegal vector to handle error interrupts. This causes the vlapic_error() to recurse, this is protected, but the lock used for this protection will try to be taken recursiveley, leading to a deadlock.intel-microcode:
* Latest Intel microcode update, still named IPU 2024.3, including security updates for:
* INTEL-SA-01103
* INTEL-SA-01097
Test on XCP-ng 8.3
yum clean metadata --enablerepo=xcp-ng-candidates yum update "xen-*" intel-microcode --enablerepo=xcp-ng-candidates rebootThe usual update rules apply: pool coordinator first, etc.
Versions:
xen: xen-4.17.5-3.xcpng8.3intel_microcode: intel-microcode-20240815-1.xcpng8.3
What to test
Normal use and anything else you want to test.
Test window before official release of the update
Until 8.3 release.
-
@bleader Update successful, no issue so far. There is just a message appearing when starting the update: "Delta RPMs disabled because /usr/bin/applydeltarpm not installed."
All VM working for now.
-
@ThierryC01 said in XCP-ng 8.3 betas and RCs feedback
:@bleader Update successful, no issue so far. There is just a message appearing when starting the update: "Delta RPMs disabled because /usr/bin/applydeltarpm not installed."
All VM working for now.
That's harmless. It's just notifying that the system doesn't have deltarpm package installed. This package reduces the size of updates based on what's already installed.
-
@bleader Updated a small test server without any issues.
-
I powered on my spare test "server" and ran this update.
All went fine.
After the reboot I started the fully updated XOA (local installed) and ran it for a few minutes.
then I shut it down but it sat for a few minutes so I did a force shut down from xsconsole.
Rebooted the host again and started the XOA, shut it down and it worked fine
Tested one more time and it went OK. -
Not sure if this is Xcp-ng 8.3 or Nvidia based error.
But when I try to take gpu passthrough with a gtx 1070ti with windows 10. I get the drivers installed fine without errors but after reboot I get an error triangle in the windows device mangager-. error43 and no image on the screen
Wasn't Xcp-ng 8.3 related or windows drivers I think.
Tested with another PC with Xcp-ng 8.3 and everything worked immediately. So think it must be Asrock rack B650D4U3-2L2Q bios related or ipmi trying to use the same gpu.
-
Applying the latest XCP-ng 8.3 RC2 "xen-*" and intel-microcode updates from the candidate repository worked great here as well. Everything appears to be running well.
-
@bleader There is a
xcp-ng-8.3.0.isoon the ISO repository. Is that the release of XCP-ng 8.3
? Looking forward to an official announcement 
. -
@gskger Good catch
-
@gskger Yes, but the official announcement is for tomorrow. Be careful because the release notes are crucial for this release, so wait for them before doing anything production related
(and yes we've already seen PAID users with XCP-ng 8.3 in PRODUCTION environment, people are crazy
Even if it's really stable, I wouldn't have bet my entire production on it) -
@olivierlambert I am one of those crazy people as you well know! But we needed the better hardware and driver support with our new servers.
That said if we already did the ISO upgrade to RC2 + latest updates are we essentially on the final version already or will there be additional new packages?
-
Yes
-
@olivierlambert Thats great news and makes for an easy Monday then tomorrow! Happy to actually be on a stable release now!
Also congrats on the release! We have been running 8.3 on remote single host sites since March of this year and in our core production environment since August, other than a few NFS4 related woes (Solved by using NFS3 instead) its been a very solid experience even for something considered "pre-release".
-
@olivierlambert People might be a little crazy, but they also have trust in the test and RC lifecycle of XCP-ng, which has proven to be very reliable thanks to the dedication of the Vates team and also the community. But I agree, for production use it's better to wait for a GA announcement. Anyway, congratulation to this important milestone in the development of XCP-ng
. -
Let's celebrate tomorrow with the official announcement
We might do a live on Youtube with a part of the team, stay tuned -
@flakpyro said in XCP-ng 8.3 betas and RCs feedback
:That said if we already did the ISO upgrade to RC2 + latest updates are we essentially on the final version already or will there be additional new packages?
You even are one update ahead from the final version if you installed the the last security fix which isn't on the ISOs. But that's only because you already did the ISO upgrade to RC2. Users of earlier prereleases of XCP-ng 8.3 need to upgrade using the final installation ISO.
-
@steff22 I have no idea. Maybe try to open a dedicated thread. Also search for older threads about the subject.
-
@steff22 I have the exact same problem with a Asrock rack B650D4U i tried everything to make it but work but have the exact same problem as you.
Even new fresh installation of windows machine didnt work.If you have solution please let me know thanks in advance!
-
@stormi the LINUX OS under XCP-NG detects the cards but xcp-ng says that no ethernet was detected. Even after some emergency network resets.
Hardware is fine. As said, solved reinstalling, but this is not the first time, after upgrading it happened some times but solved with emergency network reset -
This post is deleted!
