XCP-ng 8.3 betas and RCs feedback 🚀

gskger

@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 .

olivierlambert

Let's celebrate tomorrow with the official announcement We might do a live on Youtube with a part of the team, stay tuned

stormi

@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.

stormi

@steff22 I have no idea. Maybe try to open a dedicated thread. Also search for older threads about the subject.

marvine

@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!

xisco

@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

xisco

This post is deleted!

nomad

When upgrading an 8.2.1 pool is it safe to issue the commands

secureboot-certs install
xe pool-enable-tls-verification

as soon as the master is upgrade (all other hosts hosts still running 8.2.1) or does that need to wait until all hosts are updated?

Greg_E

@stormi

OK, I'm a little behind in my reading right now... If I was running the 8.3 beta and letting it do all the upgrades, am I now on the release version of 8.3? I just had an update this morning and my servers are telling me that I'm on version 8.3.0 ( ) which I think is different from a few days ago.

stormi

@nomad Good question. Better once the complete upgrade process of the pool is finished.

stormi

@Greg_E answer here, in the release notes: https://docs.xcp-ng.org/releases/release-8-3/#upgrade-from-previous-releases

GravityMan

I upgraded to the RC today from 8.2.1 in prod, and everything went smoothly!

Even though it's just a homelab, I'm glad to move away from VMWare and not jump ship to the stereotypical Proxmox setup that many seem to be going for.

Question: should my uuid have changed, and if not, should I change it? Under XO Advanced settings, the 8.3 version is correct, but in the terminal, states,

xe host-list params=uuid,name,label,version
uuid ( RO)    : 8212db90-3c82-4e72-829a-c346b644a0ab

If not, I'll leave it be. Thanks!

olivierlambert

No UUID change if you made an upgrade, that's the beauty of it, it should be painless/transparent without modifying the database for most parts

stormi

@GravityMan You upgraded to the release candidate rather than the final release?

stormi

Just in case not everyone is aware: we published XCP-ng 8.3 officially on Monday.

Announcement: https://xcp-ng.org/blog/2024/10/07/xcp-ng-8-3/

Release notes: https://docs.xcp-ng.org/releases/release-8-3/

As you can read in the announcement, we really want to thank everyone who helped us with their feedback and other forms of contribution!

stormi

We also had a live yesterday, whose replay is here: https://www.youtube.com/watch?v=YfyCxP0I6y8

Tristis Oris

not sure is it distro problem, but mc is pretty broken on 8.3, same at release version.
Arrows navigation is not working, it typing something instead.

That probably happens because of missing ini file. https://github.com/microsoft/WSL/issues/26#issuecomment-210004998

trapframe created this issue in microsoft/WSL

closed midnight commander arrow keys #26

stormi

@Tristis-Oris indeed, I can confirm. I'm not sure about the config file because it's the same version of mc as we have on 8.2.1, where it's working.

Maybe it needs a rebuild.

Greg_E

@stormi

I noticed an error message while performing this upgrade... Says we should be using UEFI from this point forward. I didn't see that in the release notes, or didn't really read that part very well. It lets you go forward but mentions that higher revisions will not be able to work in BIOS mode.

Here's a question that probably doesn't need to be worked out yet:

If we have old BIOS boot for 8.2.x, and we go to upgrade to 8.x.x (next LTS), are we going to be able to switch to shutdown, switch to UEFI, boot the installer, and upgrade? Or is this going to need a clean install?

john.c

@Greg_E said in XCP-ng 8.3 betas and RCs feedback :

@stormi

I noticed an error message while performing this upgrade... Says we should be using UEFI from this point forward. I didn't see that in the release notes, or didn't really read that part very well. It lets you go forward but mentions that higher revisions will not be able to work in BIOS mode.

Here's a question that probably doesn't need to be worked out yet:

If we have old BIOS boot for 8.2.x, and we go to upgrade to 8.x.x (next LTS), are we going to be able to switch to shutdown, switch to UEFI, boot the installer, and upgrade? Or is this going to need a clean install?

The release of 8.3 is the last version in the 8.x version series. Also 8.3 is a special release at the moment its a standard release, then at a later date its going to become the LTS (next one from after 8.2).

The next version number after 8.3 is going to be 9.0 (https://xcp-ng.org/blog/2024/10/07/xcp-ng-8-3/ and https://docs.xcp-ng.org/releases/release-8-3/).