-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
No
-
None
-
rhel-virt-core-libvirt-1
-
ssg_virtualization
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
The KVM disks are not guaranteed stable naming across reboots, so it is recommended to use /dev/disk/by-
{path|id|uuid|label} for the storage pool.After creating the storage pool, when creating a volume based on the pool it requires a friendly naming convention like sda1.
To reproduce the issue:
1) Create a storage pool type 'disk'
2) Create a volume `virsh vol-create-as <pool_name> <volume_name> <size>`
3) Reboot the KVM host until the friendly name is no longer the same as /dev/disk/by-{path|id|uuid|label}
4) The volume path dose not change to line up with the storage pool
It looks like libvirt is using parted to get the names: `parted /dev/sda p`