blob: 262bdb8225940abeae425c96cf2376f23df37f17 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
id = 1990
title = "qemu ASSERT [ArmCpuDxe] DefaultExceptionHandler.c:333 on Mac M3"
state = "opened"
created_at = "2023-11-20T22:51:55.968Z"
closed_at = "n/a"
labels = ["accel: HVF", "hostos: macOS", "target: arm"]
url = "https://gitlab.com/qemu-project/qemu/-/issues/1990"
host-os = "macOS Sonoma 14.1.1"
host-arch = "aarch64"
qemu-version = "8.1.2"
guest-os = "fedora-coreos-39.20231101.2.1"
guest-arch = "aarch64"
description = """I am installing Podman 4.7.2 and `podman-machine` uses `qemu-system-aarch64` to boot up an embedded coreos image to run containers.
With the new Apple M3 hardware, I am experiencing a QEMU assertion failure almost all of the time.
`ASSERT [ArmCpuDxe] /home/kraxel/projects/qemu/roms/edk2/ArmPkg/Library/DefaultExceptionHandlerLib/AArch64/DefaultExceptionHandler.c(333): ((BOOLEAN)(0==1))`
I have been unable to get the full crash output - I didn't figure out how to resize the console any larger, and I tried a couple different ways to hook the console up to qemu stdout without any success. (since the kernel command line parameters are not passed in, but instead the image uses a bootloader)
I believe this is the same issue I experience, but with a better capture of the crash:
https://github.com/lima-vm/lima/issues/1996"""
reproduce = """1. Use Mac M3 (Max in my case)
2. Install Podman
3. Run `podman-machine init`
4. Run `podman-machine start --log-level=debug`
5. Crash (almost certainly)"""
additional = "n/a"
|