XCP-ng 8.3 betas and RCs feedback 🚀
-
@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! -
When upgrading an 8.2.1 pool is it safe to issue the commands
secureboot-certs install
xe pool-enable-tls-verificationas 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?
-
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.
-
@nomad Good question. Better once the complete upgrade process of the pool is finished.
-
@Greg_E answer here, in the release notes: https://docs.xcp-ng.org/releases/release-8-3/#upgrade-from-previous-releases
-
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-c346b644a0abIf not, I'll leave it be. Thanks!
-
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
-
@GravityMan You upgraded to the release candidate rather than the final release?
-
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!
-
We also had a live yesterday, whose replay is here: https://www.youtube.com/watch?v=YfyCxP0I6y8
-
not sure is it distro problem, but
mcis 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
closed midnight commander arrow keys #26
-
@Tristis-Oris indeed, I can confirm. I'm not sure about the config file because it's the same version of
mcas we have on 8.2.1, where it's working.Maybe it needs a rebuild.
-
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?
-
@Greg_E said in XCP-ng 8.3 betas and RCs feedback
: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/).
-
@john-c
The UEFI only is going to cut off a bunch of older lab hardware, my HP DL360 gen 8 do not (can not?) have UEFI. That also means that Supermicro X9 is probably out, not sure about old Dell.It's progress and as such need to move with the times, but Beta 9 is going to be a long way off for my testing it due to hardware limitations.
-
@Greg_E said in XCP-ng 8.3 betas and RCs feedback
:@john-c
The UEFI only is going to cut off a bunch of older lab hardware, my HP DL360 gen 8 do not (can not?) have UEFI. That also means that Supermicro X9 is probably out, not sure about old Dell.It's progress and as such need to move with the times, but Beta 9 is going to be a long way off for my testing it due to hardware limitations.
If your old Dell machines are from PowerEdge Gen 12 or later then they can use EFI (UEFI) just need to enable it in the BIOS of those servers.
May also be possible with your Supermicro X9, though a link to the model or the datasheet would help please?
The HPE DL360 Gen8 is likely definitely out unless it has a EFI option via an update. Though for sure the use of HPE DL360 Gen9 or higher will work.
-
weird that i got warning even with UEFI enabled.
