abiosoft / colima

Container runtimes on macOS (and Linux) with minimal setup
MIT License
18.9k stars 382 forks source link

Lima v0.20.0 breaks Colima #967

Closed aalbiach closed 8 months ago

aalbiach commented 8 months ago

Description

After launching the Homebrew package update, Colima stopped working. I noticed that in the last upgrade Lima was updated to the version v0.20.0.

Version

colima version 0.6.7 git commit: ba1be00e9aec47f2c1ffdacfb7e428e465f0b58a limactl version 0.20.0 qemu-img version 8.2.0

Operating System

Output of colima status

colima status
FATA[0000] colima is not running
colima list
PROFILE    STATUS     ARCH       CPUS    MEMORY    DISK     RUNTIME    ADDRESS
default    Stopped    aarch64    2       2GiB      60GiB

Reproduction Steps

  1. colima start

The execution gets stuck at this point:

> [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
> [hostagent] Waiting for the essential requirement 1 of 4: "ssh"

Expected behaviour

Colima starts the VM

Additional context

No response

AkihiroSuda commented 8 months ago
aalbiach commented 8 months ago

I have this errors:

ha.stderr.log
{"level":"debug","msg":"qemu[stderr]: qemu-system-aarch64: terminating on signal 2 from pid 63664 (\u003cunknown process\u003e)","time":"2024-01-20T11:16:28+01:00"}
{"error":"failed to execute `ssh -O exit -p 54500 127.0.0.1`, out=\"Control socket connect(/Users/alvaro.albiach/.colima/_lima/colima/ssh.sock): No such file or directory\\r\\n\": exit status 255","level":"warning","msg":"failed to exit SSH master","time":"2024-01-20T11:16:28+01:00"}
{"error":"dial unix /Users/alvaro.albiach/.colima/_lima/colima/qmp.sock: connect: no such file or directory","level":"warning","msg":"failed to open the QMP socket \"/Users/alvaro.albiach/.colima/_lima/colima/qmp.sock\", forcibly killing QEMU","time":"2024-01-20T11:16:28+01:00"}

serial.log
Error: Image at 000BFD35000 start failed: Not Found
Error: Image at 000BFC87000 start failed: Unsupported
Error: Image at 000BFC07000 start failed: Not Found
Tpm2GetCapabilityPcrs fail!
BdsDxe: failed to load Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x1,0x0)/Scsi(0x0,0x0): Not Found

serialp.log
[    3.268429] cloud-init[295]: 2024-01-20 10:10:22,473 - schema.py[WARNING]: Invalid cloud-config provided: Please run 'sudo cloud-init schema --system' to see the schema errors.
         Starting grub-initrd-fallb…0m - GRUB failed boot detection...
[  OK  ] Finished grub-initrd-fallb… - GRUB failed boot detection.

serialv.log
BdsDxe: failed to load Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x1,0x0)/Scsi(0x0,0x0): Not Found

The limactl start --video gets stuck at this point:

limactl start --video
INFO[0000] Using the existing instance "default"
INFO[0000] Starting the instance "default" with VM driver "qemu"
INFO[0000] QEMU binary "/opt/homebrew/bin/qemu-system-aarch64" seems properly signed with the "com.apple.security.hypervisor" entitlement
INFO[0001] [hostagent] hostagent socket created at /Users/alvaro.albiach/.lima/default/ha.sock
INFO[0001] [hostagent] Using existing firmware ("/Users/alvaro.albiach/.lima/default/qemu-efi-code.fd")
INFO[0001] [hostagent] Starting QEMU (hint: to watch the boot progress, see "/Users/alvaro.albiach/.lima/default/serial*.log")
INFO[0001] SSH Local Port: 60022
INFO[0001] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0011] [hostagent] Waiting for the essential requirement 1 of 4: "ssh"
INFO[0012] [hostagent] The essential requirement 1 of 4 is satisfied
INFO[0012] [hostagent] Waiting for the essential requirement 2 of 4: "user session is ready for ssh"
INFO[0012] [hostagent] The essential requirement 2 of 4 is satisfied
INFO[0012] [hostagent] Waiting for the essential requirement 3 of 4: "sshfs binary to be installed"
INFO[0052] [hostagent] Waiting for the essential requirement 3 of 4: "sshfs binary to be installed"
INFO[0092] [hostagent] Waiting for the essential requirement 3 of 4: "sshfs binary to be installed"

And on the video screen I only see lima-default login: _

AkihiroSuda commented 8 months ago

Are you using some corporate proxy or VPN stuff? With the standard limactl shell, does sudo apt-get install sshfs show any error?

aalbiach commented 8 months ago

Hi, sorry for the inconvenience, I solved it restarting the VPN and the proxy server.