diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-01 21:35:14 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-01 21:35:14 +0200 |
| commit | 3e4c5a6261770bced301b5e74233e7866166ea5b (patch) | |
| tree | 9379fddaba693ef8a045da06efee8529baa5f6f4 /gitlab/issues_text/target_arm/host_missing/accel_HVF/1990 | |
| parent | e5634e2806195bee44407853c4bf8776f7abfa4f (diff) | |
| download | qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.tar.gz qemu-analysis-3e4c5a6261770bced301b5e74233e7866166ea5b.zip | |
clean up repository
Diffstat (limited to 'gitlab/issues_text/target_arm/host_missing/accel_HVF/1990')
| -rw-r--r-- | gitlab/issues_text/target_arm/host_missing/accel_HVF/1990 | 19 |
1 files changed, 0 insertions, 19 deletions
diff --git a/gitlab/issues_text/target_arm/host_missing/accel_HVF/1990 b/gitlab/issues_text/target_arm/host_missing/accel_HVF/1990 deleted file mode 100644 index c2e4e1467..000000000 --- a/gitlab/issues_text/target_arm/host_missing/accel_HVF/1990 +++ /dev/null @@ -1,19 +0,0 @@ -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) |