Cause. A datastore was to be mounted on a host, or unmounted from one host, that cannot share it. A datastore on an iSCSI LUN (the VMFS-like type) is a file system of one host and cannot be moved between hosts this way. A local datastore is a directory of its own host and can only be mounted there again.
Remedy.
To stop using an iSCSI datastore, remove it: kyvernon host remove-datastore <id> <ds-id>, or from every host: kyvernon datastore remove <ds-id>.
To share storage between hosts, use an NFS datastore and mount it on each host: kyvernon host mount-datastore <id> <ds-id>.
error.datastore.insufficient_space
Text in the console
Datastore {datastore} has room for {available} bytes; {requested} bytes were asked for. Choose a smaller disk or another datastore.
Meaning for API clients
A new or grown disk asks for more bytes than the datastore has free (thick) or than the thin-disk cap.
the bytes that the datastore, or the thin-disk limit, can give.
datastore
the name of the datastore.
Cause. A new or grown disk asks for more bytes than the datastore has free (thick disks), or more than the largest thin disk that is allowed. That limit is max_thin_disk_gib in the [vm_ops] section of the controller configuration, or the capacity of the datastore when the setting is 0.
Remedy.
Choose a smaller disk size, or a datastore with more free space.
Free space on the datastore: delete files that nothing uses. kyvernon datastore orphans <id> lists disk images that no virtual machine, template or snapshot references.
For thin disks, an administrator can raise max_thin_disk_gib. Pass on the message id and the name of the datastore.
error.image_in_use
Text in the console
The image file still backs the virtual machine {vm}. Delete or move that virtual machine first.
the id of the virtual machine whose disk the file is.
Cause. A disk was to be made from an image file that is still the disk of another virtual machine. Copying or linking the file of a virtual machine that is running or suspended, or any linked clone of it, is refused.
Remedy.
Power off the virtual machine that holds the file, or delete that virtual machine when it is no longer needed.
Make the disk from a template, or clone the virtual machine instead of its file.
Repeat the operation.
error.datastore_bad_path
Text in the console
The path is not valid: it must be relative, below the datastore root and not empty. Correct the path.
Meaning for API clients
The datastore path is empty, absolute, or escapes the root.
Cause. The path on the datastore is empty, absolute, contains .. or an internal name, or would leave the root folder of the datastore. The root itself cannot be deleted.
Remedy.
Give a path that is relative to the root of the datastore, for example images/disk1.qcow2.
Do not start the path with / and do not use ...
error.datastore_file_exists
Text in the console
A file or folder with that name already exists. Choose another name, or allow overwriting.
Cause. A file or folder with that name exists already at the destination.
Remedy.
Choose another name, or remove the existing file when it is no longer needed: kyvernon datastore rm <id> <path>.
To replace the file on purpose, repeat the operation with overwriting allowed: kyvernon datastore upload <id> <file> --overwrite, or --overwrite with cp and mv.
error.datastore_file_not_found
Text in the console
The file does not exist on the datastore. It may have been removed. Refresh the list.
Cause. The file is larger than the upload limit of the controller. The limit is max_upload_bytes in the [files] section of the controller configuration. The value 0 means no limit.
Remedy.
Split the file, or put it on the datastore another way, for example by copying it on the host.
An administrator can raise max_upload_bytes and restart the controller. Pass on the message id and the size of the file.
error.datastore_upload_incomplete
Text in the console
The upload ended before the whole file arrived. Upload the file again.
Cause. The operation moves a running virtual machine to another host, which needs a datastore that both hosts mount. Moving a virtual machine together with its disks to a host that does not mount the datastore is not offered.
Remedy.
Choose a datastore that both hosts mount.
Power the virtual machine off and relocate it with a datastore of the destination host: kyvernon vm relocate <id> --host <host> --datastore <datastore>.