Open OpenNebulaProject opened 6 years ago
Original Redmine Comment Author Name: Javi Fontan (Javi Fontan) Original Date: 2017-03-16T11:34:51Z
The target given to libvirt is a hint to the OS but it's not forced to use that specific naming. That problem is caused because the systems fills the holes left in the storage bus identifiers.
There is not a simple and fast way to extract UUID from @qcow2@ images so this can not be generalized for both of the most used formats. Moreover the latest versions don't let you format the disk so this UUID or even label could not be assigned.
We will look into other ways of distinguishing the disk devices that could work for all the most common storage options.
Author Name: Jimmy Goffaux (Jimmy Goffaux) Original Redmine Issue: 3871, https://dev.opennebula.org/issues/3871 Original Date: 2015-07-09
Hello,
Is it possible to force the UUID when creating a disk and trace information in the UUID Sunstone? An example or disks are reversed :(
Basic :
Add first disk by Sunstone : Attach Disk => Volatile Disk => Type : FS, Format : ext4, Target :vdb
Add on 2nd disk on Sunstone : Attach Disk => Volatile Disk => Type : FS, Format : ext4, Target :vdc, Size 15G
On XML virsh :
Now Detach disk vdb on Sunstone
XML virsh :
Now add new disk VDE : Attach Disk => Volatile Disk => Type : FS, Format : ext4, Target :vde, Size 12G
View in Sunstone :
XML Virsh :
Now we have problems relationship:
I decided to shut down the VM (POWEROFF) and start the VM .. The result is worse !!!
vdb => vdc vdc => vdb vde ?
Imagine the size of the disks in Sunstone is the same one does not even know which drive is to be deleted: /
I hope you understand what I mean;)
Thank you !! ;)