similar to: migrate & virtlockd

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

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 works fine. Am I wrong thinking that editing

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 script test -x

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

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

Dear colleagues, I am facing a problem that has been troubling me for last week and a half. Please if you are able to help or offer some guidance. I have a non-prod POC environment with 2 CentOS7 fully updated hypervisors and an NFS filer that serves as a VM image storage. The overall environment works exceptionally well. However, starting a few weeks ago I have been trying to implement virtlock

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

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? Regards Felix Queißner

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 file or directory Changing in the init script

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,

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 >

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 >

Eric, Well, in case where several servers may start the same virtual machines after a reboot for exemple. http://lists.ceph.com/pipermail/ceph-users-ceph.com/2013-August/003887.html I've seen this hook here : http://www.wogri.at/en/linux/ceph-libvirt-locking/ But it's a hook... Yes, I may try to write a patch. My coding skills are surely not as good as yours but I 'd be glad to make

Il 28-12-2019 01:39 Gionatan Danti ha scritto: > Hi list, > I would like to ask a clarification about how locking works. My test > system is CentOS 7.7 with libvirt-4.5.0-23.el7_7.1.x86_64 > > Is was understanding that, by default, libvirt does not use any locks. > From here [1]: "The out of the box configuration, however, currently > uses the nop lock manager

On Fri, Jan 03, 2020 at 14:08:03 +0000, Daniel Berrange wrote: > On Fri, Jan 03, 2020 at 02:56:50PM +0100, Gionatan Danti wrote: > > Il 03-01-2020 11:26 Daniel P. Berrangé ha scritto: [...] > > > There are some issues with libvirt's locking though where we haven't > > > always released/re-acquired locks at the correct time when dealing > > > with block

On Mon, Jan 06, 2020 at 18:44:31 +0100, Gionatan Danti wrote: > Il 06-01-2020 10:06 Peter Krempa ha scritto: > > On Fri, Jan 03, 2020 at 14:08:03 +0000, Daniel Berrange wrote: > > > As above, QEMU's locking is good enough to rely on for file based > > > images. > > Hi Daniel, thank you for the direct confirmation. > > > > The flaws I mention with

On Sat, Dec 28, 2019 at 02:36:27PM +0100, Gionatan Danti wrote: > Il 28-12-2019 01:39 Gionatan Danti ha scritto: > > Hi list, > > I would like to ask a clarification about how locking works. My test > > system is CentOS 7.7 with libvirt-4.5.0-23.el7_7.1.x86_64 > > > > Is was understanding that, by default, libvirt does not use any locks. > > From here [1]:

On Mon, Aug 31, 2015 at 08:01:58PM +0000, Prof. Dr. Michael Schefczyk wrote: > 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.

On Thu, Nov 07, 2013 at 09:08:58AM -0700, Eric Blake wrote: > On 11/07/2013 09:04 AM, NEVEU Stephane wrote: > > Eric, > > [please don't top-post on technical lists] > > > > > Well, in case where several servers may start the same virtual machines after a reboot for exemple. > > http://lists.ceph.com/pipermail/ceph-users-ceph.com/2013-August/003887.html

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