similar to: CEBA-2016:0541 CentOS 7 sanlock BugFix Update

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

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

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

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

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

Hi I am working with libvirt on ubuntu. I would like have sanlock feature with ubuntu. Can you please guide me on how to. -- Thanks and Regards, Upendra.M *As a leading developer of IT infrastructure software solutions, Hexagrid developed the first cloud computing<http://www.hexagrid.com/d/vxdatacenter.html>platform that directly aligns with the real-world IT delivery models of both

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-

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

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:

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

CentOS Errata and Security Advisory 2006:0541 https://rhn.redhat.com/errata/RHSA-2006-0541.html The following updated files have been uploaded and are currently syncing to the mirrors: files: updates/ia64/RPMS/dia-0.94-5.7.1.ia64.rpm -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored -------------- next part -------------- A non-text attachment was

CentOS Errata and Security Advisory 2006:0541 https://rhn.redhat.com/errata/RHSA-2006-0541.html The following updated files have been uploaded and are currently syncing to the mirrors: files: updates/alpha/RPMS/dia-0.94-5.7.1.alpha.rpm -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored -------------- next part -------------- A non-text attachment was

CentOS Errata and Security Advisory 2006:0541 https://rhn.redhat.com/errata/RHSA-2006-0541.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/dia-0.94-5.7.1.s390.rpm s390x: updates/s390x/RPMS/dia-0.94-5.7.1.s390x.rpm -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored -------------- next