Stux
July 31, 2025, 10:05pm
293
Hypothetically, not having done it yet,
Clone and Promote the zvol out to somewhere else, re-enable the cache settings and set the volmode to default, then recreate the vm “classically” and point at the zvol.
You should then be able to delete the old incus vm in the UI.
For reference, its similar to this, but in reverse:
In Fangtooth 25.04 RC.1 you can create Incus VM Instances using external zvol.
This is a good way to migrate an existing VM into the Incus system, but you will be left with a dangling “root” 10GiB volume attached to your VM.
There is no harm in this, and it uses a trivial amount of space, but perhaps it annoys you and your would prefer to replace the root disk with the external zvol, and fully migrate your VM into the Incus ecosystem.
WARNING: Incus 6.0.3 LTS is prone to erasing existing zvol…
And I document the exact properties here:
Yes,
The link is:
In essence though, you’d be wanting to do the exact opposite, which is fine, it means you can replicate, clone or move out.
And you want to then update the volmode and primary/secondary caches.
volmode gets changed to default, primarycache and secondarycache get changed to all
Its the volmode which will “activate” the zvol again after it gets moved/copied out of incus
3 Likes