similar to: need help with sanlock plugin

Hello, As we know, libvirt sanlock support file type storage. I wonder *if it supports network storage.* I tried *iSCSI*, but found it didn't generate any resource file: Version: *qemu-2.10 libvirt-3.9 sanlock-3.5* 1. Set configuration: qemu.conf: *lock_manager = "sanlock"* qemu-sanlock.conf: *auto_disk_leases = 1disk_lease_dir = "/var/lib/libvirt/sanlock"host_id =

Hello, I configured libvirtd with the sanlock lock manager plugin: # rpm -qa | egrep "libvirt-0|sanlock-[01]" libvirt-lock-sanlock-0.9.4-23.el6_2.4.x86_64 sanlock-1.8-2.el6.x86_64 libvirt-0.9.4-23.el6_2.4.x86_64 # egrep -v "^#|^$" /etc/libvirt/qemu-sanlock.conf auto_disk_leases = 1 disk_lease_dir = "/var/lib/libvirt/sanlock" host_id = 4 # mount | grep sanlock

Hello, I'm using libvirt and sanlock on qemu-kvm guests. Each guest has it's own Logical Volume for it's root filesystem. Sanlock is configured and working and prevents me from starting the same VM twice on multiple nodes and corrupting it's root filesystem. Each VM's domain XML resides on 2 servers that share the LVM volume group over fiber channel. In testing, I noticed

CentOS Errata and Bugfix Advisory 2016:0541 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0541.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 96a4bc7ef0285522786a39d02c0b427656aaa71e1abb779a75c65c2e1c600748 fence-sanlock-3.2.4-2.el7_2.x86_64.rpm

Hi Daniel, I got a question about lock manager, if I enable 'sanlock' in qemu.conf and uncomment 'auto_disk_leases = 1' in qemu-sanlock.conf then restart libvirtd service, libvirtd will be dead, I know I should also uncomment 'host_id = 1' in qemu-sanlock.conf, because I enable 'auto_disk_leases'. The question is the libvirtd must die due to a error users

Hi all, I have a 2 node cluster that consists of the following: * 1 drbd/gfs2 partition that holds VM images and XML * Sanlock configured with the disk lease directory on the same drbd/gfs partition Everything is working well, aside from one small issue I ran into. When testing fencing, on one particular test GFS began replaying the journal for the remaining node, and in the middle of it

Hello list, In short: I am experiencing a problem where trying to start a VM which is allready running on a different libvirt host. Starting it fails, thanks to sanlock, but the disk dies on the original hypervisor and the vms filesystem is rendered read-only. Long version: i have the following setup: Two machines (H1 and H2) using CentOS 6.2 with the packages:

On Wed, Nov 08, 2017 at 02:42:35PM +0800, Han Han wrote: > Hello, > As we know, libvirt sanlock support file type storage. I wonder *if it > supports network storage.* > I tried *iSCSI*, but found it didn't generate any resource file: Correct, the code currently ignores locking for any non-local disk. Regards, Daniel -- |: https://berrange.com -o-

FWIW the tcpdump will be a few days at http://rosa.stappers.nl/ff/tcp_w.pcap md5sum a8090ca85202d62ddd5a3d5684b2e8fd tcp_w.pcap ----- Forwarded message from syslinux-owner at zytor.com ----- Date: Thu, 06 Jun 2013 12:49:11 -0700 From: syslinux-owner at zytor.com To: syslinux-owner at zytor.com Subject: Syslinux post from upendra.gandhi at gmail.com requires approval Message-ID:

I On Wed, Jun 5, 2013 at 7:41 PM, upen <upendra.gandhi at gmail.com> wrote: > > > > On Wed, Jun 5, 2013 at 7:34 PM, upen <upendra.gandhi at gmail.com> wrote: > >> >> >> >> On Wed, Jun 5, 2013 at 7:25 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >>> On Wed, Jun 5, 2013 at 7:49 PM, upen <upendra.gandhi at gmail.com>

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

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

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,

On Wed, Jun 5, 2013 at 7:34 PM, upen <upendra.gandhi at gmail.com> wrote: > > > > On Wed, Jun 5, 2013 at 7:25 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > >> On Wed, Jun 5, 2013 at 7:49 PM, upen <upendra.gandhi at gmail.com> wrote: >> > On Wed, Jun 5, 2013 at 5:39 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Jun 5,

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 >

Hello, I wonder what the "open error -1" / "release open_disk error" messages in sanlock.log actually mean. I saw these messages in the log on a KVM host that rebooted, and after running "/usr/sbin/virt-sanlock-cleanup" on that host. The resources where disks from 2 guests running on another KVM host. So in fact the disks are still in use, bot got cleaned up by

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

Please note clarifications in <<>> below. My apologies for any confusion. Thanks again, Scott ---------- Forwarded message ---------- From: Scott Stark <stark.sc@gmail.com> Date: Aug 23, 2007 1:03 PM Subject: Expedite scalar f(x) evaluation over vectors To: r-help@lists.r-project.org Dear R community, I am trying to code a fairly complex equation for optim(). My current