1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
<think>
Okay, so I'm trying to figure out how to classify this bug report for QEMU. The issue is that when someone tries to boot Ubuntu 23.04 (armhf) using UEFI in QEMU, the system hangs after printing "EFI stub: Exiting boot services...". They were able to reproduce it by running `qemu-system-arm` with certain parameters, including specifying a BIOS file and an HDD image.
First, I look at the problem description. The user mentions that Ubuntu doesn't boot with UEFI and hangs after a specific message. When they directly specify the kernel and initrd, it works fine. So, the issue seems to be related to how QEMU handles the UEFI setup when using cloud images versus manually specifying the kernel and initramfs.
Looking at the possible categories: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The bug occurs during the boot process with UEFI, so it's likely related to how QEMU initializes or interacts with the firmware. The fact that specifying kernel and initrd directly works suggests that the problem isn't with those files but rather with how QEMU is invoking them via UEFI.
Possible causes could include issues in the UEFI firmware itself (maybe not correctly handling the boot process), problems with device initialization, or perhaps a misconfiguration in how the virtual machine is set up. Since it's related to booting, categories like 'boot' or 'hypervisor' might be relevant.
But looking deeper, since the issue occurs when using UEFI and involves the EFI stub, which is part of the firmware's interaction with the kernel, I think the problem might be in the way QEMU's UEFI implementation (edk2) handles certain boot parameters. Alternatively, it could be a hardware emulation issue where some device isn't properly emulated, causing the hang.
Wait, another angle: the user is using the 'virt' machine type. Maybe there are issues with how virtualization components like KVM interact with UEFI in this setup. However, KVM is more about CPU and platform emulation rather than the boot process itself.
The fact that it works when specifying kernel and initrd directly points to a problem in the UEFI handover or initialization. This might fall under 'boot' category because it's related to the booting process of the OS using UEFI.
Alternatively, since UEFI is part of the firmware layer, perhaps it's more related to 'hypervisor', but I'm not sure if QEMU's hypervisor aspects are involved here. The error messages mention EFI stubs and issues with TPM and TCG, which might be hardware-related in the virtual setup.
Considering all this, the most fitting category seems to be 'boot' because the issue is directly related to how the OS boots using UEFI within QEMU.
</think>
boot
|