search for: __libvirt__disks__

...em with the lease of these resources on the server that host these guests? 2. Is there a way to reregister these resources, because they are still in use (but not for sanlock it seems)? 3. Overall, is it a bad idea to run virt-sanlock-cleanup? Some entries from the log file: 538 s1:r35 resource __LIBVIRT__DISKS__:e133401bfdff6979f76d9544ec8a5529:/var/lib/libvirt/sanlock/e133401bfdff6979f76d9544ec8a5529:0 for 1,9,4218 539 open error -1 /var/lib/libvirt/sanlock/e133401bfdff6979f76d9544ec8a5529 539 r35 release open_disk error /var/lib/libvirt/sanlock/e133401bfdff6979f76d9544ec8a5529 598 s1:r40 resource __LIBVI...

...<alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> Start VM: # virsh start iscsi Domain iscsi started Check resource file: # ls /var/lib/libvirt/sanlock __LIBVIRT__DISKS__ No resource file generated. So, does libvirt sanlock only support file or block type storage? -- Han Han Quality Engineer Redhat. Email: hhan@redhat.com Phone: +861065339333

...e VM in the sanlock >> list. I tried kill commands, rm ... but without a real success. >> >> I tried many command with sanlock perhaps I misunderstood some >> commands but I never succeed in removing lock on the VMs. >> >> sanlock client rem_lockspace -r >> __LIBVIRT__DISKS__:b90b9c61e2d6413077205907ffb3281a:/var/lib/libvirt/images/POOL_ADMIN/sanlock/b90b9c61e2d6413077205907ffb3281a:0:4 >> -p 9383 >> >> So I'm trying to use lock_manager to replace the sanlock but >> lock_manager doesn't have tools to retrieve the lock / VM name in >&gt...

...ch host I start a VM (domain) on, they do produce the identical filename per VM. What does not work, however, is to prevent the second host to start the VM already running on the first VM. Using sanlock (https://libvirt.org/locking-sanlock.html), no domains do start at all. However, the file "__LIBVIRT__DISKS__" is also not written to the shared folder. Hence, nothing works. Can someone please point me to the right direction? My system is current Centos 7 using a gluster storage setup like suggested for oVirt (https://community.redhat.com/blog/2014/10/up-and-running-with-ovirt-3-5/) based on the o...