XCP-ng 8.3 betas and RCs feedback 🚀

archw

@stormi
I'm installing an instance right now...stand by.

archw

@stormi daemon.log.txt
It woudl not let me upload xensource.log becuse it said it was too big.

archw

@stormi Never done it before but I clicked on "open tunnell" and its sitting there with this message:
Attempting to connect to tunnel.xen-orchestra.com:443 …

The support tunnel has been created.

stormi

@archw Thanks. Can you provide me with the tunnel number in a private message?

stormi

Note: if you don't have such a number, then it probably means it couldn't reach tunnel.xen-orchestra.com:443, due to a firewall or such.

archw

@stormi
I hate to be a moron but how do you PM with this thing?

olivierlambert

Click on @stormi nick name to get the profile displayed, then in the blue button, "Start a chat with stormi" and that's it

archw

@olivierlambert
Done!!!

wilsonqanda

@stormi @ThierryC01 For me my PFSense VMs it get stuck at splash screen. Going from 8.3b to new batch update on 12/21. It does boot up with no error for me just get stuck at autoboot_delay="X". Where X is the time it takes to count down.

Reference to my other post link

Sadly no error so cant tell. Will see how I can get these files never done this before so will be good to know if I can just get it from cmd or XOA and hopefully it is more useful.
/var/log/xensource.log OR /var/log/daemon.log

stormi

@wilsonqanda So your issue is different from that of @archw, whose VMs do not even attempt to boot and fail with a triple fault.

Hopefully you're not stuck. Most of the team will be away for one or two weeks and the remaining ones will only handle urgent support requests

I've created an issue internally so that we investigate this UEFI + pfSense/FreeBSD issue.

wilsonqanda

@stormi Thanks just notice that his situation is more serious than my as I can still move forward by pressing enter on boot screen. His does sound quite different from my situation and really thanks for the update.

HAPPY HOLIDAYS!!! MERRY CHRISTMAS AND HAPPY NEW YEAR

stormi

Could you try yum downgrade edk2 and then try again to start the VM?

wilsonqanda

@stormi I believe this reply is for me as well. Just finish moving the copy of a VM over to a new XCP-ng system and fresh installed 8.3b with latest patch updates. Still fail. Right afterward i added the suggested code below and the countdown work instantly. Thanks!!!

yum downgrade edk2

Note: The "edk2" package is related to the UEFI firmware used by the virtualization platform.

This work great for now. Once official release 8.3 non-beta hopefully it will be resolved. A happy early Christmas present for me thanks!

stormi

So despite dissimilar symptoms, this worked for both of you. We'll investigate this in January then!

exetico

@stormi I've hold back my fingers, and didn't press the "reboot button".

But, if I need to, will downgrading edk2 make anything break? I guess my pfSense instance will fail after a reboot (like described), so... Hopefully I don't need to reboot my host in the next weeks ? Maybe it's a good idea to note, to not push a update like this, so close to Christmas.

Happy Christmas, and Merry New Year .

stormi

@exetico edk2 was initially updated by XenServer to fix a VNC console corruption when vGPU was in use. As we don't support vgpu at the moment (it requires proprietary components), I doubt going back to the previous known to work version will cause any regressions. But there's always some risk.

wilsonqanda

FYI for anyone doing this the snippet of code on a 1 host 1 pool configuration no issue. If you run this code on a multiple hosts in 1 pool configuration make sure to run it all on each host that is affected by the update.

wilsonqanda

@exetico it didnt break for me lol and all 4 of my xcp-ng and multiple pfsense VMs

wilsonqanda

Though as an FYI it is annoying but it show that single upgrade needed in the pool lol that you just downgrade lol. So best not to upgrade until it is resolved in the 1st place. FYI cant move the vm even to another version of 8.3b (original iso version) that doesn't have the updated 12/21 patches as it's not same version.

Obviously after the HOSTs in the pool are updated (patch 12/21) VMs can be migrated but they all need to be on same version.

I thought 8.3b can migrate between all 8.3b of various updates but definitely not the case here. Which I think is a pretty big issues but oh well.

archw

@wilsonqanda Stormi found the issue with edk2 and got me running!