similar to: Issue with fsfreeze with qemu agent.

Hi, I use this procedure to backup my VM's: http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit It works on my current host: Compiled against library: libvirt 1.2.16 Using library: libvirt 1.2.16 Gebruikte API: QEMU 1.2.16 Draaiende hypervisor: QEMU 2.1.0 Now I'm doing a test on a testing host: Compiled against library: libvirt 1.2.21 Using library: libvirt 1.2.21

On Mon, Feb 17, 2020 at 10:03:27 +0100, Marc Roos wrote: > Hi Peter, > > Should I assume that the virsh domfsfreeze, does not require the > qemu-agent service in the guest? No. That's the official way how to drive the "guest-fsfreeze-freeze" agent command via libvirt, thus you must have the guest agent the same way as you used it before. Using qemu-agent-command is a

On 10/14/2014 11:52 AM, Jd wrote: > Hi > > * Trying to get drive-backup command, getting permission denied. :( > > sudo virsh qemu-monitor-command --hmp my-instance --cmd > drive_backup drive-virtio-disk0 /tmp/foo.vda.img Ouch. qemu-monitor-command is explicitly unsupported, precisely because it goes behind libvirt's back and is likely to get libvirt confused.

Hmmm, using 'virsh domfsinfo testdom' gives me a crash in win2008r2 (using software from virtio-win-0.1.171.iso) Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: qemu-ga.exe P2: 100.0.0.0 P3: 5c473543 P4: KERNELBASE.dll P5: 6.1.7601.24545 P6: 5e0eb6bd P7: c0000005 P8: 000000000000c4d2 P9: P10: Attached files: These files may be

On 10/15/14, 2:37 AM, Kashyap Chamarthy wrote: > On Tue, Oct 14, 2014 at 02:08:41PM -0600, Eric Blake wrote: >> On 10/14/2014 11:52 AM, Jd wrote: >>> Hi >>> >>> * Trying to get drive-backup command, getting permission denied. :( >>> >>> sudo virsh qemu-monitor-command --hmp my-instance --cmd >>> drive_backup

On Tue, Oct 14, 2014 at 02:08:41PM -0600, Eric Blake wrote: > On 10/14/2014 11:52 AM, Jd wrote: > > Hi > > > > * Trying to get drive-backup command, getting permission denied. :( > > > > sudo virsh qemu-monitor-command --hmp my-instance --cmd > > drive_backup drive-virtio-disk0 /tmp/foo.vda.img > > Ouch. qemu-monitor-command is explicitly

Hi everybody, Following this user mailing list over a period of time, I saw a few messages regarding not being able using the external snapshot feature. I refer to this procedure: http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit I would like to mention this hoping it will help those users: Using external snapshots works perfect again in qemu 2.5.0 together with this

Dear Liam, You need to upgrade to the latest LTS version of Ubuntu (16.04). I refer to my message to this mailing list on 17/03/2016: Hi everybody, Following this user mailing list over a period of time, I saw a few messages regarding not being able using the external snapshot feature. I refer to this procedure: http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit I would

Hi * Trying to get drive-backup command, getting permission denied. :( sudo virsh qemu-monitor-command --hmp my-instance --cmd drive_backup drive-virtio-disk0 /tmp/foo.vda.img Looks like apparmor issue. What can I modify to make this work ? * Couple of other questions drive-backup : * The doc seems to claim that it gives a point in time copy of

Hi Peter, Should I assume that the virsh domfsfreeze, does not require the qemu-agent service in the guest? PS. I couldn't find the result. Afaik it looks like it is returning the amount of frozen/thawed filesystem's -----Original Message----- Cc: libvirt-users Subject: Re: guest-fsfreeze-freeze freezes all mounted block devices On Fri, Feb 14, 2020 at 22:14:55 +0100, Marc Roos

I wondered if anyone here can confirm that virsh qemu-agent-command domain '{"execute":"guest-fsfreeze-freeze"}' Freezes all mounted block devices filesystems. So if I use 4 block devices they are all frozen for snapshotting. Or just the root fs?

On Fri, Feb 14, 2020 at 22:14:55 +0100, Marc Roos wrote: > > I wondered if anyone here can confirm that > > virsh qemu-agent-command domain '{"execute":"guest-fsfreeze-freeze"}' Note that libvirt implements this directly via 'virsh domfsfreeze'. This is the corresponding man page entry: domfsfreeze domain [[--mountpoint] mountpoint...]

Link? -----Original Message----- Sent: 21 February 2020 11:50 To: Marc Roos Cc: pkrempa; libvirt-users Subject: Re: guest-fsfreeze-freeze freezes all mounted block devices On Mon, Feb 17, 2020 at 01:52:02PM +0100, Marc Roos wrote: > > Hmmm, using 'virsh domfsinfo testdom' gives me a crash in win2008r2 > (using software from virtio-win-0.1.171.iso) > > Fault bucket ,

On Fri, Oct 10, 2014 at 07:32:06PM -0600, Eric Blake wrote: > On 10/10/2014 11:37 AM, Jd wrote: > > Hi > > Looking in to implementing (CBT like) delta backup for KVM. > > Not quite sure what you mean by CBT. > > > > > The following looks promising..(last paragraph) > > http://wiki.qemu.org/Features/Snapshots2 > > > > Libvirt

I've been trying to implement the quota system for a Linux cluster. I'm trying it out on a mini-cluster of 4 CentOS 6.3 VMs. I've named them: lion-login lion-sn1 lion-cn01 lion-cn02 All nodes are on the virtual subnet 192.168.56.0/24. lion-sn1 (storage node 1) is the NFS server and the other three nodes are the NFS clients. /etc/exports on lion-sn1: /home 192.168.56.0/24(rw)

On Mon, Feb 17, 2020 at 01:52:02PM +0100, Marc Roos wrote: > > Hmmm, using 'virsh domfsinfo testdom' gives me a crash in win2008r2 > (using software from virtio-win-0.1.171.iso) > > Fault bucket , type 0 > Event Name: APPCRASH > Response: Not available > Cab Id: 0 > > Problem signature: > P1: qemu-ga.exe > P2: 100.0.0.0 > P3: 5c473543 > P4:

On Fri, Feb 21, 2020 at 04:35:46PM +0100, Marc Roos wrote: > Link? > > That's not good! Could you report this problem to the QEMU bug tracker. https://www.qemu.org/support/ Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org

> > A quick google search found this: > > http://callecalle.uach.cl/ovirt-engine/docs/manual/en_US/html/Technical_Gu > > id e/QEMU_Guest_Agent_Overview.html > > > > Sadly, it didn't spell out the name of where you install hook scripts > > into the guest. But this commit is pretty telling: > >

Hello, I did a virsh snapshot-create-as --domain meta sn1 --diskspec vda,file=/var/lib/libvirt/images/meta-sn1.qcow2 --disk-only --atomic --no-metadata Then I successfully blockcommitted 2 disks: virsh blockcommit meta vda --active --verbose --pivot virsh blockcommit meta vdb --active --verbose --pivot But when doing virsh blockcommit meta vdc --active --verbose --pivot I got: Block commit:

Dominique wrote: > > Never had that problem. Can it be a setting of the guest agent on the > guest? With me all the commands of the ga are enabled... > Where can i change the settings of the agent ? > You can check the commands by using this: > virsh qemu-agent-command $VM '{"execute": "guest-info"}' > > This way you can at least check that