similar to: guest-fsfreeze-freeze freezes all mounted block devices

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

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

Hi everybody, I am having a problem with the use of domfsfreeze command. It is freezing all the filesystems present on the domain, instead of freezing just the mountpoints provided. I am issuing the command-- # virsh domfsfreeze <domain> --mountpoint <mountpoint> Output was-- Froze 3 filesystem(s) I want to freeze a particular mount point on the VM, so that i can take a

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

Hi, Is it possible to freeze windows guests for a consistent storage level snapshot. I am using openstack icehouse on centos 6.6 Hypervisor: KVM Libvirt: 0.10.2 Qemu: 0.10.2 Guest OS: Windows 7 and Windows Server 2008 I was able to freeze Centos guests by issuing the command: virsh qemu-agent-command <guest_ID> '{"execute":"guest-fsfreeze-freeze"}' For CentOS

On 11.11.2014 22:51, Eric Blake wrote: > On 11/11/2014 01:58 PM, Payes Anand wrote: >> Hi everybody, >> >> I am having a problem with the use of domfsfreeze command. >> >> It is freezing all the filesystems present on the domain, >> >> instead of freezing just the mountpoints provided. >> >> I am issuing the command-- >> >> #

On 11/12/14 22:17, Eric Blake wrote: > On 11/12/2014 10:24 AM, Michal Privoznik wrote: ... >> Although, I see a way that we could get something reasonable here. If >> qemu would tell us whenever somebody (dis-)connects (from)to the virtio >> channel. That way we could query the qemu-ga capabilities and make good >> decisions. And whenever we see a disconnect, we may

Hi, I use external snapshots to backup my guests. I use the 'quiesce' option to flush and frees the guest file system with the qemu guest agent. With the exeption of one guest, this procedure works fine. On the 'unwilling' guest, I get this error message: "ERROR 2016-05-25 00:51:19 | T25-bakVMSCmsrvVH2 | fout: internal error: unable to execute QEMU agent command

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

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

On 10/29/2014 01:07 PM, Thomas Stein wrote: > About the --quiesce option. Do i need to do something inside the vm? The most > commonly would probably be a sql server running inside the vm. Do i need to > tell the sql server something about the --quiesce option i use? I read this > article here which suggests such a procedure. Okay, it's vmware, but... Is > that right? For

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

On 12/10/2014 11:40 PM, Payes Anand wrote: > Hi, > Is it possible to freeze windows guests for a consistent storage level > snapshot. Yes, if you install qemu-guest-agent in the guest, and wire up your libvirt XML to have the guest-agent channel available. Once you have done that, use the --quiesce flag as part of creating your snapshots. > I was able to freeze Centos guests by

> -----Oorspronkelijk bericht----- > Van: Lentes, Bernd [mailto:bernd.lentes@helmholtz-muenchen.de] > Verzonden: donderdag 3 december 2015 13:54 > Aan: libvirt-ML > CC: Dominique Ramaekers > Onderwerp: RE: snapshot of running vm's > > > ... > > > > > > Hi, > > > > > > i have inserted: > > > > > > <channel

On Fri, Jul 22, 2016 at 2:51 PM, The Doctor <doctor at doctor.nl2k.ab.ca> wrote: > On Fri, Jul 22, 2016 at 02:40:04PM +1000, Damien Miller wrote: [...] >> OpenSSH 5.3 is almost ready for release, so we would appreciate testing > ^ > Huh? Either a clone of Damien has been frozen Austin Powers style since 2009 and has only just been thawed out or maybe it

On 11/11/2014 01:58 PM, Payes Anand wrote: > Hi everybody, > > I am having a problem with the use of domfsfreeze command. > > It is freezing all the filesystems present on the domain, > > instead of freezing just the mountpoints provided. > > I am issuing the command-- > > # virsh domfsfreeze <domain> --mountpoint <mountpoint> > > Output