XCP vm fails to boot after newest kernel applied.

olivierlambert

Hi,

For such issues, it's a lot better to create a support ticket. We could point you to get more detailed output (or serial) to understand exactly what's causing the boot to fail

edsilber

@olivierlambert said in XCP vm fails to boot after newest kernel applied.:

For such issues, it's a lot better to create a support ticket. We could point you to get more detailed output (or serial) to understand exactly what's causing the boot to fail

Reply

Sure thing, we were just trying to triage this morning. "Yes this seems to be real & Don't update until we know more" bought us a little time until we could move to next steps. Ticket incoming...

edsilber

@edsilber Ticket#7737661 submitted

olivierlambert

Investigating, thanks for the report!

yomeyo

We have the same issue here with the latest kernel since installing it yesterday.
4.18.0-553.50.1.el8_10.x86_64 does not boot while 4.18.0-553.47.1.el8_10.x86_64 boots fine.
Is there a fix or workaround available yet?

kpark

Ticket 7737647, same issue.

olivierlambert

This is a dual bug:

In the Linux PV driver upstream
How it was backported by RedHat

Both upstream and RH are aware, avoid doing the update for now until we have the confirmation it's fixed.

@stormi we need someone assigned to this to monitor and report any news and progress.

stormi

I also passed the information to Almalinux maintainers, they're now aware of the situation.

bberndt

Just popping in to say, I also found this today.
Yesterday and today was my set aside time to do some updates on my VMs, and came across this today.

Last night they were updating to 4.18.0-553.47.1.el8_10.x86_64
today, 4.18.0-553.50.1.el8_10.x86_64

in my looking around I thought this was related to something that was called: support for x86-64 v2, or lack there of. My CPU's on the problems are E5-2620 v0, and a E5-2430 V2. Moving one of the problem VMs (all Rock Linux 8, I believe) to a Xeon SIlver 4210 made no help. Turns out not the issue, but something to be aware of RHEL 10 is losing this v2 support, which would affect me.

Greg_E

@bberndt

Not to go off topic, but lack of v2 and lack of uefi were reasons I moved my lab to newer hardware.

As of yesterday, the xenserver management agent was still at v8.4, I'm guessing the drivers haven't changed either.

I have one Alma 9 on my vSphere lab, I'll have to update it on Monday and see if it breaks. Debian 12 on XCP-ng 8.3 is not effected as of yesterday.