You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to run the colima start command with custom CPU, memory, and disk values.
colima start --cpu 4 --memory 6 --disk 64
The entire computer froze for a few seconds, and then crashed and rebooted. I did some more testing, and the CPU and disk flags are fine, the memory one causes the problem. Even just a simple colima start --memory 6 causes the crash.
The colima list command shows a default VM in a "Broken" state, with the correct memory value.
Describe the Issue
I tried to run the
colima start
command with custom CPU, memory, and disk values.The entire computer froze for a few seconds, and then crashed and rebooted. I did some more testing, and the CPU and disk flags are fine, the memory one causes the problem. Even just a simple
colima start --memory 6
causes the crash.The
colima list
command shows a default VM in a "Broken" state, with the correct memory value.Version
Colima Version:
colima version 0.4.2
git commit: f112f33
runtime: docker
arch: aarch64
client: v20.10.17
server: v20.10.11
Lima Version:
limactl version 0.11.0
Qemu Version
qemu-img version 7.0.0
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
Operating System
MacBook Pro (16-inch, 2021)
Mac OS 12.1 (21C52)
Chip: Apple M1 Max
Memory: 32GB
To Reproduce
Steps to reproduce the behavior:
colima start --memory 6
Expected behavior
A new colima profile is created.
Additional context
Running a plain
colima start
with default values works just fine. It's the custom memory value that causes a crash.The text was updated successfully, but these errors were encountered: