blob: 96e65544b71c86e325530b4e3db0fb9c0a3d6451 (
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
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
graphic: 0.964
device: 0.893
architecture: 0.819
arm: 0.757
semantic: 0.699
debug: 0.689
ppc: 0.679
PID: 0.628
performance: 0.615
permissions: 0.600
kernel: 0.596
files: 0.589
boot: 0.588
register: 0.547
vnc: 0.476
socket: 0.469
user-level: 0.445
network: 0.442
mistranslation: 0.392
hypervisor: 0.323
virtual: 0.236
risc-v: 0.229
TCG: 0.194
peripherals: 0.191
assembly: 0.174
VMM: 0.157
i386: 0.112
x86: 0.102
KVM: 0.027
qemu ASSERT [ArmCpuDxe] DefaultExceptionHandler.c:333 on Mac M3
Description of problem:
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
Steps to 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)
|