similar to: Suspend Domain (virsh suspend) or Freeze Filesystems (virsh domfsfreze) to take Snapshot of ISCSI volume

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

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

Hello everybody, This is a cross post to libvirt-users, libguestfs and ceph-users. I came back from FOSDEM 2016 and this was my 7th year or so and seen the awesome development around visualization going on and want to thank everybody for there contributions. I seen presentations from oVirt, OpenStack and quite a few great Redhat people, just like the last previous years. I personally been

Hello everybody, This is a cross post to libvirt-users, libguestfs and ceph-users. I came back from FOSDEM 2016 and this was my 7th year or so and seen the awesome development around visualization going on and want to thank everybody for there contributions. I seen presentations from oVirt, OpenStack and quite a few great Redhat people, just like the last previous years. I personally been

As stated in the below link from libvirt-list, https://www.redhat.com/archives/libvir-list/2014-May/msg00033.html > OpenStack cinder provides these storages' snapshot feature, but it cannot > quiesce the guest filesystems automatically for now. > > This patchset adds virDomainFSFreeze()/virDomainFSThaw() APIs and virsh > domfsfreeze/domfsthaw commands to enable the users to

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

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

# virsh snapshot-create-as small snap1 --disk-only --atomic error: Operation not supported: live disk snapshot not supported with this QEMU binary OS used: CentOS 7 #virsh version Compiled against library: libvirt 1.1.1 Using library: libvirt 1.1.1 Using API: QEMU 1.1.1 Running hypervisor: QEMU 1.5.3 Any help would be greatly appreciated. Best Regards, Payes

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 want to take snapshots of a iSCSI devices from a target that hasn't snapshot/cloning capabilities (it's a Infortrend A16E storage array). What method are you using to make snapshots/clones of iSCSI targets using Open-iSCSI + CentOS? What about using Open-iSCSI + LVM snapshots system? For example: - Take a LVM snapshot in the initiator with "lvcreate". - Give read-only

Hi, The package installed is qemu-kvm-1.5.3-60.el7_0.10.x86_64 on CentOS 7. I have upgraded my libvirt and qemu also, still i am getting the same error ( Operation not supported: live disk snapshot not supported with this QEMU binary ) # virsh version Compiled against library: libvirt 1.2.10 Using library: libvirt 1.2.10 Using API: QEMU 1.2.10 Running hypervisor: QEMU 2.0.0 On Mon, Nov 24,

On 12/22/2014 03:27 PM, Gary R Hook wrote: > I am experimenting with the blockcopy command, and after figuring out > how to integrate qemu-nbd, nbd-client and > dumpxml/undefine/blockcopy/define/et. al. I have one remaining question: > > What's the point? Among other uses, live storage migration. Let's say you are running on a cluster, where your VM is running locally but

On 11/23/2014 04:15 AM, Payes Anand wrote: > # virsh snapshot-create-as small snap1 --disk-only --atomic > error: Operation not supported: live disk snapshot not supported with this > QEMU binary > OS used: CentOS 7 Libvirt can't do live snapshots if the underlying qemu cannot. Since you are using CentOS, I'd look into finding the qemu-kvm-rhev package (the default qemu-kvm

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?

I don''t know if VSS has this capability, but essentially if it can temporarily quiesce a device like a data base does for "warm standby" then a snapshot should work. This would be a very simple Windows side script/batch: 1) Q-Disk 2) Remote trigger snapshot 3) Un Q-Disk I have no idea where to even begin researching VSS unfortunately... James (Sent from my mobile)