search for: virtlockd

Hi Eric, Here is my try to write a quick upstart script for virtlockd. It should be named /etc/init/virtlockd.conf, then : ln -s /lib/init/upstart-job /etc/init.d/virtlockd It seems to work for me : # virtlockd - Locking daemon for libvirt description "virtlockd" start on filesystem and runlevel [2345] stop on starting rc RUNLEVEL=[016] pre-start sc...

Hi all, Trying to test libvirt 1.1.3 with virtlockd locking my qcow2 images on a NFS storage between two kvm hosts. ./configure ... --with-init-script=upstart Libvirtd upstart script is actually well generated but I can't see nothing about virtlockd... or am I blind ? :) Nevertheless, running virtlockd -d && service libvirtd restart wor...

Hi, I've read in the documentation that virtlockd uses SIGUSR1 to dump its state and then re-execs itself. Now I tried it and this seems to fail because virtlockd is being launched without a full path (when using the init script), thus re-exec fails with the error: error : virLockDaemonPreExecRestart:1092 : Unable to restart self: No such fil...

...gt; > > So, may I ask: > > - why does libvirtd requests READ locks even commenting the > > "lock_manager" option? > > - does it means that I can avoid modifying anything, relying on > > libvirtd to correctly locks image files? > > - if so, I should use virtlockd for what use cases? > > > > Thanks. > > > > [1] https://libvirt.org/locking-lockd.html > > Ok, maybe I found some answers: from what I read here [1] and here [2], Qemu > started to automatically lock disk image files to prevent corruption from > processes outs...

On Fri, Jan 03, 2020 at 02:56:50PM +0100, Gionatan Danti wrote: > Il 03-01-2020 11:26 Daniel P. Berrangé ha scritto: > > virtlockd also uses fcntl(), however, it doesn't have to acquire locks > > on > > the file/block device directly. It can use a look-aside file for > > locking. > > For example a path under /var/lib/libvirt/lock. This means that locks on > > block devices for /dev/sda1 would...

On 10/11/2013 03:25 AM, NEVEU Stephane wrote: > Hi all, > > Trying to test libvirt 1.1.3 with virtlockd locking my qcow2 images on a NFS storage between two kvm hosts. > ./configure ... --with-init-script=upstart > > Libvirtd upstart script is actually well generated but I can't see nothing about virtlockd... or am I blind ? :) It looks like virtlockd was added after Fedora had already...

Hello. I'm playing with libgfapi network disks, over IB and all is working fine, but not disk locking (and true rdma transport). I use virtlockd, and with fuse mount, locking works as expected. But when i converted disk definitions to libgfapi, locks are not created (but qemu starts and works fine). I used direct and indirect locking - same result : qemu working fine, no locks. my revelant xml section: <disk type='network...

...>> syntax for configuring disks. Copying Peter to confirm/deny this... > > The main issue was that we were leaking locks on the backing chain. > This > should be now fixed with -blockdev as we call the appropriate apis to > lock/unlock the images but I didn't try it with virtlockd. > > Certainly if there's still a problem now we have well defined places > where we know what's happening to images so it should be easy to fix > them. Hi Peter, can I ask what do you mean with "fixed with -blockdev"? Thanks. -- Danti Gionatan Supporto Tecnico As...

Il 03-01-2020 11:26 Daniel P. Berrangé ha scritto: > virtlockd also uses fcntl(), however, it doesn't have to acquire locks > on > the file/block device directly. It can use a look-aside file for > locking. > For example a path under /var/lib/libvirt/lock. This means that locks > on > block devices for /dev/sda1 would be held as > /...

Up. Any ideas ? Thank you De : NEVEU Stephane Envoyé : lundi 14 octobre 2013 10:46 À : libvirt-users@redhat.com Objet : migrate & virtlockd Hi all, I'm testing virtlockd with libvirt 1.1.3 and it seems I can't migrate my VMs from the first to my second kvm node (on a NFS storage). Virtlockd is locking my qcow2 : Error : resource busy Lockspace resource 'ea3jkj78.....' is locked As a result my VM is paused. How can I f...

