I have checked the log messages, it is strange.
{“level”:“fatal”,“msg”:“nested virtualization is not supported on this device”,“time”:“2025-05-07T13:35:17+03:00”}
Any idea?
Actually I setup a new machine from TimeMachine backup, so I did not remember. But I have executed colima delete then initialize again like this, colima start --nested-virtualization --runtime incus. Unfortunately, the previous statement appeared in the log again.
Regards.
Hi,
Doing some vm tests in M3, and get those errors most of the time, can you guide me how to debug / analyze the problem in here?
2025-05-08 09:16:02 ⌚ D0928 in ~
○ → incus shell testubuntu
Error while executing alias expansion: incus exec testubuntu -- su -l
Error: Only running operations can be connected
2025-05-08 09:16:32 ⌚ D0928 in ~
○ → incus stop testubuntu
Error: Failed shutting down instance, status is "Running": context deadline exceeded
Try `incus info --show-log testubuntu` for more info
P.S.
There is something wrong with the Virtualization.framework, cpu load is over 100 and vm Ubuntu GUI takes too much time to open, very slow.
Regards.
My mac version is 15.4.1, Nowadays I have no problem opening a vm but GUI problem. I have installed a gui environment on Ubuntu 24.04 vm but it stucks and consume too much CPU (over %100). I suppose (but not sure) the problem related with /opt/homebrew/bin/remote-viewer spice+unix:/// (remote-viewer)
Regards.
GPU passthrough isn’t very likely as you’d need to have an extra GPU on the host to begin with, then somehow manage to pass that GPU through two level of VMs.
If you’re willing to pay for it, the Pro version of Parallels supports nested virtualization (on M3), can share the Mac host network adapter, and also pass thru a raw disk (e.g. an external Thunderbolt disk) to a VM running Incus.
For those trying it out: you need colima start --network-address to make this work. It prompts you for your sudo password to add the required route. FAQ ref
The prompt for sudo password is only once, subsequent starts do not prompt.
If not for the prompt, it would’ve been made the default experience. There is a long term plan to have a pkg installer on macOS which should address this.
Sorry to reopen this post again, but I just want to know how to upgrade incus version in colima.
○ → colima version
colima version 0.10.1
git commit: ed905203afdbc6fd4eae6cc301918099ff31e86e
runtime: incus
arch: aarch64
Client version: 6.21
Server version: 6.14
% colima version
colima version 0.10.0
git commit: 7f5f27de13d921e66e3a78de0a838ddec581871a
runtime: incus
arch: aarch64
Client version: 6.17
Server version: 6.21
% colima --help
Colima provides container runtimes on macOS with minimal setup.
Usage:
colima [command]
Available Commands:
completion Generate completion script
delete delete and teardown Colima
help Help about any command
kubernetes manage Kubernetes cluster
list list instances
model manage AI models (requires docker runtime and krunkit VM type)
nerdctl run nerdctl (requires containerd runtime)
prune prune cached downloaded assets
restart restart Colima
ssh SSH into the VM
ssh-config show SSH connection config
start start Colima
status show the status of Colima
stop stop Colima
template edit the template for default configurations
update update the container runtime <<<<<
version print the version of Colima