Colima fails to start when VM driver is set to `vz`.
- Vorherrschende Sprache
- Go
- Sterne
- 30.8k
- Forks
- 613
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Description
After setting `vmType: vz` I'm getting the following error message when starting Colima
```
→ colima start
INFO[0000] starting colima
INFO[0000] runtime: docker
INFO[0001] starting ... context=vm
> Using the existing instance "colima"
> Starting the instance "colima" with VM driver "vz"
> [hostagent] hostagent socket created at /Users/wujekbogdan/.colima/_lima/colima/ha.sock
> [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/wujekbogdan/.colima/_lima/colima/serial*.log")
> exiting, status={Running:false Degraded:false Exiting:true Errors:[] SSHLocalPort:0} (hint: see "/Users/wujekbogdan/.colima/_lima/colima/ha.stderr.log")
FATA[0001] error starting vm: error at 'starting': exit status 1
```
### Version
```
colima version 0.6.6
git commit: 9ed7f4337861931b4d0192ca5409683a4b7d1cdc
limactl version 0.19.0
qemu-img version 8.1.3
```
### Operating System
- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [X] Apple Silicon >= 14 (Sonoma)
- [ ] Linux
### Output of `colima status`
```
FATA[0000] colima is not running
```
### Reproduction Steps
1. set `vmType: vz`
2. run `colima start`
### Expected behaviour
Colima starts
### Additional context
- Everything works fine with `vmType: qemu`
- Not sure if it makes ant difference, but I tried various `mountType` settings because of the comment I found in the config that says _"Default: virtiofs (for vz), sshfs (for qemu)"_.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
The issue is about Colima failing to start with the vz VM driver on Apple Silicon macOS Sonoma. Check the hostagent logs at ~/.colima/_lima/colima/ha.stderr.log and serial*.log for error details. Investigate the integration between Colima and Lima's vz driver, focusing on the VM startup sequence. The fix likely involves the VM driver configuration or handling of the vz runtime on newer macOS versions.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- go, macos, shell
- Bereich
- cli, devops, tooling
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100