I have several Qemu/kvm servers running VMs hosted on an NFS share, and am using virtlockd. (lock_manager = "lockd" in qemu.conf) After a power failure, one of the VMs will not start, claiming that it is locked. How do I get out of this? thanks, Steve Gaarder System Administrator, Dept of Mathematics Cornell University, Ithaca, NY, USA gaarder@math.cornell.edu

...ds with the same > error. > > So, may I ask: > - why does libvirtd requests READ locks even commenting the > "lock_manager" option? > - does it means that I can avoid modifying anything, relying on > libvirtd to correctly locks image files? > - if so, I should use virtlockd for what use cases? > > Thanks. > > [1] https://libvirt.org/locking-lockd.html Ok, maybe I found some answers: from what I read here [1] and here [2], Qemu started to automatically lock disk image files to prevent corruption from processes outside libvirt scope (ie: manually issues...

...rror APIs, it'll be ok though. > > > > While I am not an heavy user of external snapshot and other block-related > > operation, I occasionally use them (and, in these cases, I found them very > > useful). > > > > Does it means that I should avoid relying on virtlockd for locking? Should I > > rely on Qemu locks only? > > As above, QEMU's locking is good enough to rely on for file based > images. > > The flaws I mention with libvirt might actually finally be something we > have fixed in 5.10.0 with QEMU 4.2.0, since we can finally u...

...x for configuring disks. Copying Peter to confirm/deny this... > > > > The main issue was that we were leaking locks on the backing chain. This > > should be now fixed with -blockdev as we call the appropriate apis to > > lock/unlock the images but I didn't try it with virtlockd. > > > > Certainly if there's still a problem now we have well defined places > > where we know what's happening to images so it should be easy to fix > > them. > > Hi Peter, can I ask what do you mean with "fixed with -blockdev"? blockdev is the n...

Hi all, I'm testing virtlockd with libvirt 1.1.3 and it seems I can't migrate my VMs from the first to my second kvm node (on a NFS storage). Virtlockd is locking my qcow2 : Error : resource busy Lockspace resource 'ea3jkj78.....' is locked As a result my VM is paused. How can I fix this behavior ? Thank you for you...

...sk to another vms and booting it up ends with the same error. So, may I ask: - why does libvirtd requests READ locks even commenting the "lock_manager" option? - does it means that I can avoid modifying anything, relying on libvirtd to correctly locks image files? - if so, I should use virtlockd for what use cases? Thanks. [1] https://libvirt.org/locking-lockd.html -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti@assyoma.it - info@assyoma.it GPG public key ID: FF5F32A8

Hello! Is it possible to disable the virtlockd daemon or VM file locking? I start qemu with a -snapshot option which prevents and changes to the disk image anyways. Using <readonly /> is not supported for IDE disks. Another option would be to not require locking on the NFS share, but i have no idea how. Can someone help me with that?...

On Mon, Jun 08, 2020 at 16:26:44 +0200, Felix Queißner wrote: > Hello! Hi, > > Is it possible to disable the virtlockd daemon Yes. via the 'lock_manager' option in /etc/libvirt/qemu.conf >or VM file locking? I If you mean the image locking provided by qemu, then no, libvirt doesn't have provisions to disable it. > start qemu with a -snapshot option which prevents and changes to the > disk i...

Hi, I'm trying to put in place a KVM cluster (using clvm and gfs2), but I'm running into some issues with either sanlock or virtlockd. All virtual machines are handled via the cluster (in /etc/cluser/cluster.conf) but I want some kind of locking to be in place as extra security measurement. Sanlock ======= At first I tried sanlock, but it seems if one node goes down unexpectedly, sanlock sometimes blocks everything on the oth...

Dear All, I am trying to use VM (disk) locking on a two node Centos 7 KVM cluster. Unfortunately, I am not successful. Using virtlockd (https://libvirt.org/locking-lockd.html), I get each host to write the zero length file with a hashed filename to the shared folder specified. Regardless of which 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...