forums

Start a new topic

Volume device name shown in mapping with not necessarily match device name inside VM instance

Due to limitations with the KVM hypervisor used in the Nectar Research Cloud, the device name shown in the volume mapping table will not necessarily be the device name that is assigned to the block device within your VM instance.


It is recommended that you use either filesystem labels, or filesystem UUIDs when mounting your volume device and adding to the /etc/fstab file.


Feel free to create a helpdesk ticket if you're unsure.

Login to post a comment