`podman machine start` stuck "Waiting for VM" indefinitely with qemu synchronous exception MacOS M3 #20776

peter-crist · 2023-11-25T02:33:02Z

Issue Description

With a fresh install via homebrew, I cannot start a machine and it hangs indefinitely at Waiting for VM. Running with debug shows that qemu hits a Synchronous Exeception at 0x00000000BC308000.

Steps to reproduce the issue

brew install podman
podman machine init
podman machine start

Describe the results you received

VM fails to start.

Describe the results you expected

VM starts.

podman info output

Version: 4.7.2
OS: macOS 14.2
Chip: Apple M3 Pro
Architecture: arm64

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

The text was updated successfully, but these errors were encountered:

danielroseman · 2023-11-26T17:11:26Z

I had this issue; updating qemu from 8.1.3_1 to 8.1.3_2 via brew upgrade qemu fixed it.

peter-crist · 2023-11-26T21:47:01Z

Updating to qemu 8.1.3_2 resulted in a different exception and hang:

ASSERT [ArmCpuDxe] /home/kraxel/projects/qemu/doms/edk2/ArmPkg/Library/DefaultExceptionHandlerLib/AArch64/DefaultExceptionHandler.c(333): ((BOOLEAN)(0==1))

jwhostet · 2023-11-27T15:18:02Z

Reading through some other issues I've found this workaround: podman machine init -m 3072

podman 4.7.2
qemu 8.1.3_2
MacOs 14.1.1 - M3 Max

peter-crist · 2023-11-27T16:38:26Z

Reading through some other issues I've found this workaround: podman machine init -m 3072

Unfortunately no such luck on my end.

mchataigner · 2023-11-29T12:01:50Z

podman machine init -m 3072 solved the issue for me

podman 4.8.8
qemu 8.1.3_2
MacOs 14.1.1 - M3 pro

jaydorsey · 2023-11-29T14:26:07Z

Reading through some other issues I've found this workaround: podman machine init -m 3072

Unfortunately no such luck on my end.

I didn't have any luck doing this initially either; then I absolutely nuked everything:

Killed all the podman related processes using Activity Monitor
Ran podman machine rm to delete the machine
Uninstalled podman, podman desktop, and qemu

Re-ran it all from scratch today, starting with podman only and then running podman desktop afterwards:

Reinstall podman & qemu
Run the command from jwhostet, then podman machine start and it worked
Open up podman desktop, everything looks good

podman 4.8.0
qemu 8.1.3_2
macos 14.1.1 M3 Max

I have a max, you have a pro, but one other person with a pro reported success so double-checking everything might be worth a shot? I tried similar steps before but skipped the podman machine rm step before and I deleted podman desktop by just dragging it to the trash before so that might have been why it failed the first time

robahtou · 2023-11-29T19:44:43Z

@jaydorsey I have the same specs and followed your instructions. I am still unable to get the VM to run:
Waiting for VM ...

EDIT:
I installed brew install podman-desktop and enabled podman engine this way and it is working now 🤷🏽‍♂️

peter-crist · 2023-11-30T14:39:03Z

@jaydorsey I have the same specs and followed your instructions. I am still unable to get the VM to run: Waiting for VM ...

EDIT: I installed brew install podman-desktop and enabled podman engine this way and it is working now 🤷🏽‍♂️

This worked for me as well!
Additionally, I did the following before installing podman-desktop:

brew uninstall podman
brew uninstall qemu
Removed any lingering podman files I could find:
- Removed ~/.ssh/podman-machine-default and ~/.ssh/podman-machine-default.pub.
- Removed ~/.local/share/containers and ~/.config/containers

jaydorsey · 2023-11-30T15:46:36Z

One thing of maybe note: It worked great yesterday. I let my machine go to sleep, logged back on today, and the whole thing was locked up again list it was. Podman said it wasn't running, but it actually was, I can't delete images or machines, everything was essentially responsive. I tried force-quitting everything and restarting with no luck

I need to try a restart/reboot of my computer later to see if that fixes it but it didn't seem to work after I let my computer sleep (or perhaps some other unrelated reason, like a crash)

peter-crist · 2023-11-30T16:15:04Z

And now I'm seeming to have problems with volumes and my VM is somehow back in a "Currently starting" state. Can't stop, or remove it. 👎

