the request field that holds the rejected disk size.
disk
the key of the disk.
Cause. The new configuration gives a disk a smaller size than it has. Kyvernon grows disks but does not shrink them, because a smaller disk could cut off data of the guest.
Remedy.
Keep the size of the disk, or set a larger one in the configuration file: kyvernon vm reconfigure <id> --config <file>. In the console, use Edit settings.
To end up with a smaller disk, add a new, smaller disk, copy the data inside the guest, and remove the old disk from the configuration.
error.disk_owned_by_other_vm
Text in the console
The disk file belongs to another virtual machine, and you have no disk access to that virtual machine.
Meaning for API clients
The disk file belongs to another VM the caller has no disk access to.
Cause. The configuration uses a disk file that belongs to another virtual machine, and your role has no disk access to that virtual machine. Attaching the disk of another virtual machine needs the privilege VirtualMachine.Provisioning.DiskRandomAccess on it.
Remedy.
Use a disk file that belongs to this virtual machine, or create a new disk.
To attach the disk of the other virtual machine on purpose, ask an administrator to grant the privilege on that virtual machine. Pass on the message id and the path of the disk.