podman: qemu VM stuck in spin loop after running podman machine start with podman 4.6.1 and macOS 13.3.1
Issue Description
I’m not sure when exactly this broke on my machine, but running podman machine start causes it to spawn a QEMU process that appears to get stuck in some kind of spin loop. I’ve let this run for several hours as I’ve seen other Mac users find success in doing so, but I had no such luck.
Steps to reproduce the issue
Steps to reproduce the issue
- Install podman 4.6.1 (using MacPorts here, on 13.3.1 Ventura with qemu 8.0.4)
- Run
podman machine init --now(orpodman machine initandpodman machine start)
Describe the results you received
The command hangs after printing Waiting for VM... and a qemu-system-aarch64 process spawns and sits at 100% core usage indefinitely.
Describe the results you expected
Running podman machine start usually finishes within 10-20 seconds.
podman info output
(neither podman info nor podman version can connect)
CPU: Apple M1 Pro
OS: macOS Ventura 13.3.1
podman version: 4.6.1
qemu version: 8.0.4
$ podman machine list && podman machine info
NAME VM TYPE CREATED LAST UP CPUS MEMORY DISK SIZE
podman-machine-default* qemu 14 minutes ago 14 minutes ago 6 4GiB 100GiB
Host:
Arch: arm64
CurrentMachine: podman-machine-default
DefaultMachine: podman-machine-default
EventsDir: /var/folders/0x/ww0lq3cx6575w9twz_bfjncw0000gn/T/podman-run--1/podman
MachineConfigDir: /Users/ray/.config/containers/podman/machine/qemu
MachineImageDir: /Users/ray/.local/share/containers/podman/machine/qemu
MachineState: Stopped
NumberOfMachines: 1
OS: darwin
VMType: qemu
Version:
APIVersion: 4.6.1
Built: 0
BuiltTime: Wed Dec 31 16:00:00 1969
GitCommit: ""
GoVersion: go1.21.0
Os: darwin
OsArch: darwin/arm64
Version: 4.6.1
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
$ port info podman qemu
podman @4.6.1 (sysutils)
Description: Podman is a tool for running Linux containers. You can do this from a MacOS desktop as long as you have access to a linux box either running inside of a VM on the host, or available via
the network. You need to install the remote client and then setup ssh connection information.
Homepage: https://github.com/containers/podman
Build Dependencies: go, go-md2man, python311, pre-commit
Runtime Dependencies: gvisor-tap-vsock, qemu
Platforms: darwin, freebsd, linux
License: Apache-2
Maintainers: Email: judaew@macports.org, GitHub: judaew
Policy: openmaintainer
--
qemu @8.0.4 (emulators)
Variants: [+]cocoa, curl, curses, dbus, gtk3, sdl2, [+]spice, spice_protocol, ssh, target_alpha, [+]target_arm, target_cris, target_hppa, [+]target_i386, target_m68k, target_microblaze,
target_mips, target_nios2, target_or1k, target_ppc, target_riscv32, target_riscv64, target_rx, target_s390x, target_sh4, target_sparc, target_tricore, [+]target_x86_64, target_xtensa,
[+]usb, vde, [+]vnc
Description: QEMU is a generic and open source machine emulator. It can run OSes and programs made for one machine on a different machine. By using dynamic translation, it achieves very good
performance.
Homepage: https://www.qemu.org
Extract Dependencies: xz
Build Dependencies: texinfo, libtool, meson, ninja, pkgconfig, py311-sphinx, perl5
Library Dependencies: glib2, gnutls, libpixman, bzip2, libslirp, lzfse, lzo2, snappy, zlib, zstd, libusb, usbredir, cyrus-sasl2, libjpeg-turbo, libpng, spice-protocol, spice-server
Platforms: darwin
License: GPL-2+
Maintainers: Email: raimue@macports.org, GitHub: raimue
Policy: openmaintainer
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 10 months ago
- Comments: 18 (9 by maintainers)
… and I was able to make it work for me by decompressing the
/opt/local/share/qemu/edk2-aarch64-code.fdFW image as per this post in MacPorts. When done, the machine starts successfully.