Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't start machine on M1 #13010

Closed
per6x opened this issue Jan 26, 2022 · 6 comments
Closed

Can't start machine on M1 #13010

per6x opened this issue Jan 26, 2022 · 6 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine

Comments

@per6x
Copy link

per6x commented Jan 26, 2022

/kind bug

Description

Steps to reproduce the issue:

  1. I first initialised a new machine:
$ podman --log-level=debug machine init m1       
INFO[0000] podman filtering at log level debug          
Extracting compressed file
  1. Then I tried to run the machine and got this:
$ podman machine start m1 
INFO[0000] waiting for clients...                       
INFO[0000] listening tcp://127.0.0.1:7777               
INFO[0000] new connection from  to /var/folders/t1/wk3fwzss61vb_rjtwmnz1y4w0000gn/T/podman/qemu_m1.sock 
Waiting for VM ...
qemu-system-x86_64: Unknown Error
Error: dial unix /var/folders/t1/wk3fwzss61vb_rjtwmnz1y4w0000gn/T/podman/m1_ready.sock: connect: connection refused
ERRO[0003] cannot receive packets from , disconnecting: cannot read size from socket: EOF                                                                                                                   
ERRO[0003] cannot read size from socket: EOF        

Any Ideas on how to solve this?

Output of podman version:

$ podman --version
podman version 3.4.4

Output of uname -a:

$ uname -a
Darwin laptop.local 21.2.0 Darwin Kernel Version 21.2.0: Sun Nov 28 20:29:10 PST 2021; root:xnu-8019.61.5~1/RELEASE_ARM64_T8101 arm64

I have macOS Monterey Version 12.1 installed.

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Jan 26, 2022
@baude
Copy link
Member

baude commented Jan 26, 2022

make sure you are using the qemu version installed along with podman in brew. secondly, if you have used or are using rosetta, that can mess up brew as well.

@Luap99 Luap99 added the machine label Jan 26, 2022
@laszlo-major
Copy link

Same issue, same version of Monterey, not using rosetta in the terminal and brew was also installed in apple silicon native mode.

podman machine --log-level=debug start
INFO[0000] podman filtering at log level debug          
DEBU[0000] [/usr/local/bin/qemu-system-aarch64 -m 2048 -smp 1 -fw_cfg name=opt/com.coreos/config,file=/Users/major/.config/containers/podman/machine/qemu/podman-machine-default.ign -qmp unix://var/folders/9t/g297flsj6zv0f819pl04jqrr0000gn/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/9t/g297flsj6zv0f819pl04jqrr0000gn/T/podman/podman-machine-default_ready.sock,server=on,wait=off,id=podman-machine-default_ready -device virtserialport,chardev=podman-machine-default_ready,name=org.fedoraproject.port.0 -accel hvf -accel tcg -cpu cortex-a57 -M virt,highmem=off -drive file=/usr/local/share/qemu/edk2-aarch64-code.fd,if=pflash,format=raw,readonly=on -drive file=/Users/major/.local/share/containers/podman/machine/qemu/podman-machine-default_ovmf_vars.fd,if=pflash,format=raw -drive if=virtio,file=/Users/major/.local/share/containers/podman/machine/qemu/podman-machine-default_fedora-coreos-35.20220103.2.0-qemu.aarch64.qcow2] 
[/opt/homebrew/opt/podman/libexec/gvproxy -listen tcp://127.0.0.1:7777 -listen-qemu unix:///var/folders/9t/g297flsj6zv0f819pl04jqrr0000gn/T/podman/qemu_podman-machine-default.sock -pid-file /var/folders/9t/g297flsj6zv0f819pl04jqrr0000gn/T/podman/podman-machine-default.pid -ssh-port 50546 --debug]
DEBU[0000] Using search domains: [nodomain basefarm.net basefarm.com basefarm.no lan] 
INFO[0000] waiting for clients...                       
INFO[0000] listening tcp://127.0.0.1:7777               
DEBU[0000] [/usr/local/bin/qemu-system-aarch64 -m 2048 -smp 1 -fw_cfg name=opt/com.coreos/config,file=/Users/major/.config/containers/podman/machine/qemu/podman-machine-default.ign -qmp unix://var/folders/9t/g297flsj6zv0f819pl04jqrr0000gn/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/9t/g297flsj6zv0f819pl04jqrr0000gn/T/podman/podman-machine-default_ready.sock,server=on,wait=off,id=podman-machine-default_ready -device virtserialport,chardev=podman-machine-default_ready,name=org.fedoraproject.port.0 -accel hvf -accel tcg -cpu cortex-a57 -M virt,highmem=off -drive file=/usr/local/share/qemu/edk2-aarch64-code.fd,if=pflash,format=raw,readonly=on -drive file=/Users/major/.local/share/containers/podman/machine/qemu/podman-machine-default_ovmf_vars.fd,if=pflash,format=raw -drive if=virtio,file=/Users/major/.local/share/containers/podman/machine/qemu/podman-machine-default_fedora-coreos-35.20220103.2.0-qemu.aarch64.qcow2] 
INFO[0000] new connection from  to /var/folders/9t/g297flsj6zv0f819pl04jqrr0000gn/T/podman/qemu_podman-machine-default.sock 
Waiting for VM ...
Error: dial unix /var/folders/9t/g297flsj6zv0f819pl04jqrr0000gn/T/podman/podman-machine-default_ready.sock: connect: no such file or directory
ERRO[0003] cannot receive packets from , disconnecting: cannot read size from socket: EOF 
ERRO[0003] cannot read size from socket: EOF                                      

Are the steps described in https://github.com/containers/podman/blob/5d2c03e8b0283446aec6da2ac4ad45262c4244bd/docs/tutorials/mac_experimental.md still required? And if yes, where are we supposed to find the binaries used in step 8?

@baude
Copy link
Member

baude commented Jan 26, 2022

@laszlo-major you no longer need to build it ... i will update the docs

@baude
Copy link
Member

baude commented Jan 26, 2022

@laszlo-major also, this is different ... notice your calls are calling the aarch64 qemu. The original reported shows it calling x86_64

@daiaji
Copy link

daiaji commented Jan 29, 2022

@laszlo-major also, this is different ... notice your calls are calling the aarch64 qemu. The original reported shows it calling x86_64

I don't particularly understand, isn't M1 the SOC of ARM64? Why would QEMU for X86_64 be started, wouldn't this cause a considerable performance penalty? Does arm not provide virtualization technology similar to VT-x?

@per6x
Copy link
Author

per6x commented Jan 29, 2022

I solved the problem by reinstalling both podman and qemu. Apparently either one of them or both were installed for x86 and not arm.
Thanks for the help!

@per6x per6x closed this as completed Jan 29, 2022
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine
Projects
None yet
Development

No branches or pull requests

5 participants