osamamunir23 · 2023-12-05T13:18:33Z

I have tried all steps as above, but still stuck on Waiting for VM ...

if i log out the errors, thats what i get back:

podman --log-level=debug machine start
INFO[0000] podman filtering at log level debug
DEBU[0000] Using Podman machine with qemu virtualization provider
Starting machine "podman-machine-default"
DEBU[0000] {true 1500 map[forward-dest:[/run/user/503/podman/podman.sock] forward-identity:[/Users/USERNAME/.ssh/podman-machine-default] forward-sock:[/Users/USERNAME/.local/share/containers/podman/machine/qemu/podman.sock] forward-user:[core]] [] map[listen-qemu:unix:///var/folders/v9/n5xqlp4j441csny4xvmgyr6c0000gq/T/podman/qmp_podman-machine-default.sock] /var/folders/v9/n5xqlp4j441csny4xvmgyr6c0000gq/T/podman/podman-machine-default_proxy.pid 49455}
DEBU[0000] qemu cmd: [/opt/homebrew/bin/qemu-system-aarch64 -accel hvf -accel tcg -cpu host -M virt,highmem=on -drive file=/opt/homebrew/share/qemu/edk2-aarch64-code.fd,if=pflash,format=raw,readonly=on -drive file=/Users/USERNAME/.local/share/containers/podman/machine/qemu/podman-machine-default_ovmf_vars.fd,if=pflash,format=raw -m 3072 -smp 5 -fw_cfg name=opt/com.coreos/config,file=/Users/USERNAME/.config/containers/podman/machine/qemu/podman-machine-default.ign -qmp unix:/var/folders/v9/n5xqlp4j441csny4xvmgyr6c0000gq/T/podman/qmp_podman-machine-default.sock,server=on,wait=off -netdev socket,id=vlan,fd=3 -device virtio-net-pci,netdev=vlan,mac=5a:94:ef:e4:0c:ee -device virtio-serial -chardev socket,path=/var/folders/v9/n5xqlp4j441csny4xvmgyr6c0000gq/T/podman/podman-machine-default_ready.sock,server=on,wait=off,id=apodman-machine-default_ready -device virtserialport,chardev=apodman-machine-default_ready,name=org.fedoraproject.port.0 -pidfile /var/folders/v9/n5xqlp4j441csny4xvmgyr6c0000gq/T/podman/podman-machine-default_vm.pid -virtfs local,path=/Users,mount_tag=vol0,security_model=none -virtfs local,path=/private,mount_tag=vol1,security_model=none -virtfs local,path=/var/folders,mount_tag=vol2,security_model=none -drive if=virtio,file=/Users/USERNAME/.local/share/containers/podman/machine/qemu/podman-machine-default_fedora-coreos-39.20231119.2.0-qemu.aarch64.qcow2]
Waiting for VM ...

jordyguntur · 2023-12-08T15:47:38Z

Also stuck on Waiting for VM. Has anyone found a work-around without using podman-desktop?

relistan · 2023-12-08T18:36:05Z

M3 Pro
macOS 14.1
QEMU 8.1.3_2
podman 4.7.2

I have intermittently been able to get it to work between sessions of removing everything, re-installing, deleting and recreating machines. Once it decides to work, it is fine until the mac goes to sleep while the QEMU machine is running.

On recovery from sleep, the podman machine shows as running, but it's not accessible. From then on the issues remains until some series of uninstalling and reinstalling, deleting and recreating machines finally works. I have not yet figured it out.

The specific problem seems to be with -netdev socket,id=vlan,fd=3 if replacing fd=3 with listen=:1234 the machine starts, but of course does not work with podman.

EDIT: Steps that seem to make it work again:

podman machine rm
brew uninstall podman
brew uninstall qemu
Reboot
brew install podman (qemu installs with it)
Create machine from podman desktop but not let it start it
podman machine start

pantaovay · 2023-12-09T13:52:29Z

I have tried all the methods, but all do not work.

herblet · 2023-12-11T13:30:51Z

Is this not a result of this issue tracked on the qemu project, which is the result of a bug even further upstream?

https://gitlab.com/qemu-project/qemu/-/issues/1990

m8nmueller · 2023-12-12T16:47:31Z

I agree with @herblet. Also see the fix employed by Lima: lima-vm/lima#2061

What worked for me:

Download https://github.com/lima-vm/edk2-patched.tmp/releases/download/edk2-stable202311%2Blima.0/edk2-aarch64-code.fd.gz from https://github.com/lima-vm/edk2-patched.tmp/releases
Init podman machine
Update podman machine config json using
sed -i 's@file=.*edk2-aarch64-code.fd@file=/path/to/downloaded/edk2-aarch64-code.fd@g' /path/to/qemu-config/podman-machine-default.json

where the qemu-config directory is reported by MachineConfigDir in the output of podman machine info.
Start machine

nzhuk98 · 2023-12-15T23:24:28Z

What worked for me:

Download https://github.com/lima-vm/edk2-patched.tmp/releases/download/edk2-stable202311%2Blima.0/edk2-aarch64-code.fd.gz from https://github.com/lima-vm/edk2-patched.tmp/releases

These links don't work anymore.

I am on M3 Max. Changing memory on init didn't work.

Uninstalling everything, and installing podman-desktop worked.

podman machine rm
brew uninstall podman qemu
rm -rf ~/.config/containers
rm -rf ~/.local/share/containers
brew install podman-desktop

Start podman-desktop, init and start podman machine. I disabled "Machine with root privileges:", but it probably doesn't matter.

nutshellfool · 2023-12-20T01:28:54Z

What worked for me:

Download https://github.com/lima-vm/edk2-patched.tmp/releases/download/edk2-stable202311%2Blima.0/edk2-aarch64-code.fd.gz from https://github.com/lima-vm/edk2-patched.tmp/releases

These links don't work anymore.

I am on M3 Max. Changing memory on init didn't work.

Uninstalling everything, and installing podman-desktop worked.
podman machine rm
brew uninstall podman qemu
rm -rf ~/.config/containers
rm -rf ~/.local/share/containers
brew install podman-desktop
Start podman-desktop, init and start podman machine. I disabled "Machine with root privileges:", but it probably doesn't matter.

This works for me.

FullofQuarks · 2023-12-21T06:29:28Z

What worked for me:

Download https://github.com/lima-vm/edk2-patched.tmp/releases/download/edk2-stable202311%2Blima.0/edk2-aarch64-code.fd.gz from https://github.com/lima-vm/edk2-patched.tmp/releases

These links don't work anymore.

I am on M3 Max. Changing memory on init didn't work.

Uninstalling everything, and installing podman-desktop worked.
podman machine rm
brew uninstall podman qemu
rm -rf ~/.config/containers
rm -rf ~/.local/share/containers
brew install podman-desktop
Start podman-desktop, init and start podman machine. I disabled "Machine with root privileges:", but it probably doesn't matter.

Was having the same issue, but this worked for me. Not sure I like having to run an installer from within a cask, since this installation is controlled outside of brew

denisborisov · 2023-12-21T15:28:49Z

What worked for me:

Download https://github.com/lima-vm/edk2-patched.tmp/releases/download/edk2-stable202311%2Blima.0/edk2-aarch64-code.fd.gz from https://github.com/lima-vm/edk2-patched.tmp/releases

These links don't work anymore.

I am on M3 Max. Changing memory on init didn't work.

Uninstalling everything, and installing podman-desktop worked.
podman machine rm
brew uninstall podman qemu
rm -rf ~/.config/containers
rm -rf ~/.local/share/containers
brew install podman-desktop
Start podman-desktop, init and start podman machine. I disabled "Machine with root privileges:", but it probably doesn't matter.

I have the same issue on my M1 and these instructions does not work for me. =(

robahtou · 2023-12-21T15:42:30Z

I've been having this issue on/off.

What got it working consistently for me is very similar to @FullofQuarks

If you already have podman-desktop installed make sure to delete it as well:

podman machine rm  
brew uninstall podman-desktop podman qemu  
rm -rf ~/.config/containers  
rm -rf ~/.local/share/containers
## <didn't do this>brew install podman-desktop

Instead of installing podman-desktop via brew I downloaded and installed the arm .dmg file (follow the instructions) and so far no issues (so far!!). Will report back if the issue resurfaces.

rhatdan · 2023-12-21T15:52:08Z

You could try this with the apple hypervisor, which we plan to move with to see if it works better. Qemu has proven to be not as stable as we like.

If you have a recent Podman, I believe you can do.

export CONTAINERS_MACHINE_PROVIDER=applehv
podman machine init

robahtou · 2023-12-21T16:06:47Z

@rhatdan Just tried your suggestion and now I'm getting this error:

➜  ~ podman machine init machine
Extracting compressed file: machine_fedora-coreos-39.20231204.2.1-applehv.aarch64.raw: done. 
Error: could not find "vfkit" in one of {[$BINDIR/../libexec/podman /usr/local/opt/podman/libexec/podman /opt/homebrew/opt/podman/libexec/podman /opt/homebrew/bin /usr/local/bin /usr/local/libexec/podman /usr/local/lib/podman /usr/libexec/podman /usr/lib/podman] {<nil>}}.  
To resolve this error, set the helper_binaries_dir key in the `[engine]` section of containers.conf to the directory containing your helper binaries.

Not sure what this means 😓

denisborisov · 2023-12-21T16:26:18Z

You could try this with the apple hypervisor, which we plan to move with to see if it works better. Qemu has proven to be not as stable as we like.

If you have a recent Podman, I believe you can do.
export CONTAINERS_MACHINE_PROVIDER=applehv
podman machine init

installed vfkit via this doc: https://github.com/crc-org/vfkit
but the result of podman machine start is Error: Get "http://localhost:8081/vm/state": EOF

lockcrocodilegiraffe · 2023-12-21T16:36:28Z

I've been having this issue on/off.

What got it working consistently for me is very similar to @FullofQuarks

If you already have podman-desktop installed make sure to delete it as well:
podman machine rm  
brew uninstall podman-desktop podman qemu  
rm -rf ~/.config/containers  
rm -rf ~/.local/share/containers
## <didn't do this>brew install podman-desktop
Instead of installing podman-desktop via brew I downloaded and installed the arm .dmg file (follow the instructions) and so far no issues (so far!!). Will report back if the issue resurfaces.

Sadly, this hasn't worked for me (Apple M2 Pro). I get "Error: Command execution failed with exit code 125"

lestex · 2024-01-23T16:40:09Z

I'm experiencing this on M1 pro as well, a downgrade of qemu to 8.1.3 helped, so I'll stick to it for a time being.

cbr7 · 2024-01-23T18:05:07Z

Same for me, just had the same problem on a M1 PRO after updating to podman 4.9.0. After several uninstalls, restarts and reinstalls I finally got it to work and the podman machine to start up correctly.

andremayer · 2024-01-24T05:05:37Z

I'm experiencing this on M1 pro as well, a downgrade of qemu to 8.1.3 helped, so I'll stick to it for a time being.

Hi @lestex Can you share how you downgraded qemu back to 8.1.3? I tried running this on my macOS but didn't work:

❯ brew install [email protected]
Warning: No available formula with the name "[email protected]".
==> Searching for similarly named formulae and casks...
Error: No formulae or casks found for [email protected].

:(

cfergeau · 2024-01-24T12:01:18Z

For what it's worth, since this is an issue related to the qemu build available in brew, the discussion is better suited for this homebrew issue: Homebrew/homebrew-core#159971

nokcm · 2024-01-24T18:19:38Z

Removing everything, and installing dmg podman-desktop worked for me.
Here's the exact steps I took.

First remove any machines you have

podman machine rm --force

Then remove everything you have installed from homebrew (don't include podman-desktop if you haven't installed it)

brew uninstall podman-desktop podman qemu

Then remove all podman caches:

rm -rf ~/.config/containers  
rm -rf ~/.local/share/containers
rm ~/.ssh/podman*

Then download podman desktop dmg from: https://podman-desktop.io/downloads
Then install podman dmg, It will prompt you that podman is not installed, follow the instruction and install it through podman-desktop. Then it will ask you to create a VM. Follow the instructions to create a VM. Wait for the machine to start.

Now you can go back to developing

benz0li · 2024-01-25T09:01:38Z

@macports users: Stay with QEMU v8.0.5; do not update to v8.2.0.

Cross reference: https://trac.macports.org/ticket/67731#comment:25

andremayer · 2024-01-26T07:54:47Z

@macports users: Stay with QEMU v8.0.5; do not update to v8.2.0.

Cross reference: https://trac.macports.org/ticket/67731#comment:25

Hi @benz0li how are you? Can you share the brew install instructions for this QEMU specific version v8.0.5? I got mine upgraded to latest 8.2.0 and now it is no longer working due this "Waiting for VM" issue. The command below will not work, correct?

brew install [email protected]

benz0li · 2024-01-26T07:57:49Z

Can you share the brew install instructions for this QEMU specific version v8.0.5?

@andremayer I am using MacPorts and not Homebrew.

slemeur · 2024-01-26T11:09:14Z

Along with the comment here: #20776 (comment) this is what I've done and worked on my side for M3.

If you are on M1/M2, the recommended path is to update to Podman 4.9.

1 - Remove everything podman and qemu to get a clean environment:

remove eventual installation from podman/podman desktop installer from sudo rm -rf opt/podman
remove brew installations
- brew uninstall podman-desktop
- brew uninstall podman
- brew uninstall qemu
cleanup of podman files
- rm -rf ~/.ssh/podman-machine-default
- rm -rf ~/.ssh/podman-machine-default.pub
- rm -rf ~/.local/share/containers
- rm -rf ~/.config/containers

2 - Reinstall using brew

`brew install podman``

3 - Install patched EDK2

Make sure you have bunzip2 (if not brew install bzip2)
Make sure QEMU is installed at the following path /opt/homebrew/Cellar/qemu/8.2.0 (if you are using a different path, just adapt the command below)
curl -sL https://github.com/AkihiroSuda/qemu/raw/704f7cad5105246822686f65765ab92045f71a3b/pc-bios/edk2-aarch64-code.fd.bz2 | bunzip2 > /opt/homebrew/Cellar/qemu/8.2.0/share/qemu/edk2-aarch64-code.fd

Now you should be able to do podman machine init and podman machine start

You can then reinstall Podman Desktop (either brew or Podman Desktop website)

The situation should get better with the upcoming release of QEMU 8.2.1

Note: If you are on M1/M2, you should be fine with the latest release of Podman 4.9. If not, please raise it!

fuzzball81 · 2024-01-26T21:31:33Z

I am using a M1 with Podman 4.9 installed via brew. I am still seeing the issue. I have not tried to patch qemu like suggested as above. I did make sure to remove my old vm and re-ran podman machine init before running podman machine start

benz0li · 2024-01-26T21:37:01Z

@slemeur @fuzzball81 Please check HFS+/APFS compression of edk2-aarch64-code.fd. Most likely this is the problem.

See https://trac.macports.org/ticket/67731#comment:14

fuzzball81 · 2024-01-26T21:43:26Z

@benz0li I am using homebrew but checked as you have recommended and got the following
afsctool -l /opt/homebrew/share/qemu/edk2-aarch64-code.fd /opt/homebrew/share/qemu/edk2-aarch64-code.fd is not HFS+/APFS compressed.

lestex · 2024-01-28T01:52:23Z

I'm experiencing this on M1 pro as well, a downgrade of qemu to 8.1.3 helped, so I'll stick to it for a time being.

Hi @lestex Can you share how you downgraded qemu back to 8.1.3? I tried running this on my macOS but didn't work:
❯ brew install [email protected]
Warning: No available formula with the name "[email protected]".
==> Searching for similarly named formulae and casks...
Error: No formulae or casks found for [email protected].
:(

Like here #21088 (comment)

adrian-moisa · 2024-01-28T21:32:49Z

I had the same issue on Mac M1 Pro. "Waiting for VM". Got it working by reverting to qemu 8.1.3. It started using latest podman 4.9.0.

podman machine init -m 3072 - tried it as suggested, did not help.
I tried several earlier podman versions up to 4.8.0. No luck.
podman machine start --log-level=debug - Retrieve more info about the failure. Thanks to this command I got out this error message from qemu: Synchronous Exception at 0x00000000BC562000 ASSERT [ArmCpuDxe] /home/kraxel/projects/qemu/roms/edk2/ArmPkg/Library/DefaultExceptionHandlerLib/Arch64/DefaultExceptionHandler.c(343): ((BOOLEAN)(0==1))
Following hints from here: Some people suggest reverting to an older qemu - qemu ASSERT [ArmCpuDxe] DefaultExceptionHandler.c:333 on Mac M3, Synchronous Exception at 0x00000000BC562000
I managed to get it running by reverting qemu to 8.1.3 qemu.rb. Reverting brew version instructions here: How To Install Older Versions of Homebrew Packages @andremayer

Edit:
Looks like the answer is buried in many answers. A plea to the original author @peter-crist . Please append the description to let people know that there's are 2 ways to fix: via the rollback of qemu or via applehv provider. I wasted 3 hours looking for the answer. Had it been in the first post it would have been only 30 mins lost. Cheers!

fuzzball81 · 2024-01-29T14:34:59Z

I can confirm using the 8.1.3 version of qemu does allow the VM to start on a M1 on macOS 14.3 with podman 4.9.

cfergeau · 2024-01-30T10:38:45Z

QEMU 8.2.1 has been released and is available in brew. Hopefully this fixes this issue.

robahtou · 2024-01-30T11:13:56Z

Can confirm that the update to QEMU 8.2.1 fixed the issue!!
I made sure to start with a clean slate so removed all the programs and folders/files as has been stated above.

benoitschipper · 2024-01-30T11:16:14Z

Hey All,

Just did the following to make this work without downgrading (Thanks @cfergeau and @robahtou for the mention's):

Remove the Machine:

podman machine rm
...
Are you sure you want to continue? [y/N] y

# Press y to make sure to remove everything

Upgrade to the latest QEMU:

brew update && brew upgrade
...
==> Upgrading qemu
  8.2.0 -> 8.2.1

Re-Init your Podman Machine:

Extracting compressed file: podman-machine-default_fedora-coreos-39.20240112.2.0-qemu.aarch64.qcow2: done
Image resized.
Machine init complete
To start your machine run:

	podman machine start

Start your Podman Machine:

Starting machine "podman-machine-default"
Waiting for VM ...
Mounting volume... /Users:/Users
Mounting volume... /private:/private
Mounting volume... /var/folders:/var/folders

This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:

        podman machine set --rootful

API forwarding listening on: /var/run/docker.sock
Docker API clients default to this address. You do not need to set DOCKER_HOST.

Machine "podman-machine-default" started successfully

This worked for me on M1, M2 and M3! 🥳

dedenf · 2024-01-31T03:49:10Z

just want to update my issue, after upgrading QEMU to 8.2.1, the problem seems go away, tried using applehv but somehow if i did not set the amount of disk, it will took all of the available space and crippling my system, so upgrading QEMU works 👍 .

now i can pull and operate as usual

  version:
  APIVersion: 4.8.3
  Built: 1704291040
  BuiltTime: Wed Jan  3 21:10:40 2024
  GitCommit: ""
  GoVersion: go1.21.5
  Os: linux
  OsArch: linux/arm64
  Version: 4.8.3

QEMU emulator version 8.2.1
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers

cfergeau · 2024-01-31T09:05:06Z

it will took all of the available space and crippling my system

I don't know what you saw exactly, but while it's true applehv will create a 100GB disk image, it is a sparse image, and it won't use 100GB on disk unless it's filled.
It's doing the equivalent of:

$ truncate -s 100G foo.img
$ du -sh foo.img
0

dedenf · 2024-02-01T09:03:59Z

@cfergeau so the system prompt me with warning that i had low free space after initiatingpodman machine init using applehv as its image, during the extraction it took more than 100GB, i had like 130GB+ free space at that time, but all of them taken by the extraction.

cfergeau · 2024-02-09T10:28:57Z

@cfergeau so the system prompt me with warning that i had low free space after initiatingpodman machine init using applehv as its image, during the extraction it took more than 100GB, i had like 130GB+ free space at that time, but all of them taken by the extraction.

Turns out podman did not create sparse files when extracting its disk images, but that's been solved in the main branch.

thiner · 2024-03-13T15:43:55Z

I followed @benoitschipper's guide, fixed the problem. One more step I had to do is that I uninstalled homebrew and then install it back. The reason is that I migrated my Mac system from previous Intel cpu Mac Book Pro to a new M3 Mac Book Pro. When I ran the podman machine start command, it prompted that my qemu is a x86 binary. I tried to reinstall qemu but that didn't work. I solved the problem by purge existing homebrew, and reinstall it.

Luap99 · 2024-04-04T10:00:47Z

podman 5.0 no longer supports qemu on macos and uses the apple hypervisor by default.

peter-crist added the kind/bug Categorizes issue or PR as related to a bug. label Nov 25, 2023

peter-crist changed the title ~~podman machine start stuck "Waiting for VM" indefinitely with qemu synchronous exception~~ podman machine start stuck "Waiting for VM" indefinitely with qemu synchronous exception MacOS M3 Nov 25, 2023

Luap99 added macos MacOS (OSX) related machine labels Nov 27, 2023

Luap99 mentioned this issue Dec 1, 2023

podman machine start stuck starting status on Apple M3 Max #20859

Closed

themr0c mentioned this issue Jan 26, 2024

docs: troubleshooting installation on macOS M1/M2/M3 podman-desktop/podman-desktop#5704

Closed

adrian-moisa mentioned this issue Jan 28, 2024

Podman machine start stuck at Waiting for VM ... #21088

Closed

lastmjs mentioned this issue Feb 17, 2024

Live reload demergent-labs/azle#1653

Closed

24 tasks

Luap99 closed this as completed Apr 4, 2024

stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Jul 4, 2024

stale-locking-app bot locked as resolved and limited conversation to collaborators Jul 4, 2024

podman machine start stuck "Waiting for VM" indefinitely with qemu synchronous exception MacOS M3 #20776

podman machine start stuck "Waiting for VM" indefinitely with qemu synchronous exception MacOS M3 #20776

Comments

peter-crist commented Nov 25, 2023 • edited Loading

Issue Description

Steps to reproduce the issue

Describe the results you received

Describe the results you expected

podman info output

Podman in a container

Privileged Or Rootless

Upstream Latest Release

danielroseman commented Nov 26, 2023

peter-crist commented Nov 26, 2023

jwhostet commented Nov 27, 2023

peter-crist commented Nov 27, 2023

mchataigner commented Nov 29, 2023 • edited Loading

jaydorsey commented Nov 29, 2023

robahtou commented Nov 29, 2023 • edited Loading

peter-crist commented Nov 30, 2023

jaydorsey commented Nov 30, 2023

peter-crist commented Nov 30, 2023

osamamunir23 commented Dec 5, 2023

jordyguntur commented Dec 8, 2023

relistan commented Dec 8, 2023 • edited Loading

pantaovay commented Dec 9, 2023

herblet commented Dec 11, 2023

m8nmueller commented Dec 12, 2023

nzhuk98 commented Dec 15, 2023

nutshellfool commented Dec 20, 2023

FullofQuarks commented Dec 21, 2023

denisborisov commented Dec 21, 2023

robahtou commented Dec 21, 2023

rhatdan commented Dec 21, 2023

robahtou commented Dec 21, 2023

denisborisov commented Dec 21, 2023

lockcrocodilegiraffe commented Dec 21, 2023

lestex commented Jan 23, 2024

cbr7 commented Jan 23, 2024 • edited Loading

andremayer commented Jan 24, 2024 • edited Loading

cfergeau commented Jan 24, 2024

nokcm commented Jan 24, 2024

benz0li commented Jan 25, 2024

andremayer commented Jan 26, 2024

benz0li commented Jan 26, 2024

slemeur commented Jan 26, 2024

fuzzball81 commented Jan 26, 2024

benz0li commented Jan 26, 2024

fuzzball81 commented Jan 26, 2024

lestex commented Jan 28, 2024

adrian-moisa commented Jan 28, 2024 • edited Loading

fuzzball81 commented Jan 29, 2024

cfergeau commented Jan 30, 2024

robahtou commented Jan 30, 2024

benoitschipper commented Jan 30, 2024

dedenf commented Jan 31, 2024

cfergeau commented Jan 31, 2024

dedenf commented Feb 1, 2024

cfergeau commented Feb 9, 2024

thiner commented Mar 13, 2024

Luap99 commented Apr 4, 2024

`podman machine start` stuck "Waiting for VM" indefinitely with qemu synchronous exception MacOS M3 #20776

`podman machine start` stuck "Waiting for VM" indefinitely with qemu synchronous exception MacOS M3 #20776

peter-crist commented Nov 25, 2023 •

edited

Loading

mchataigner commented Nov 29, 2023 •

edited

Loading

robahtou commented Nov 29, 2023 •

edited

Loading

relistan commented Dec 8, 2023 •

edited

Loading

cbr7 commented Jan 23, 2024 •

edited

Loading

andremayer commented Jan 24, 2024 •

edited

Loading

adrian-moisa commented Jan 28, 2024 •

edited

Loading