FATA[0000] error starting vm: error at 'starting': exit status 1

[AraceliAL]

Description

Good morning!!!

I get the following error when trying to start colima.... I tried multiple things, installing and uninstalling colima again and the same with docker. I also read the following threads but there were not useful at the end (ttps://github.com//issues/20).

do you have any idea of what can I do?
The error is the following

INFO[0000] starting colima                              
INFO[0000] runtime: docker                              
INFO[0000] starting ...                                  context=vm
> Using the existing instance "colima"
> [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/araceli.aznar/.lima/colima/serial.log")
> exiting, status={Running:false Degraded:false Exiting:true Errors:[] SSHLocalPort:0} (hint: see "/Users/araceli.aznar/.lima/colima/ha.stderr.log")
FATA[0000] error starting vm: error at 'starting': exit status 1 

The /Users/araceli.aznar/.lima/colima/serial.logis empty and in /Users/araceli.aznar/.lima/colima/ha.stderr.logthere's the following:

{"level":"debug","msg":"Creating iso file /Users/araceli.aznar/.lima/colima/cidata.iso","time":"2022-12-19T10:52:24+01:00"}
{"level":"debug","msg":"Using /var/folders/_x/j8w1w9hs38vgv3p4bt0n5bn40000gp/T/diskfs_iso2328349935 as workspace","time":"2022-12-19T10:52:24+01:00"}
{"level":"debug","msg":"OpenSSH version 9.0.1 detected","time":"2022-12-19T10:52:24+01:00"}
{"level":"debug","msg":"AES accelerator seems available, prioritizing aes128-gcm@openssh.com and aes256-gcm@openssh.com","time":"2022-12-19T10:52:24+01:00"}
{"level":"info","msg":"Starting VZ (hint: to watch the boot progress, see \"/Users/araceli.aznar/.lima/colima/serial.log\")","time":"2022-12-19T10:52:24+01:00"}
{"level":"debug","msg":"Start udp server listening on: 127.0.0.1:49553","time":"2022-12-19T10:52:24+01:00"}
{"level":"debug","msg":"Start tcp server listening on: 127.0.0.1:49973","time":"2022-12-19T10:52:24+01:00"}
{"level":"debug","msg":"Using search domains: [odigeo.org colt.edreams.com services.odigeo.com liligo.com fra4.odigeo.com ec2.odigeo.com par3.odigeo.com]","time":"2022-12-19T10:52:24+01:00"}
{"level":"info","msg":"new connection from  to ","time":"2022-12-19T10:52:24+01:00"}
{"level":"fatal","msg":"Error Domain=VZErrorDomain Code=1 Description=\"Internal Virtualization error. The virtual machine failed to start.\" UserInfo={\n    NSLocalizedFailure = \"Internal Virtualization error.\";\n    NSLocalizedFailureReason = \"The virtual machine failed to start.\";\n}","time":"2022-12-19T10:52:24+01:00"}

Thanks a lot and sorry for the inconvenience

Version

Colima Version: 0.5.0
Lima Version: 0.14.1
Qemu Version: 7.2.0

Operating System

• macOS Intel
• macOS M1
• Linux

Reproduction Steps

1.arch -x86_64 brew install colima
2.arch -x86_64 brew install docker
3. colima start

Expected behaviour

Create VM

Additional context

None

[AraceliAL]

I finally had to reinstall hombrew, it was an architecture problem.

Thanks anyway!

[abiosoft]

Glad you were able to resolve it.