similar to: live migration - qemu hook

On Fri, Apr 03, 2015 at 10:13:38AM +0200, Kashyap Chamarthy wrote: > On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote: > > Migration without --p2p works just fine, ie. the below works: > > > > > > $ virsh migrate --verbose --copy-storage-all \ > > --live cvm1 qemu+ssh://kashyapc@devstack3/system > > Migration: [100 %] >

Hi all, I was trying to take live snapshot of VMs, but I got the following error: [root@localhost ~]# virsh snapshot-create-as 1 test desc --live --memspec file=mem.bak,snapshot=external --diskspec vda,snapshot=external,file=/root/root.bak.qcow2 error: Operation not supported: live disk snapshot not supported with this QEMU binary I upgraded my qemu-kvm 0.12.1 to qemu 1.2, the error still

Under libvirt 1.1.1 snapshot support is incomplete. Source: http://wiki.libvirt.org/page/I_created_an_external_snapshot,_but_libvirt_won't_let_me_delete_or_revert_to_it In regard to snapshotting (features and stability), I have selected these versions of libvirt and qemu: Libvirt >= 1.2.9 (currently 1.2.12) Qemu = 2.1.0 On Qemu 2.3 and 2.4, I have experienced a regression bug regarding

Hello! After some mistakes yesterday we ( me and my colleague ) think that it will be wise for libvirt to check config file existence on remote side and through error if not, before migrating, otherwise migration will fail and VM fs can be damaged, because it is sort of remove of power plug... We missed twice yesterday :-( Could  you tell me is there already such option or any plans to

Hi, I'm using libvirt 0.8.3. It looks like to me that when a QEMU domain is restored from save, the hook is called with the "stopped end -" arguments. I've also noticed that the domain description passed to the hook script doesn't contain the network device the host will be attached to (XPath: /domain/devices/interface/target/@dev). Are these a bugs or a features?

Hi all, If some people use generic ethernet interface and want to set traffic shaping, I made a libvirt hook for qemu: https://github.com/rhardouin/libvirt_hooks Of course, this is a workaround. I recently started to work on a fix but in the meantime this hook will do the trick and maybe it could help someone else. Feel free to fork it if you think about any improvements. Cheers, Romain IRC:

On Thu, Jan 03, 2019 at 18:07:58 +0100, daggs wrote: > Greetings, > > I'm executing an external script when the qemu hook is called with start or release, the script is rather simple, upon start it iterates over the output of lsusb -t and for each device, it looks if it should be added to the vm we started, if so, it attaches it to the vm as follows: > virsh --connect

On 1/4/19 11:27 AM, daggs wrote: > Greetings Peter, > >> Sent: Friday, January 04, 2019 at 4:47 PM >> From: "Peter Krempa" <pkrempa@redhat.com> >> To: daggs <daggs@gmx.com> >> Cc: libvirt-users@redhat.com >> Subject: Re: [libvirt-users] script called from qemu hook freezes. >> >> On Thu, Jan 03, 2019 at 18:07:58 +0100, daggs

On 1/21/20 9:10 AM, Guy Godfroy wrote: > Hello, this is my first time posting on this mailing list. > > I wanted to suggest a addition to the qemu hook. I will explain it > through my own use case. > > I use a shared LVM storage as a volume pool between my nodes. I use > lvmlockd in sanlock mode to protect both LVM metadata corruption and > concurrent volume mounting.

On 1/22/20 9:23 AM, Guy Godfroy wrote: > I could launch `lvchange -asy` on the source host manually, but the aim > of hooks is to automatically execute such commands and avoid human errors. Agreed. However, you would need two hooks actually. One that is called on the source when the migration is started, and the other that is called on the destination when the migration is finished (so

So, how likely is it possible to get this feature (two new events for the qemu hook)? Le 22/01/2020 à 10:56, Guy Godfroy a écrit : > That's right, I need also that second hook event. > > For your information, for now I manage locks manually or via Ansible. > To make hook manage locks, I still need to find out a secure way to > run LVM commands from a non-root account, but

On 1/23/20 1:43 PM, Guy Godfroy wrote: > So, how likely is it possible to get this feature (two new events for > the qemu hook)? I've started writing it, but then I realized we might need third hook - in confirm phase - which would be run on the source when quemu switches control over to the destination, or when migration failed. And this is what I need to figure out, how to

I don't really understand what new hook this would be. Le 24/01/2020 à 14:05, Michal Privoznik a écrit : > On 1/23/20 1:43 PM, Guy Godfroy wrote: >> So, how likely is it possible to get this feature (two new events for >> the qemu hook)? > > I've started writing it, but then I realized we might need third hook > - in confirm phase - which would be run on the

Cool :) Don't worry I'm not on a rush: I guess the feature will not be part of Debian before next major release anyway. Le ven., janv. 24, 2020 at 17:24, Michal Privoznik <mprivozn@redhat.com> a écrit : > On 1/24/20 4:34 PM, Guy Godfroy wrote: >> I don't really understand what new hook this would be. > > Libvirt's migration happens in phases [1]. The last

On Fri, Jan 04, 2019 at 17:27:48 +0100, daggs wrote: > Greetings Peter, > > > Sent: Friday, January 04, 2019 at 4:47 PM > > From: "Peter Krempa" <pkrempa@redhat.com> > > To: daggs <daggs@gmx.com> > > Cc: libvirt-users@redhat.com > > Subject: Re: [libvirt-users] script called from qemu hook freezes. > > > > On Thu, Jan 03, 2019

That's right, I need also that second hook event. For your information, for now I manage locks manually or via Ansible. To make hook manage locks, I still need to find out a secure way to run LVM commands from a non-root account, but this is another problem. Le 22 janvier 2020 10:24:53 GMT+01:00, Michal Privoznik <mprivozn@redhat.com> a écrit : >On 1/22/20 9:23 AM, Guy Godfroy

Hi, "Before a QEMU guest is started, the qemu hook script is called" (http://libvirt.org/hooks.html)... In writing a simple bash script to prevent a VM on shared storage from being started on one host if it's already running on another, it's easy enough to check if virsh on the other host reports the particular VM as "shut off" there, and go ahead if that's the

I could launch `lvchange -asy` on the source host manually, but the aim of hooks is to automatically execute such commands and avoid human errors. Le 22 janvier 2020 09:18:54 GMT+01:00, Michal Privoznik <mprivozn@redhat.com> a écrit : >On 1/21/20 9:10 AM, Guy Godfroy wrote: >> Hello, this is my first time posting on this mailing list. >> >> I wanted to suggest a

Hello, this is my first time posting on this mailing list. I wanted to suggest a addition to the qemu hook. I will explain it through my own use case. I use a shared LVM storage as a volume pool between my nodes. I use lvmlockd in sanlock mode to protect both LVM metadata corruption and concurrent volume mounting. When I run a VM on a node, I activate the desired LV with exclusive lock