Machine fails to start on Mac M1 Pro

[edeandrea]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Everything was working fine last week. I came back this morning from a long weekend and my podman vm won't start up. I get

╰─ podman machine start                      
Starting machine "podman-machine-default"
Waiting for VM ...
Error: dial unix /var/folders/6j/dk6dwmgd7874pjx7s9dknhxw0000gn/T/podman/podman-machine-default_ready.sock: connect: connection refused

I then removed the VM (via podman machine rm) and even uninstalled podman (brew uninstall podman).

I then re-installed podman via brew install podman (Yes I'm running the arm version of homebrew)

╰─ brew -v      
Homebrew 3.4.11
Homebrew/homebrew-core (git revision 391d3be1235; last commit 2022-05-31)
Homebrew/homebrew-cask (git revision 1d3a14e856; last commit 2022-05-31)

╰─ brew config 
HOMEBREW_VERSION: 3.4.11
ORIGIN: https://github.com/Homebrew/brew
HEAD: 30e3d8883cde265cbc16ff94b49a3ac14137590e
Last commit: 3 weeks ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 391d3be12354b9b68fbf930915f4a86e0c8b760d
Core tap last commit: 39 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_CORE_GIT_REMOTE: https://github.com/Homebrew/homebrew-core
HOMEBREW_MAKE_JOBS: 10
Homebrew Ruby: 2.6.8 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: 10-core 64-bit arm_firestorm_icestorm
Clang: 13.1.6 build 1316
Git: 2.36.1 => /opt/homebrew/bin/git
Curl: 7.79.1 => /usr/bin/curl
macOS: 12.4-arm64
CLT: 13.4.0.0.1.1651278267
Xcode: N/A
Rosetta 2: false

╰─ podman machine init --cpus 4 --memory 6144
Extracting compressed file
Image resized.
Machine init complete
To start your machine run:

	podman machine start

╰─ podman machine start                      
Starting machine "podman-machine-default"
Waiting for VM ...
Error: dial unix /var/folders/6j/dk6dwmgd7874pjx7s9dknhxw0000gn/T/podman/podman-machine-default_ready.sock: connect: connection refused

Output of podman version:

╰─ podman version      
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman. failed to create sshClient: connection to bastion host (ssh://core@localhost:61465/run/user/501/podman/podman.sock) failed: dial tcp [::1]:61465: connect: connection refused

Output of podman info --debug:

╰─ podman info --debug
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman. failed to create sshClient: connection to bastion host (ssh://core@localhost:61465/run/user/501/podman/podman.sock) failed: dial tcp [::1]:61465: connect: connection refused

Package info (e.g. output of rpm -q podman or apt list podman):

╰─ brew info podman     
podman: stable 4.1.0 (bottled), HEAD
Tool for managing OCI containers and pods
https://podman.io/
/opt/homebrew/Cellar/podman/4.1.0 (174 files, 46.3MB) *
  Poured from bottle on 2022-05-31 at 08:06:26
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/podman.rb
License: Apache-2.0
==> Dependencies
Build: go ✘, go-md2man ✘
Required: qemu ✔
==> Options
--HEAD
	Install HEAD version
==> Caveats
zsh completions have been installed to:
  /opt/homebrew/share/zsh/site-functions
==> Analytics
install: 21,057 (30 days), 58,692 (90 days), 149,471 (365 days)
install-on-request: 20,997 (30 days), 58,624 (90 days), 149,391 (365 days)
build-error: 0 (30 days)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes

[mheon]

@ashley-cui @baude PTAL

[ashley-cui]

Related: #14303

So far it seems like podman doesn't like qemu 7.0.0?

[edeandrea]

I don't see a way via homebrew to back qemu down to 6.2?

[arixmkii]

@edeandrea You can try my workaround mentioned here

[edeandrea]

@edeandrea You can try my workaround mentioned here

Thank you @arixmkii that worked!

@ashley-cui forcing qemu back down to 6.2 seems to have fixed the issue.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

Since this is an issue between qemu and MAC OS, I am going to close this issue.
qemu 7.* and MacOS 12.4 are supposed to work together now, as far as I know.