nils
June 29, 2025, 10:07am
1
AlmaLinux VMs don’t seem to boot with this version, this is the console output:
Booting AlmaLinux (5.14.0-570.23.1.el9_6.x86_64) 9.6 (Sage Margay)'
!!!! X64 Exception Type - 0E(#PF - Page-Fault) CPU Apic ID - 00000000 !!!!
ExceptionData - 0000000000000003 I:0 R:0 U:0 W:1 P:1 PK:0 SS:0 SGX:0
RIP - 0000000034D7B7B0, CS - 0000000000000038, RFLAGS - 0000000000210006
RAX - 0000000034D96000, RCX - 0000000034D96000, RDX - 0000000000024000
RBX - 0000000000000000, RSP - 000000003EE9AF18, RBP - 000000003CB5FC18
RSI - 0000000000000000, RDI - 0000000034D96000
R8 - 0000000034DBA000, R9 - 000000003AC896FD, R10 - 000000003C3E9058
R11 - 0000000000000077, R12 - 000000003E9EC018, R13 - 000000003CC20000
R14 - 000000003C96E3B8, R15 - 000000003C96E3C0
DS - 0000000000000030, ES - 0000000000000030, FS - 0000000000000030
GS - 0000000000000030, SS - 0000000000000030
CR0 - 0000000080010033, CR2 - 0000000034D96000, CR3 - 000000003EC01000
CR4 - 0000000000000668, CR8 - 0000000000000000
DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 000000003E9E1000 0000000000000047, LDTR - 0000000000000000
IDTR - 000000003E297018 0000000000000FFF, TR - 0000000000000000
FXSAVE_STATE - 000000003EE9AB70
!!!! Find image based on IP(0x34D7B7B0) (No PDB) (ImageBase=0000000001066DC8, EntryPoint=00000000010675F3) !!!!
Downgrading to 6.13 fixes the problem for me. I think in the past there were some problems with certain UEFI Firmware files.
stgraber
June 29, 2025, 3:49pm
2
What’s the host system you’re running this on?
stgraber
June 29, 2025, 3:52pm
3
@nils I moved this to its own topic so we don’t make too much noise in the announcement post
Can you also show cat /run/incus/NAME/qemu.conf?
1 Like
stgraber
June 29, 2025, 3:58pm
4
Got it reproduced here, it definitely looks like it’s the new EDK2 that’s at fault.
nils
June 29, 2025, 4:19pm
5
Yes that’s what my research lead me to believe as well, I was somewhat afraid this is another “just me” Problem
I’m not sure but maybe it’s related to this: Changes/Edk2Security - Fedora Project Wiki
stgraber
June 29, 2025, 7:55pm
6
There should be an updated package out now with the old EDK2.
1 Like
nils
June 30, 2025, 4:26am
7
Confirmed, my machines now also start with the new packages. However I don’t think long-term it’s a good idea to ship the old EDK2 for everyone, what do you think? Perhaps there is some way to ship two versions and tag the images that need the old?
stgraber
June 30, 2025, 4:35am
8
Nah, the right fix is to fix whatever is wrong with EDK2.
EDK2 is enough of a mess to build and try to keep track of, we really don’t want to have to deal with multiple versions, especially as basically no two distributions agree on how to name and where to place those files
We have a patch in our edk2 build which normally takes care of the issue (reverts the edk2 change) you’ve linked to, so maybe that needs some updating for the newer version or something else is going on.
