search for: quiesce

...commit，qemu-img rebase to shorten snapshot chain. Details are as follows（when VM running state， we perform the following operations）: (1) the host machine control VM test virsh snapshot-create-as mix snap1 --diskspec vda,file=/tmp/mul/loop-mix-commit-rebase/snap1-mix.img --disk-only --atomic --quiesce virsh snapshot-create-as mix snap2 --diskspec vda,file=/tmp/mul/loop-mix-commit-rebase/snap2-mix.img --disk-only --atomic --quiesce virsh snapshot-create-as mix snap3 --diskspec vda,file=/tmp/mul/loop-mix-commit-rebase/snap3-mix.img --disk-only --atomic --quiesce virsh snapshot-create-as mix snap4...

...while creating snapshots. I posted on Stack Exchange [1], but figured I might get more success here. My VM backup script fails while creating the snapshot. virsh snapshot-create-as --domain machine_1 snap --diskspec vda,file=/srv/test/test-snap.qcow2 --disk-only --atomic --no-metadata --quiesce error: Requested operation is not valid: domain is already quiesced Even after a VM reboot, the system is still quiesced and I get the same error. I thought quiesce means FS freeze, but this makes no sense since I can still write to the FS when logged in the faulty VMs. And this would not...

Hi everyone! I use the libvirt(version: 1.2.2) and QEMU(version: 2.2.1) to test qemu snapshot features: I tried virsh blockcommit when VM offline, the virsh blockcommit failed: the error messase as below: error: Requested operation is not valid: domain is not running when I start the VM, the virsh blockcommit work fine! my question is：we need

...; > make > > sense to include --memspec to capture the memory state so that an fsck on > > boot > > isn't necessary? I remember you explained --quiese awhile back: > > https://www.redhat.com/archives/libvirt-users/2013-February/msg00020.html > > --memspec and --quiesce are orthogonal, you only need one or the other > (in fact, they do NOT work together in the current implementation). > --memspec says to capture the domain memory state (migrate to file; > using --live additionally says to minimize the time the guest is paused > but the file may be larg...

Hi Eric. Thank you so much for your quick and relieving answer. Le 2015-09-11 17:05, Eric Blake a écrit : > Yes, using active block-commit is the ideal way to perform a live backup. Great. > Yep, that about covers it. Note that the --quiesce step in snapshot > creation requires qemu-guest-agent running in the guest, and that you > trust interaction with your guest. Yes, I think I get this. I don't really figure out what these cases could be. We're using Debian Jessie and I installed qemu-guest-agent. Other VM could use o...

...; I posted on Stack Exchange [1], but figured I might get more success here. > > My VM backup script fails while creating the snapshot. > >     virsh snapshot-create-as --domain machine_1 snap --diskspec > vda,file=/srv/test/test-snap.qcow2 --disk-only --atomic --no-metadata > --quiesce >     error: Requested operation is not valid: domain is already quiesced This is the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1160084 Should be fixed in 1.2.11 by 6085d917d5c5839b7ed351e99fadbbb56f5178fe. Upgrade and the bug should go away. Michal

