similar to: Re: migrate & virtlockd

Displaying 20 results from an estimated 4000 matches similar to: "Re: migrate & virtlockd"

2013 Oct 21
1
Re: upstart script 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 script test -x
2013 Oct 14
0
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 fix this behavior ? Thank you for your help.
2014 Dec 08
0
libgfapi disk locking in virtlockd not working
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
2013 Oct 11
0
Re: upstart script for virtlockd
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
2013 Oct 11
2
upstart script for virtlockd
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
2013 Nov 07
4
Re: RBD images locking
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
2013 Nov 08
1
Re: RBD images locking
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
2014 Oct 13
0
Re: Virt-v2v conversion issue
Richard, After un moment I have to force the unmount volume on /tmp umount -f /tmp/v2v.Nj0eik and I have this message : qemu-img: error while writing sector 246526903: Input/output error virt-v2v: error: qemu-img command failed, see earlier errors Alain Alain VONDRA Chargé d'exploitation des Systèmes d'Information Direction Administrative et Financière +33 1 44 39 77 76 UNICEF
2013 May 06
1
virtlockd, init script and kill signals
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
2013 Nov 07
0
Re: RBD images locking
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 Isn't the existing virtlockd support already sufficient for this? If not, what is preventing the
2020 Jan 03
0
Re: Locking without virtlockd (nor sanlock)?
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 >
2020 Jan 03
2
Re: Locking without virtlockd (nor sanlock)?
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 >
2019 Dec 28
0
Re: Locking without virtlockd (nor sanlock)?
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
2020 Jan 06
0
Re: Locking without virtlockd (nor sanlock)?
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
2020 Jan 07
0
Re: Locking without virtlockd (nor sanlock)?
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
2020 Jan 03
2
Re: Locking without virtlockd (nor sanlock)?
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]:
2018 Jul 03
1
Breaking a virtlockd lock?
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
2020 Jan 06
2
Re: Locking without virtlockd (nor sanlock)?
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 libvirt might actually finally be something >> we >> have fixed in 5.10.0 with QEMU 4.2.0,
2020 Jun 09
0
Re: Disable virtlockd
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
2020 Jun 08
2
Disable virtlockd
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