search for: fsfreeze

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

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 backdoor for testing arbi...

...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 'guest-fsfreeze-freeze': failed to freeze /: Device or resource busy" I don't think this is not some sort of time-out error, because activation of the fsfreeze and the error message happen immediately after each other: $ grep qemu-ga syslog.1 May 25 00:51:19 CmsrvMTA qemu-ga: info: guest-fsfreeze ca...

...e: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_qemu-ga.exe_bd 2e6535bdb93328680e0285e89e08f2866db83_0b0deada Analysis symbol: Rechecking for solution: 0 Report Id: 3d82596e-517c-11ea-b213-525400e83365 Report Status: 0 -----Original Message----- Cc: libvirt-users Subject: Re: guest-fsfreeze-freeze freezes all mounted block devices 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...

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?

...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: > > https://github.com/qemu/qemu/blob/master/scripts/qemu-guest-agent/fsfreeze > > -h ook After a little bit of fiddling i've got this running. Here is what's neccessary in case someone wanna try this too. qemu-guest.-agent has to run with the option: "-F /etc/qemu/fsfreeze-hook". This file contains as pointed out by Eric: https://github.com/qemu/...

...tp://callecalle.uach.cl/ovirt-engine/docs/manual/en_US/html/Technical_Guide/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: https://github.com/qemu/qemu/blob/master/scripts/qemu-guest-agent/fsfreeze-hook -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

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...] Freeze mounted filesystems within a running domain to prepare for consistent snapshots. The --m...

...ibvirt 1.2.11. Guest Agent is running in the vm. > > I'm trying to snapshot: > > > > virsh # snapshot-create-as --domain sles11 --name sn_sles11 --atomic > > --disk- only --quiesce > > error: internal error: unable to execute QEMU agent command > > 'guest-fsfreeze-freeze': The command guest-fsfreeze-freeze has been > > disabled for this instance > > > > What is now going on ? > > Guest Agent in VM is qemu-guest-agent-2.0.2-1.35. > > virsh # qemu-agent-command sles11 '{"execute": "guest-info"}' {...

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 , type 0 > Event Name: APPCRASH...

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

> -----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 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-- >> >> # virsh domfsfreeze <domain> --mountpoint <mountpoint> >> >&g...

...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 guests, I enabled access between compute nodes and guests through a socket by setting metadata parameter, hw_qemu_guest_agent=yes for the guest image. And then installing qemu-guest-agent inside the guest. What steps do i have to follow for windows ? Regars, Payes

In every place where sb_start_pagefault was called now we must manage the error code and return VM_FAULT_RETRY. Signed-off-by: Marco Stornelli <marco.stornelli at gmail.com> --- fs/btrfs/inode.c | 4 +++- fs/buffer.c | 4 +++- fs/ext4/inode.c | 4 +++- fs/f2fs/file.c | 4 +++- fs/gfs2/file.c | 4 +++- fs/nilfs2/file.c | 4 +++- fs/ocfs2/mmap.c |

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

...ss-response":*false*}, {"enabled":true,"name":"guest-suspend-disk","success-response":*false*}, {"enabled":true,"name":"guest-fstrim","success-response":true}, {"enabled":true,"name":"guest-fsfreeze-thaw","success-response":true}, {"enabled":true,"name":"guest-fsfreeze-freeze-list","success-response":true}, {"enabled":true,"name":"guest-fsfreeze-freeze","success-response":true}, {"enabled":...

...> of time to save a VM... > I managed to update to libvirt 1.2.11. Guest Agent is running in the vm. I'm trying to snapshot: virsh # snapshot-create-as --domain sles11 --name sn_sles11 --atomic --disk-only --quiesce error: internal error: unable to execute QEMU agent command 'guest-fsfreeze-freeze': The command guest-fsfreeze-freeze has been disabled for this instance What is now going on ? Guest Agent in VM is qemu-guest-agent-2.0.2-1.35. Bernd Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherber...

Hello, For some vms the virsh backup-begin sometimes shuts off the vm and returns "error: operation failed: domain is not running" although it was clearly in state running (or paused). Is the idea that you should guest-fsfreeze-freeze / virsh suspend before virsh backup-begin? I have tried with both with the same results. What could be causing the machine to shut off? Thanks, Andr?