similar to: XML-RPC

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

Background: ---------- I'm trying to debug a two-node pacemaker/corosync cluster where I want to be able to do live migration of KVM/qemu VMs. Storage is backed via dual-primary DRBD (yes, fencing is in place). When moving the VM between nodes via 'pcs resource move RES NODENAME', the live migration fails although pacemaker will shut down the VM and restart it on the other node.

I'm setting up for libvirt remote access on a xend host. On the host, xl info | egrep "release|xen_version" release : 5.6.10-24.gde48f93-default xen_version : 4.13.0_12-lp151.700 systemctl --version systemd 234 I've installed rpm -qa libvirt-daemon-xen libvirt-daemon-xen-6.2.0-lp151.890.1.x86_64 libvirtd --version libvirtd (libvirt)

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, Sep 25, 2020 at 4:54 PM Daniel P. Berrangé <berrange@redhat.com> wrote: > > > Yes, I tried, but it fails with > > ../src/util/virfile.c:42:11: fatal error: libutil.h: No such file or > > directory > > You'd have to delete the build dir and re-run meson so that it > auto-detects again. > > OK, that issue seems gone, but ninja reports lots of

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

Hi, I'm using qemu+ssh://username at hostname/system as the remote URI. Libvirt seems to be communicating fine until some 2 minutes (we poll every 5 seconds) and then it throws up RPC error and many counters are wrong. But if I collect on localhost the counters seems to be coming fine. Test and testvm are guests on the local machine where as Win8 and Ubuntu* are remote URI's connected

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

Hello. I'm try to understand, why in case of 20 workers libvirt fully locked when runs qemu hook (when domain starts) virsh list freezes. As i understand in case of using more workers it utilized to run hooks too, but as i see in pstree only main libvirt process executes hook. Why this happening? pstree -a -p 6642 libvirtd,6642 -d -l ├─qemu,9272 /etc/libvirt/hooks/qemu testvm prepare begin -

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

Hi, my system got updated to libvirt 6.0.0 (from 5.6.0) this morning, and now I'm having problems starting VMs that make use of openvswitch portgroups. When I start a VM, I get this error message on virsh: > virsh # start testvm > error: Failed to start domain testvm > error: An error occurred, but the cause is unknown The system log contains: > Mar 30 09:45:39 tplinux

On Wed, Aug 09, 2017 at 11:53:54AM +0800, netsurfed wrote: > Hi all, > I think it's a bug, when call virDomainGetState after "service libvirtd stop" > , I receive signal SIGPIPE. For the QEMU driver, the libvirt library just talks to libvirtd over an RPC layer. You killed libvirtd, so the libvirt library gets SIGPIPE. > I want to know how to avoid this problem? And

The error message could however give a hint what is going on. It should sax that it is impossible to talk to libvirtd and that it might be stopped. On 9 Aug 2017 2:19 p.m., "Daniel P. Berrange" <berrange@redhat.com> wrote: > On Wed, Aug 09, 2017 at 11:53:54AM +0800, netsurfed wrote: > > Hi all, > > I think it's a bug, when call virDomainGetState after

On Wed, 12 Feb 2014 21:51:53 +0100 urgrue <urgrue@bulbous.org> wrote: > 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? It's indeed not documented

On 30. 3. 2020 11:10, Thomas Pircher wrote: > Hi, > > my system got updated to libvirt 6.0.0 (from 5.6.0) this morning, and > now I'm having problems starting VMs that make use of openvswitch > portgroups. I don't see any changes between 5.6.0 and now done to openvswitch in libvirt (apart from harmless code reworks towards glib). > > When I start a VM, I get this

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

2017-08-10 8:21 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: > On 08/09/2017 03:59 PM, Dominik Psenner wrote: > > The error message could however give a hint what is going on. It should > sax > > that it is impossible to talk to libvirtd and that it might be stopped. > > [Please don't top post on technical lists] > Yes and no. There can be a lot of

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

Hallo, I have one ups with snmp and any ups without snmp. Shutdown works while network online. But some batteries are empty, so that the communication break early. Howto force shutdown if nut-snmp Communications lost? My 1. suggestion was option DEADTIME, but seem to be information only. (s. below) Any suggestions? The last way would be a ugly cronjob (like: ping || shutdown). regards Heiko