colima icon indicating copy to clipboard operation
colima copied to clipboard

vm fails to start (macOS Intel)

Open ardeguire opened this issue 2 years ago • 15 comments

Describe the Issue

VM hangs at start:

% colima start
INFO[0000] starting colima                              
INFO[0000] runtime: docker                              
INFO[0000] preparing network ...                         context=vm
INFO[0000] starting ...                                  context=vm
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="[hostagent] Waiting for the essential requirement 1 of 5: \"ssh\""
> msg="did not receive an event with the \"running\" status"
FATA[0600] error starting vm: error at 'starting': exit status 1 

Version

Colima Version:

What is the output of colima version:

% colima version
colima version 0.4.2
git commit: f112f336d05926d62eb6134ee3d00f206560493b

Lima Version:

What is the output of limactl --version:

% limactl --version
limactl version 0.11.1

Qemu Version

What is the output of qemu-img --version:

% qemu-img --version
qemu-img version 7.0.0

Operating System

  • [ x] macOS Intel
  • [ ] macOS m1
  • [ ] Linux

To Reproduce

Steps to reproduce the behavior:

  1. brew install colima
  2. brew install docker
  3. colima start

Expected behavior

VM to start

Additional context

Add any other context about the problem here. ha.stderr.log serial.log

ardeguire avatar Jun 21 '22 09:06 ardeguire

This is very strange.

  • What version of macOS are you on?
  • How did you install qemu?

abiosoft avatar Jun 21 '22 13:06 abiosoft

macOS Monterey 12.3.1 (21E258) qemu was installed as a dependency with brew install colima

ardeguire avatar Jun 21 '22 14:06 ardeguire

I don't know if this is relevant at all, but I am able to start lima with the "docker" configuration. It's kind of slow (~5 minutes), but it does eventually complete successfully complete

ardeguire avatar Jun 21 '22 15:06 ardeguire

I don't know if this is relevant at all, but I am able to start lima with the "docker" configuration. It's kind of slow (~5 minutes), but it does eventually complete successfully complete

Except your internet is relatively slow, this sounds more like an emulation and the host CPU not being utilised directly. Are you on a relatively old MacBook?

abiosoft avatar Jun 21 '22 15:06 abiosoft

2019 MBP, 2.6 GHz i7.

My internet is relatively slow due to my company's proxy settings, but it should still work quickly once things are cached on my machine

ardeguire avatar Jun 22 '22 12:06 ardeguire

I will close this issue for now, as I don't have the time to troubleshoot or power to change my company's proxy settings and other restrictions.

ardeguire avatar Jun 24 '22 14:06 ardeguire

I will close this issue for now, as I don't have the time to troubleshoot or power to change my company's proxy settings and other restrictions.

I would argue otherwise. Let us leave it open.

abiosoft avatar Jun 24 '22 15:06 abiosoft

I was seeing the exact same on a M1 Max. Cleaning out all the files in $HOME/.lima/colima/ fixed the issue. I think in my case it was just super old vm image files as I re-installed colima after many months

Moulick avatar Jun 24 '22 17:06 Moulick

I am experiencing the exact same problem, Intel MacBook Pro (16-inch, 2019). It was working weeks ago, all of the sudden it broke. Cleaning $HOME/.lima/colima/ or deleting Colima did not help.

fortesdev avatar Jun 28 '22 07:06 fortesdev

@fortesdev did you update anything?

abiosoft avatar Jun 28 '22 07:06 abiosoft

Yes, @abiosoft, I updated the common: Xcode to Version 13.4.1 + command line tools And MacOS Monterrey to 12.4 But note this: I just deleted HEAD, installed v0.3.4, and that old version works like a charm.

fortesdev avatar Jun 28 '22 08:06 fortesdev

Coming back to this, it started working today. I'm not sure what changed, but I haven't updated anything explicitly. Any logs or additional information you'd like, @abiosoft?

colima version 0.4.2
git commit: f112f336d05926d62eb6134ee3d00f206560493b

runtime: docker
arch: x86_64
client: v20.10.8
server: v20.10.11
% colima status
INFO[0000] colima is running                            
INFO[0000] arch: x86_64                                 
INFO[0000] runtime: docker                              
INFO[0000] mountType: sshfs                             
INFO[0000] socket: unix:///Users/deguire/.colima/default/docker.sock

ardeguire avatar Jul 01 '22 11:07 ardeguire

@ardeguire did you restart your machine?

abiosoft avatar Jul 01 '22 16:07 abiosoft

Yes, but I'm pretty sure I also restarted several times when I was attempting to troubleshoot when I first encountered the issue

ardeguire avatar Jul 21 '22 08:07 ardeguire