XCP-ng 8.3 betas and RCs feedback 🚀
-
@olivierlambert
Unfortunately, I don't have much time in the next few days.
On Sunday I will reset one of the pools with the error to NBD / CBT Delta Backup and then pull the logs and compare them with the one from the working 9.3. Let's see if I can see anything there. If not, I will send you the logs. I will also take a closer look at which processes are stuck there. It looks to me like there are ghost processes running there that don't terminate but seem to continue to block the snapshot. That also seems to be the reason why the snapshot cannot be deleted, except after a reboot.
If I have time, I will also set up a new pool with 9.3 RC2 and then update it to 9.3 officially via yum, just to see if it can then also do error-free NBD deltas.
Regards Joerg -
@jhansen
Hello,
I created a thread about the NBD issue where VBD are left connected to Dom0.
I added what I already know about the situation on my side.
Anyone observing the error can help us by sharing what they observed in the thread.https://xcp-ng.org/forum/topic/9864/vdi-staying-connected-to-dom0-when-using-nbd-backups
Thanks
-
the systems freezes after the last screen and it is diffult to catch the log just before the freeze...
-
@Ajmind-0 does it still freeze if you add
atexit=shell
on the linux commandline? In some error situations the installer attempts to reboot the system after a few seconds, this will make it drop into a shell instead. -
@Ajmind-0 try using the save option at the beginning of the installation.
-
-
I have started the installer again in the BIOS mode and have finished this process successful. It seems to be that the "EFI" Mode from the old intel server is the problem.
As this old equipment is only used as a testing playground I could stay with it as it is. The hardware will never be used as a production system.
-
@Ajmind-0 this was an install not an upgrade of 8.2.1, right? Was your previous working install of 8.2.1 in UEFI mode?
-
@yann
Yes, it was a fresh install. I have removed any partition layout from the Hardware RAID1 via gparted before I have started from scratch.The previous 8.2.1 install was also created in BIOS mode. For me it is clear that this old EFI Intel BIOS from 2012 lacks support for this kind of install process.
-
@Ajmind-0 said in XCP-ng 8.3 betas and RCs feedback :
@yann
Yes, it was a fresh install. I have removed any partition layout from the Hardware RAID1 via gparted before I have started from scratch.The previous 8.2.1 install was also created in BIOS mode. For me it is clear that this old EFI Intel BIOS from 2012 lacks support for this kind of install process.
What model of Intel Server is it?
-
@john-c
Intel Server (SR2625/S5520UR / Dual Xeon E5645) -
@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.
-
@Ajmind-0 said in XCP-ng 8.3 betas and RCs feedback :
@john-c
Intel Server (SR2625/S5520UR / Dual Xeon E5645)If you can access from Intel with an account associated with the motherboard. There's a firmware update available which will add EFI (UEFI) mode support, but to enable it may require adjusting a bios setting. That EFI mode will highly likely or even definitely not include support for SecureBoot.
-
@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?