Looks like performance is impressive and the overhead is minimal.
Geekbench kept freezing in the multi-core tests, so I had to limit the VM to single CPU to get it to complete successfully. I am mainly interested in the single-core performance anyways.
You can suggest other tests or benchmarking tools to use.
The left window is the VM, right is the nested VM.
I got Incus and Colima up and running pretty quickly with your documentation - thanks!
Mac Mini M1 uname -a produces; Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:21 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T8103 arm64
$ incus version
Client version: 6.5
Server version: 6.4
Kind of weird that there is a different kernel in the container and also weird that it is an Ubuntu labled kernel on Debian. Is that the âcloud-initâ component? Or what is going on here?
Running uname -a inside the container produces;
Linux Trixie 6.8.0-39-generic #39-Ubuntu SMP PREEMPT_DYNAMIC Sat Jul 6 02:50:39 UTC 2024 aarch64 GNU/Linux
Itâs strange that the Incus Client and the Incus Server versions are different. They should be the same. Not critical, but this one is weird.
As already said, Incus requires a Linux system to work, and in the case of macOS (and Windows), Incus launches a Linux VM. The Incus Client is running on macOS but the Incus Server is inside the Linux VM.
When you launch Incus containers and VMs, those run inside the LinuxVM. When you launch an Incus VM, then this VM runs inside the Linux VM (nested virtualization).
Yeah, the client and server are totally detached and actually installed separately. It is also evident from the installation instructions.
The slight delay in version parity is due to the fact that I assume Iâm pretty much the only user. I am personally always on the bleeding edge and I only push out releases at my convenience.
Going forward, I will try to push out updates shortly after new incus releases.
I work a lot on our Incus terraform provider with my Mac and used Orbstackâs systems machine feature for that.
Today I just gave Colima a shot with Incus and I am very impressed! In particular as it seems you have brought ZFS storage with Colima which I could not get with Orbstack becasue they donât allow me to build a kernel module.
When I run containers on Linux, they usually point to the kernel on the host. In this case, instead of pointing to Darwin the uname command in the container points to Linux Trixie 6.8.0-39-generic #39-Ubuntu SMP PREEMPT_DYNAMIC which obviously is a Linux kernel (apparently with an âUbuntuâ tag from Debian.) Where is that coming from? Is Incus providing this?
When you launch Incus containers and VMs, those run inside the LinuxVM. When you launch an Incus VM, then this VM runs inside the Linux VM (nested virtualization).
To me this seems logical. I perhaps was confused by the discussion in this thread on the patch bringing in ânested virtualizationâ. If Iâm running a Linux VM, perhaps via QEMU since that is installed, then donât we already have nested virtualization?