XCP-ng 8.3 betas and RCs feedback 🚀
-
@laurentm said in XCP-ng 8.3 betas and RCs feedback
:@Ajmind-0 Same problem with DELL PowerEdge R820 and DELL PowerEdge R520:
I had to upgrade in BIOS mode and it was the same thing for a fresh install.
With DELL PowerEdge R240, no problem to upgfrade in UEFI.
You can switch to EFI mode in the BIOS setup of Dell PowerEdge R520 and Dell PowerEdge R820. I know this for sure as my home lab is based around a trio Dell PowerEdge R620 servers.
I found this out when navigating around the BIOS settings, specifically its in the Boot Mode options settings.
-
@john-c I know already that, bios was updated and it was easy to boot in UEFI but the install failed and even complains about not enough space on EFI boot part.
I tried after wiping all disks but could not perform the install all the way.
Either with SATA SSDs or NVMe (with an upgraded DELL backplane designed for NVMe) it never works. -
@laurentm said in XCP-ng 8.3 betas and RCs feedback
:@john-c I know already that, bios was updated and it was easy to boot in UEFI but the install failed and even complains about not enough space on EFI boot part.
I tried after wiping all disks but could not perform the install all the way.
Either with SATA SSDs or NVMe (with an upgraded DELL backplane designed for NVMe) it never works.SSD drives eventually fill and/or wear up so you eventually don't have enough space for data. Also if the amount of data needed for booting is larger than the size of EFI boot partition it will run out of space and complain.
Also how large is the OS drive's capacity is it large enough capacity to exceed the system requirements for XCP-ng? The OS drive gets partitioned according to a predetermined fixed structure so if the drive isn't large enough, then when partitioning it may make them too small.
@yann How large does XCP-ng make the EFI boot partition please, as for laurentm it may not be making it with sufficient size?
-
Hello,
I also had problems installing Beta 2 on older servers.
Switch from BIOS to UEFI under Boot in the BIOS.
Take a USB stick with the RC1, install and update with yum update
or
just use the new 8.3 Official. -
@jhansen Installing from RC1 then updating with yum update is not supported. The release notes state you must reinstall from prereleases of XCP-ng 8.3, unless you installed using XCP-ng 8.3 RC2 (and now that the final release is out, there's no reason to keep installing a pre-release).
-
the Intel Bios (64) has already EFI support included, so I can select EFI to boot the install media and everything works fine until the step were the boot entries are created, which performs still correct, but with the EFI boot entries creation my install dies.
-
@Ajmind-0 said in XCP-ng 8.3 betas and RCs feedback
:the Intel Bios (64) has already EFI support included, so I can select EFI to boot the install media and everything works fine until the step were the boot entries are created, which performs still correct, but with the EFI boot entries creation my install dies.
What does it say when it dies or logs when it does so?
-
@john-c
The system freezes and the last screenshots are above visible. -
@Ajmind-0 said in XCP-ng 8.3 betas and RCs feedback
:@john-c
The system freezes and the last screenshots are above visible.What's "IBA GE Slot 0100 v1371" it shows up as part of the boot menu load order, boot options from your EFI instance?
-
@john-c
PXE boot ROM for network boot. (Never used) -
@Ajmind-0 said in XCP-ng 8.3 betas and RCs feedback
:@john-c
PXE boot ROM for network boot. (Never used)So SanDisk HD is the portable drive used or is it something else?
-
@stormi
should have been and and not or.
so
and then update with iso 8.3 Of.
Had an old server that kept crashing during the 8.3 Of. installation. It worked with RC1 and then upgraded to 8.3 Of.
Sometime this old things are a bit tricky
-
Yes, Sandisk USB Stick (Ventoy) in UEFI boot mode. I had also created a standard DVD ROM in order to exclude any differences in such a boot construct.
-
@Ajmind-0 said in XCP-ng 8.3 betas and RCs feedback
:Yes, Sandisk USB Stick (Ventoy) in UEFI boot mode. I had also created a standard DVD ROM in ourder to exclude any differences in such a boot construct.
Did you verify that the checksums matched for the ISO you downloaded, before preparing the media?
The reason being any corruption in the downloaded image can affect the resulting media and their contents. So unexpected things can happen if the media or source media is corrupt, such as an in ability to complete the installation of OS software even at the final stage - boot manager installation.
-
the install process went fine in BIOS mode!
And yes, the checksum is correct. -
Hello,
Is it necessary to upgrade all hosts in the pool to manage VMs across the entire pool?
I receive the error "NOT_SUPPORTED_DURING_UPGRADE" when attempting to migrate vm and doing snapshots after upgraded a host to 8.3. -
@Robert You can migrate VMs from a host not upgraded yet to a host which was upgraded. Some other operations are not possible. A partially upgraded pool is supposed to the a short transitioning state.
-
@stormi Thanks for the response, probably was something wrong with that pool then, everything seemms to be working after upgraded all hosts to 8.3
-
S stormi unpinned this topic
-
This is the end for this nice and useful thread, as XCP-ng 8.3 is not a beta nor a RC anymore: it's a supported release now.
However, we still need your feedback, as we publish update candidates ahead of their official release, for users to test them.
Right now, there's a security update candidate which is to be tested.
I strongly invite everyone who is currently subscribed to this thread to now subscribe to the new, dedicated thread: XCP-ng 8.3 updates announcements and testing, and to verify that their settings allow sending notification e-mails and/or other forms of notification.
-
O olivierlambert locked this topic
