[ovirt-users] disk order in vm and disk order in export
Fabrice Bacchella
fabrice.bacchella at icloud.com
Mon May 16 09:34:42 UTC 2016
I have a VM with the following disks (in the ordrer return by a get query):
<Disk href="/api/vms/2ddfb8c3-d258-4d3e-9f65-fc247d0a03f6/disks/1180405d-699e-4594-bf73-8b1b170f38a9" id="1180405d-699e-4594-bf73-8b1b170f38a9">
...
<name>vm_sys</name>
<actual_size>17179869184</actual_size> <- 16GiB
<interface>virtio_scsi</interface>
<bootable>true</bootable>
<storage_type>image</storage_type>
</Disk>
<Disk href="/api/vms/2ddfb8c3-d258-4d3e-9f65-fc247d0a03f6/disks/1fe74758-c521-40ed-b8e5-d02d80188088" id="1fe74758-c521-40ed-b8e5-d02d80188088">
<name>vm_data</name>
<interface>virtio_scsi</interface>
<bootable>false</bootable>
<lun_storage id="3600c0ff00026285a2091355701000000">
<logical_unit id="3600c0ff00026285a2091355701000000">
<size>1099511627776</size> <- 1 TiB.
<paths>0</paths>
</logical_unit>
</lun_storage>
<storage_type>lun</storage_type>
</Disk>
So the first one is a 16 GiB virtual disk, the second one a 1 iTB direct access LUN that will contains data.
But once booterd, I see:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1T 0 disk
...
sdb 8:16 0 16G 0 disk
...
and :
ls -l /dev/disk/by-*/*
...
lrwxrwxrwx. 1 root root 9 May 16 09:03 /dev/disk/by-path/pci-0000:00:04.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx. 1 root root 9 May 16 09:03 /dev/disk/by-path/pci-0000:00:04.0-scsi-0:0:0:1 -> ../../sdb
So the first disk sda is the second non bootable disk.
What set the disk order associated to a VM ? Is there a way to enforce that the first disk is really the first disk ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160516/f089fe5c/attachment-0001.html>
More information about the Users
mailing list