Error in colima start

[luizthadeu]

Description

colima start --very-verbose
TRAC[0000] cmd ["limactl" "info"]
TRAC[0000] cmd ["limactl" "list" "colima" "--json"]
INFO[0000] starting colima
INFO[0000] runtime: docker
TRAC[0000] cmd ["limactl" "list" "colima" "--json"]
INFO[0000] preparing network ... context=vm TRAC[0000] cmd ["/usr/local/bin/colima" "daemon" "status" "default"] TRAC[0000] cmd ["/usr/local/bin/colima" "daemon" "start" "default" "--gvproxy" "--verbose"] INFO[0000] starting ... context=vm TRAC[0000] cmd ["limactl" "start" "colima"]

Using the existing instance "colima" [hostagent] Starting QEMU (hint: to watch the boot progress, see "/Users/temp/.lima/colima/serial.log") SSH Local Port: 52575 [hostagent] QEMU has exited exiting, status={Running:false Degraded:false Exiting:true Errors:[] SSHLocalPort:0} (hint: see "/Users/temp/.lima/colima/ha.stderr.log") FATA[0000] error starting vm: error at 'starting': exit status 1

Version

Colima Version: 0.4.4 Lima Version: 0.11.3 Qemu Version: 5.2.0

Operating System

• [X] macOS Intel
• [ ] macOS M1
• [ ] Linux

Reproduction Steps

1. Install > brew install colima docker
2. colima start

Expected behaviour

No response

Additional context

No response

[luizthadeu]

Append:

colima/serial.log > 0 bytes

colima/ha.stderr.log

{"level":"debug","msg":"Creating iso file /Users/temp/.lima/colima/cidata.iso","time":"2022-08-05T14:06:28-03:00"}
{"level":"debug","msg":"Using /var/folders/gg/ykgx8p291tg9gx94x_368ct40000gp/T/diskfs_iso1170600255 as workspace","time":"2022-08-05T14:06:28-03:00"}
{"level":"debug","msg":"firmware candidates = [/Users/temp/.local/share/qemu/edk2-x86_64-code.fd /Users/temp/.colima/_wrapper/4e1b408f843d1c63afbbdcf80c40e4c88d33509f/share/qemu/edk2-x86_64-code.fd /usr/share/OVMF/OVMF_CODE.fd /usr/share/qemu/ovmf-x86_64-code.bin /usr/share/edk2-ovmf/x64/OVMF_CODE.fd]","time":"2022-08-05T14:06:28-03:00"}
{"level":"debug","msg":"OpenSSH version 8.6.1 detected","time":"2022-08-05T14:06:28-03:00"}
{"level":"debug","msg":"AES accelerator seems available, prioritizing [email protected] and [email protected]","time":"2022-08-05T14:06:28-03:00"}
{"level":"info","msg":"Starting QEMU (hint: to watch the boot progress, see \"/Users/temp/.lima/colima/serial.log\")","time":"2022-08-05T14:06:28-03:00"}
{"level":"debug","msg":"qCmd.Args: [/Users/temp/.colima/_wrapper/4e1b408f843d1c63afbbdcf80c40e4c88d33509f/bin/qemu-system-x86_64 -m 2048 -cpu host -machine q35,accel=hvf -smp 2,sockets=1,cores=2,threads=1 -drive if=pflash,format=raw,readonly=on,file=/Users/temp/.colima/_wrapper/4e1b408f843d1c63afbbdcf80c40e4c88d33509f/share/qemu/edk2-x86_64-code.fd -boot order=d,splash-time=0,menu=on -drive file=/Users/temp/.lima/colima/basedisk,media=cdrom,readonly=on -drive file=/Users/temp/.lima/colima/diffdisk,if=virtio -cdrom /Users/temp/.lima/colima/cidata.iso -netdev user,id=net0,net=192.168.5.0/24,dhcpstart=192.168.5.15,hostfwd=tcp:127.0.0.1:52575-:22 -device virtio-net-pci,netdev=net0,mac=52:55:55:22:0b:1a -device virtio-rng-pci -display none -device virtio-vga -device virtio-keyboard-pci -device virtio-mouse-pci -device qemu-xhci,id=usb-bus -parallel none -chardev socket,id=char-serial,path=/Users/temp/.lima/colima/serial.sock,server=on,wait=off,logfile=/Users/temp/.lima/colima/serial.log -serial chardev:char-serial -chardev socket,id=char-qmp,path=/Users/temp/.lima/colima/qmp.sock,server=on,wait=off -qmp chardev:char-qmp -name lima-colima -pidfile /Users/temp/.lima/colima/qemu.pid]","time":"2022-08-05T14:06:28-03:00"}
{"level":"debug","msg":"qemu[stderr]: time=\"2022-08-05T14:06:28-03:00\" level=fatal msg=\"dial unix /Users/temp/.colima/default/daemon/gvproxy.sock: connect: permission denied\"","time":"2022-08-05T14:06:28-03:00"}
{"error":"exit status 1","level":"info","msg":"QEMU has exited","time":"2022-08-05T14:06:28-03:00"}
{"level":"info","msg":"Waiting for the essential requirement 1 of 5: \"ssh\"","time":"2022-08-05T14:06:28-03:00"}

[hazardv]

I got the same error after following the same steps on an M1 mac

[abiosoft]

Is this still the case? Do you get same experience when you use the development version brew install --HEAD colima?

[hazardv]

Is this still the case? Do you get same experience when you use the development version brew install --HEAD colima?

I am not getting that error anymore. The issue was resolved for me by making sure to use the ARM based brew installation when installing Colima.