similar to: virtlockd, init script and kill signals

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,

I'm trying to set up SAN-based shared storage in KVM, key word being "shared" across multiple KVM servers for a) live migration and b) clustering purposes. But it's surprisingly sparsely documented. For starters, what type of pool should I be using?

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

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

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 >

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]:

Whilst bored I purchased HalfLife for Windows, having read people mention on Slashdot that it runs on Wine. I run Debian (woody) on an AMD Athlon 1.4GHz machine with 1Gb RAM as my desktop. It currently has a Voodoo3 video card, though I have a dual head Radeon which I'm going to use once I get a monitor that is compatible (my current monitor has a very wavy display with that card). I

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,

[moderator note: .pngs were stripped to avoid overwhelming the mail server and list recipients with 1M of data] -------- Forwarded Message -------- Date: Wed, 30 Mar 2016 11:25:09 +0200 Message-ID: <20160330112509.Horde.0Oad-ZfkzdZnouXf-VkEmw1@webmailperso.univ-brest.fr> From: villeneu@kassis.univ-brest.fr To: Franky Van Liedekerke <liedekef@telenet.be> Cc: libvirt-users@redhat.com

[Dropping libvir list and adding libvir-users list.] On Mon, Jan 19, 2015 at 04:12:46PM +0100, liedekef@telenet.be wrote: > Hi all, > > I had libvirt 1.2.10 running without issues together with the qemu package > qemu-kvm-0.12.1.2-2.415.el6_5.14.x86_64.rpm That's a really old QEMU and the libvirt you're using is relatively newer. > Now, after updating my server,

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 plugin". As "lock_manager" is commented in my qemu.conf file, I was

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

Hello, I am having a little problem with executing logon scripts on Win95 clients, logging into Samba Netlogon service. When a user logges in, a MS-DOS prompt shows up and quicky disappears. Then I get "Please Wait While your logon script executes". It hangs at that point. A user has to hit cancel to start his win95 session. I have done the logon script in MS-DOS editor. I have the

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

>Date: Mon, 4 Aug 1997 10:05:04 +0200 >From: marc.waknine@espace.aerospatiale.fr >To: samba@arvidsjaur.anu.edu.au (Non Receipt Notification Requested) >Subject: printer problem . URGENT help form SAMBA team !! >Message-ID: <9708040805.AA06185@musun95009.espace.aerospatiale.fr> > >on the SAMBA server i declare some printers >everything is ok in win3.11 because all

More information on the problem. A couple of days ago I posted a request for help for this error msg terre{testgb}73: smbpasswd Old SMB password: New SMB password: Retype new SMB password: /opt/samba/bin/smbpasswd: machine 127.0.0.1 rejected the session setup. Error was : ERRSRV - ERRbadpw (Bad password - name/password pair in a Tree Connect or Session Setup are invalid.). This happens only

Hi all, I'm trying to install PM65 and the install goes just fine, but when trying to start PM, I get: err:winspool:WINSPOOL_OpenDriverReg win32 style printing used with 16 bits app, try specifying 'win95' Windows version err:winspool:AddPrinterDriverA Can't create Drivers key err:winspool:WINSPOOL_LoadSystemPrinters Failed adding PS Driver (6) fixme:dialog:MSGBOX_OnInit system

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

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