Bug 2376917 - Cannot boot VM using Incus due UEFI EDK problem
Summary: Cannot boot VM using Incus due UEFI EDK problem
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: incus
Version: 42
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-07 18:58 UTC by Winicius Allan
Modified: 2026-06-08 17:45 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-08 17:45:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Winicius Allan 2025-07-07 18:58:07 UTC
Description of problem:
I'm facing a problem with VM creation when using Incus as an engine. The UEFI EDK2 firmware appears to have crashed during the VM boot process. The discussion can be followed here[1]

[1] https://discuss.linuxcontainers.org/t/incus-shows-error-vm-agent-isnt-currently-running/24174 

Incus version 6.12
Linux kernel version 6.15.4

Steps to Reproduce:
$ sudo dnf install -y incus
$ systemctl enable --now incus
$ incus admin init --minimal
$ incus launch images:debian-12 debian-12 --vm

Actual results:
~
❯ incus console first --show-log
0
0
BdsDxe: loading Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/Scsi(0x0,0x1)
BdsDxe: starting Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/Scsi(0x0,0x1)
!!!! X64 Exception Type - 0E(#PF - Page-Fault)  CPU Apic ID - 00000000 !!!!
ExceptionData - 0000000000000011  I:1 R:0 U:0 W:0 P:1 PK:0 SS:0 SGX:0
RIP  - 0000000001800200, CS  - 0000000000000038, RFLAGS - 0000000000210006
RAX  - 0000000001800200, RCX - 0000000000000000, RDX - 000000003CF513E8
RBX  - 000000003CF51000, RSP - 000000003EF291B0, RBP - 0000000000000190
RSI  - 000000003CF51000, RDI - 0000000000000010
R8   - 0000000000000085, R9  - 0000000034B487B0, R10 - 0000000010000000
R11  - 00000000F0000000, R12 - 000000003CF51000, R13 - 000000003C6EDEA0
R14  - 000000003C6E85A1, R15 - 000000003C6F8FA0
DS   - 0000000000000030, ES  - 0000000000000030, FS  - 0000000000000030
GS   - 0000000000000030, SS  - 0000000000000030
CR0  - 0000000080010033, CR2 - 0000000001800200, CR3 - 000000003EC01000
CR4  - 0000000000000668, CR8 - 0000000000000000
DR0  - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3  - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 000000003E9E1000 0000000000000047, LDTR - 0000000000000000
IDTR - 000000003E3AE018 0000000000000FFF,   TR - 0000000000000000
FXSAVE_STATE - 000000003EF28E10
!!!! Find image based on IP(0x3C6EDEA0) (No PDB)  (ImageBase=000000003C6DD000, EntryPoint=000000003C6DE000) !!!!

Expected results:
A booted VM

Additional info:
I've tested different guest OS such as Ubuntu, CentOS and Debian, all of them crashed on boot

Comment 1 Fedora Release Engineering 2026-05-06 13:28:54 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Aoife Moloney 2026-06-08 17:45:24 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.