...This also means that I am unable to utilize the xen snapshots. What I would like to do is to use the zfs snapshots so that I can replicate them between sites. However, my issue is that we will have several database servers as well as exchange 2007 running in virtual machines and we need to somehow quiesce these vms during the zfs snapshot procedure otherwise they will only be crash consistent, which can be very bad as many of you know. Is there a way to call the quiesce operation at the same time I am calling the zfs snapshot? Is there an api call that I can make to accomplish this? Does anyone have...

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> To: "Andrew Martin" > <amartin@xes-inc.com>, libvirt-users@redhat.com Sent: Thursday, May 22, 2014 > 5:44:54 PM Subject: Re: [libvirt-users] Live snapshots of a single block > device > > On 05/22/2014 04:31 PM, Andrew Martin wrote: > > Hello, > > > > [Can you

...nged, 2 deletions(-) diff --git a/fs/fuse/virtio_fs.c b/fs/fuse/virtio_fs.c index c483482185b6..eadaea6eb8e2 100644 --- a/fs/fuse/virtio_fs.c +++ b/fs/fuse/virtio_fs.c @@ -208,7 +208,6 @@ static void virtio_fs_free_devs(struct virtio_fs *fs) if (!fsvq->fud) continue; - /* TODO need to quiesce/end_requests/decrement dev_count */ fuse_dev_free(fsvq->fud); fsvq->fud = NULL; } @@ -1022,7 +1021,6 @@ static int virtio_fs_fill_super(struct super_block *sb) if (i == VQ_REQUEST) continue; /* already initialized */ fuse_dev_install(fsvq->fud, fc); - atomic_inc(&fc-...

Author: jesusm Repository: /hg/zfs-crypto/gate Revision: 0c4dd65cca5bd3b8022d696234d9797a4a5b2110 Log message: 6244519 dead code to suspend kernel threads on OS quiesce should be removed Files: update: usr/src/uts/sun4u/ngdr/io/dr_quiesce.c

Hi, How I can I quiesce / freeze all writes to zfs and zpool if want to take hardware level snapshots or array snapshot of all devices under a pool ? are there any commands or ioctls or apis available ? Thanks & Regards, sridhar. -- This message posted from opensolaris.org

On 09/11/2015 10:18 AM, Jérôme wrote: >> Yep, that about covers it. Note that the --quiesce step in snapshot >> creation requires qemu-guest-agent running in the guest, and that you >> trust interaction with your guest. > > Yes, I think I get this. I don't really figure out what these cases > could be. We're using Debian Jessie and I installed qemu-guest-agen...

...r creating live backups of VMs - would it make > sense to include --memspec to capture the memory state so that an fsck on boot > isn't necessary? I remember you explained --quiese awhile back: > https://www.redhat.com/archives/libvirt-users/2013-February/msg00020.html --memspec and --quiesce are orthogonal, you only need one or the other (in fact, they do NOT work together in the current implementation). --memspec says to capture the domain memory state (migrate to file; using --live additionally says to minimize the time the guest is paused but the file may be larger), and when the gu...

...2. Create an external live snapshot: $ virsh snapshot-create-as --domain vm1 sn1 \ --diskspec vda,file=/export/images/sn1.qcow2 \ --disk-only --atomic --no-metadata Note (thanks Eric Blake): Above, if you have QEMU guest agent installed in your virtual machine, try --quiesce option with 'snapshot-create-as' to ensure you have a consistent disk state. Now, you have a disk image chain: base <-sn1 (live QEMU) 3. Take a backup of the original disk in backround: $ rsync -avh --progress /export/images/base.img \ /export/images/...

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

Hello, I have two servers where I can push VMs from one to the other by issuing the command virsh migrate --live --persistent --copy-storage-all --verbose \ test6 qemu+ssh://kvmhost2/system on kvmhost1. I can get the VM back by issuing the equivalent command on kvmhost2: virsh migrate --live --persistent --copy-storage-all --verbose \ test6 qemu+ssh://kvmhost1/system virsh

Hi everybody, I'm trying to implement in the non profit organization where I work a backup strategy for our VMs. At the moment I weekly backup the machine (on sunday nights) by stopping the vm, making a snapshot, exporting the xml descriptor file and syncing these files to a remote backup server. I would really like to make daily snapshot without shutting down the vms. at the moment the vms

...wiki [2]. -> Considering our use case, is this the recommended way? Assuming yes, here is the plan. I wrote a script that does # Create snapshot virsh snapshot-create-as --domain $VM_NAME snap --diskspec vda,file=$VM_DIR/"$VM_NAME"-snap.qcow2 --disk-only --atomic --no-metadata --quiesce # Copy frozen backing file cp $VM_DIR/"$VM_NAME".qcow2 $SNAP_FILEPATH # Blockcommit snapshot back into backing file virsh blockcommit $VM_NAME vda --active --pivot # Remove snapshot file rm $VM_DIR/"$VM_NAME"-snap.qcow2 Variables should be self-explanatory: - VM_DIR is the...

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

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> > To: "Andrew Martin" <amartin@xes-inc.com>, libvirt-users@redhat.com > Sent: Thursday, July 21, 2016 5:40:07 PM > Subject: Re: [libvirt-users] Blockpull behavior when interrupted > > On 07/21/2016 03:05 PM, Andrew Martin wrote: > > Hello, > > > > I use