[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Persistent block device naming by UUID
Hi, xen1:~# uname -a Linux xen1.int.autonlab.org 4.9.65-1-hardened #2-Alpine SMP Mon Nov 27 15:36:10 GMT 2017 x86_64 Linux xen1:~# apk info xen xen-4.11.1-r1 description: Xen hypervisor xen-4.11.1-r1 webpage: https://www.xenproject.org/ xen-4.11.1-r1 installed size: 47734784 xen1:/etc/xen/my-guests/auto# more ubuntu-16.04-observium-ng.cfg type = "hvm" name = "observium-ng" vcpus=8 memory = 32768 vif = [ 'mac=12:16:3e:0d:98:96, bridge=br0', 'mac=12:16:3e:0d:98:97, bridge=br1' ] disk = [ 'phy:/dev/sdc,xvda,rw' ] boot = "dc" on_reboot="restart" on_crash="restart" I am reading documentation back and forth in search of a better persistent naming method. Namely disk = [ 'phy:/dev/sdc,xvda,rw' ] is not persistent between the boots. I like putting my DomUs on a dedicated block devices (M.2 SSDs) and when one of them dies the disk labels are switching on the reboot. Ideally I would like to have something like disk = [ 'phy:UUID="839ca898-db1d-4c89-ad3f-faf6909bf448",xvda,rw' ] instead. That seems to be unsupported https://xenbits.xen.org/docs/4.11-testing/ I do understand that uuid in Xen lingo is used for something else https://www.practicalxenserver.org/tutorials/miscellaneous-tutorials/working-with-uuids/ Am I missing here something? Best, Predrag _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |