XCP-ng 8.3 betas and RCs feedback 🚀

alex821982

@stormi Thanks, it works that way)

olivierlambert

Replication or warm migration will work, indeed

alex821982

Copied, I get the following error when starting up

FAILED_TO_START_EMULATOR(OpaqueRef:1286de32-6c5a-4e51-b85c-794e66b4d3f7, varstored, Daemon exited unexpectedly)

stormi

@alex821982 Interesting. There have been changes in UEFI handling in 8.3, but the daemon failing to start when copied back to 8.2 is unexpected. We'll try to replicate this in our lab. If we can't, we'll ask you for more logs.

stormi

@alex821982 Is Secure Boot enabled for this VM in Xen Orchestra? If so, can you try disabling it?

alex821982

@stormi
No is not enabled. I don 't use this option on any machines at all )

stormi

@alex821982 What's the operating system on the VM?

alex821982

@stormi
This is a XOA machine on Ubuntu 22.04

seanmcg182

Went to restart my Server to test my vApp loading, and it didn't actually reboot. The Splash screen cam up as if it was shutting down, and then just stood there.

I was able to access XO Lite, and saw this task just stuck there, obviously for 13 minutes.

Had to hard reboot, and will check to see if any updates available (probably been a couple days since I checked). If so, I'll try again and report back.

UPDATE: No Updates Found. Attempted another reboot. This time it worked. Not sure what locked it up the previous time.

bufanda

@seanmcg182 I know I am a bit late but have you tried to press ESC on the spalsh screen, usually you should then see kernel/systemd messages and see which task may have hung there. Just for the next time when it occurs.

olivierlambert

Yes, that's the usual thing, especially if you have a VM on the same host that is hosting your ISO SR for example (in NFS). The VM will be shutdown, and the NFS will stop answering, and the reboot will be stuck until the timeout is reach (10 minutes?). That might explain why it takes so long to reboot

seanmcg182

@bufanda I appreciate the response. I did not know/try that, but I will keep it in mind if it happens again.

seanmcg182

@olivierlambert Not the case for me. my ISO SR is a local LVM, and my VM SR is a locally mounted HBA... IE, all my VM's can be shut off, and I can still access all my VMDK/VHDs.

The only NFS Storage the XCP-ng is using is for my Backup Schedule, which was not running at that time.

As my edit says though, it worked fine afterwards, and i still havent seen an issues in the last few days since. It was a one-off that I can't reproduce

BenjiReis

@alex821982 Hi!

We reproduced and find a temporary workaround: on your 8.2 host you can run
xe vm-param-remove uuid=<uuid> param-name=NVRAM param-key=EFI-variables

this will clear the UEFI variables of the NVRAM and so the VM should start after that.
HOWEVER: This does not work on Debian VMs, and on other distro you should make sure to save your VM before in case something goes wrong.

We suspect a change in the auth file format between 8.2 and 8.3 is responsible for this issue.

BR

alex821982

@BenjiReis
Thanks )
But we really have already put 8.2 from iso on it with included fixes, which we gave in another topic.
Therefore, there is no way to check now.
While it was 8.3, I managed to conduct some tests.
Did I understand something wrong or is it quite possible that in some tasks 8.3 is significantly faster on the same hardware than 8.2?

Finallf

New installer and final screen out of sync.

I'm testing 8.3 and the only thing I noticed was when installing it on the LG Flatron w2043s monitor, the image is lost in some stages, the monitor complains that it's out of sync, with the wrong hz.

It is possible to install normally, but the screen is small and located on the straight/low side and not in the center.
Sometimes the final screen with the xcp-ng server information appears, other times the monitor says it is out of sync/wrong hz.

Tested with another monitor of the same model and the error persists.
I believe it is Hz above what the monitor supports.

stormi

@Finallf Have you tried the safe boot option?

ThierryC01

I have upgraded from Xcp-ng 8.2 to 8.3 Beta, performed all patches via XOA. I can connect via ssh and on the XOA host console with the same root password but on the host console, the root password is refused!! Why is that? I need to remap my ISO repository that I can browse in XOA but cannot remap in XOA which is inconvenient by the way but... root password is refused on the main console. That does not make any sense.

ThierryC01

@ThierryC01 Well, it happened that there was some kind of keyboard mismatch. Anyway, why can't we choose or even create a local ISO repository? I will have to dig in and play to mount the already existing local disk containing my ISO files into a folder.

ThierryC01

After upgrading to 8.3. from 8.2, all backups have disappeared, I wanted to restore one VM but nothing is displayed at all. Even after importing the config file from 8.2, it is impossible to restore anything. There is not even a way to browse and direct the system to the location of previous backup files.