Happy to provide more detail but is a root volume treated specially from other custom volumes in an Incus 6.20 VM?
I’m failing to do these operations:
- Swap one
rootvolume device for another (I’m currently achieving this via adding custom volumes and changing their boot priority to superscede the root volume) - Shadow a
rootvolume using a custom volume, to mount at/of a VM (attempting to hide the root volume device) - Clone the
rootvolume (VMSrcRoot) of VMVMSrcthat’s currently stopped, attempting to attach it to a different VMVMClonerthat also has another custom volumeVMSrcRootCloneattached to it, that mountsVMSrcRootas read only and runs addfromVMSrcRoottoVMSrcRootClone(incus simply refuses to attachVMSrcRoottoVMClonersayingVMSrcRootdoesn’t exist althoughincus storage volumeshows it does) - Obtain the
locationof the root volume (actually this seems to be the case for any volume Is it expected for Incus to not show the `location` of volumes?)
Again, if these are all expected to work out of box in Incus 6.20 and not error out, I’m likely making mistakes, let me know and I will follow up with the exact commands I’m using - just wanted to see if my expectations are correct
Now I’m using a OpenWRT VM to achieve all of this so if this detail matters or is relevant, let me know as well, but so far it feels like the protections are from directly from Incus