similar to: [libvirt] a question about sanlock

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

Hello, I am managing several virtual machines (a predefined set) with virsh, and I would like to make sure that all VMs are booted when the host reboots. What is the recommended approach for this? Thanks, Daniel Gonzalez -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 02/14/2012 11:01 AM, Jun Koi wrote: > On Tue, Feb 14, 2012 at 11:47 PM, Alex Jia <ajia at redhat.com> wrote: >> Hi Jun, >> I assume you haven't changed libvirt default URI, it may be a issue, >> I want to know whether it works for you if you explicitly specify >> --connect qemu:///system with virt-install? I think a root reason >> probably is your disk

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 All, Am new to this list, and have asked in #ovirt / ovirt-users list and they pointed me to here ... I've seen libvirtd using ~11 GB of resident memory after the host has been running for about 60+ days with about 40 VMs running on it. The versions I'm currently running are : libvirt.x86_64 0.9.10-21.el6_3.7 libvirt-client.x86_64 0.9.10-21.el6_3.7

Hello Community, I am installing a domU image via virt-install. However, it seems that a driver needs to be installed for the connection as I saw an error while running the command. Can anyone give any hints about this error? Here is the running script: # virt-install --connect=xen:/// -p -d Thu, 15 Mar 2012 10:17:55 DEBUG Launched with command line: /usr/bin/virt-install --connect=xen:///

Hello Community, I am installing a domU image via virt-install. However, it seems that a driver needs to be installed for the connection as I saw an error while running the command. Can anyone give any hints about this error? Here is the running script: # virt-install --connect=xen:/// -p -d Thu, 15 Mar 2012 10:17:55 DEBUG Launched with command line: /usr/bin/virt-install --connect=xen:///

Dear List , We are using intel 82599EB based SRIOV capable 10GbE cards on the host machine.The VFs are being assigned to the guest in pass through mode and are providing the network connectivity as expected. However when we shutdown the guest the connectivity does not comes back via the VFs on the guest in next boot unless the VFs are detached from the *guest* *before* initiating a shutdown of

I had a host that was exporting a resource to another host to trigger backups. The first host has now gone away, but the second host is still seeing the exported resource (because it still exists in the puppetmaster''s database). I fixed the problem by going in to the database and deleting all the rows I could find that related to the absent host, but I''m wondering if

Hi, I have RHEL5 libvirt client compiled at ${BSPACE}/usrcisco This client when connecting to a libvirtd/server fails to connect as follows -bash-3.2$ ${BSPACE}/usrcisco/bin/virsh -c qemu+ssh://sarvi at cnh-nehalem-1/system?socket=/var//run/libvirt/libvirt-sock error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 I have the libvirt

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

Hi Alex, when I got this error, it was a vnc listener problem. Is there other actives vms on this server? try to change the port number to see if the problem was solved. <graphics type='vnc' listen='0.0.0.0' port='5909'/> Good Luck. Josir Gomes Date: Thu, 15 Mar 2012 18:07:07 +0800 > From: Alex Jia <ajia at redhat.com> > To: ??? <zhanggp at

Hello, A compilation failure happened when I tried building libvirt latest code on rhel8 Version: gcc-8.3.1-4.5.el8.x86_64 libvirt v5.9.0-352-g5e939cea89 Steps: 1. Clone libvirt source code 2. Create build dir, and run autogen.sh # cd libvirt # mkdir build && cd build # ../autogen.sh --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix=

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

Hi All, I am trying to compile libvirt tools from source on RHEL 4. I could get the sources compiled, but when I try to connect to libvirtd using QEMU+SSH I get the following error: error: failed to connect to the hypervisor error: authentication failed: unsupported authentication type 2 With root as the user, I could login, rest other users get the error. All authentication related settings

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

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 all Centos 7.0.1406, 3.10.0-123.el7.x86_64 Configure libvirt-1.2.7 as: ./configure --prefix=/usr --with-xen=no --with-qemu=no --with-openvz=no --with-vmware=no --with-esx=no --with-parallels=no --with-bhyve=no --with-uml=no --with-vbox=no --with-selinux=no make ... make[3]: Entering directory `/usr/local/src/libvirt-1.2.7/daemon' CC libvirtd-remote.o CCLD libvirtd