similar to: Live Disk Backup with Active Blockcommit

Hi , Working on the simple POC : Advanced snapshot using libvirt and qemu . Following are the exact steps which are followed . 1. Created as base VM - Ubuntu 15.10 with following libvirt and qemu versions Using library: libvirt 1.2.16 Using API: QEMU 1.2.16 Running hypervisor: QEMU 2.3.0 QEMU emulator version 2.3.0 (Debian 1:2.3+dfsg-5ubuntu9.1), Copyright (c) 2003-2008 Fabrice

I have an automatic process setup. It's still pretty new and obviously in need of better error handling because now I find myself in a bad state. I run snapshot-create-as across all my vms, then do zfs replication to the target backup system, then blockcommit everything. virsh snapshot-create-as --domain $vm snap --diskspec $DISK,file=$VMPREFIX/"$vm"-snap.qcow2 --disk-only --atomic

On Fri, Jun 30, 2017 at 09:23:29 -0400, Doug Hughes wrote: > On Jun 30, 2017 6:22 AM, "Peter Krempa" <pkrempa@redhat.com> wrote: > > On Fri, Jun 30, 2017 at 12:05:47 +0200, Peter Krempa wrote: > > > On Thu, Jun 22, 2017 at 11:02:41 -0400, Doug Hughes wrote: [...] > file or directory > > $ virsh blockcommit --active --pivot fedora23 vda > > >

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

Am 13.10.14 16:25, schrieb Eric Blake: > On 10/13/2014 03:56 AM, Thomas Stein wrote: >> Hello. >> >>> blockcommit vm1 vda --active --verbose --pivot >> >> That's where libvirt stops working at the moment, right? >> >> virsh # blockcommit puppet-test vda --active --verbose --pivot >> error: unsupported flags (0x4) in function

Hello All, I think I have seen this in previous bugs. Trying to live backup qcow2 images. I am able to virsh snapshot-create-as and virsh domblklist shows correct new source, but I am unable to commit back changes to qcow base. I get the above error. Libvirt at 1.2.2-0ubuntu13.1.17 Qemu is (2.0.0+dfsg-2ubuntu1.22) I tried compiling latest libvirt, but cannot get it to connect to socket on

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

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:

Hi Kashyap Chamarthy: thank you very much for answer my question: 一： lead to VM filesystem becoming read-only 1： test case it lead to VM filesystem becoming read-only test case as follows: we want to snapshot for VM , to obtain VM incremental data，and use virsh blockcommit，qemu-img commit，qemu-img rebase to shorten snapshot chain. Details are as follows（when VM running state， we perform the

On Tue, Oct 13, 2015 at 10:39:58AM +0800, justlibvirt@gmail.com wrote: > Hi everyone! Hi, Firstly, please don't post the same message multiple times in a row. If someone hasn't responded, they're either busy, or haven't noticed this message. > I use the libvirt(version: 1.2.2) and QEMU(version: 2.2.1) to > test qemu snapshot features: > > I

Hi. I'm following here a conversation that was initiated on Kashyap's website [1]. We have a server we use as a host for virtual machines using KVM (virt-manager used for VM creation) and we would like to setup VM backups. Basically, we're thinking of a backup schedule like "keep 7 daily and 4 weekly backups". We'd rather not shutdown the VM every day so live backups

Hi, Recently We've upgraded some KVM hosts from Fedora 29 to Fedora 30 and now experience broken VM configurations on filesystem after virsh blockcommit. Commands "virsh dumpxml ..." and "virsh dumpxml --inactive ..." is showing diffrent configuration than the one on filesystem. In case of restart libvirtd or system reboot, there are broken VM xml configurations on

Posted to https://bugzilla.redhat.com/show_bug.cgi?id=1217185 I just stumbled on another bug while snapshotting and think it's related to 1210903 and 1197592 as it seems like some sort of race condition because it depends on what logging is in place and doesn't happen every time. Here are the details: I wrote this test script to snapshot and commit over and over: #!/bin/sh while [ 1

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

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

Hello, it happened with another VM: # virsh snapshot-create-as --domain rasa sn1 --diskspec vda,file=/var/lib/libvirt/images/rasa-sn1.qcow2 --disk-only --atomic --no-metadata # virsh blockcommit rasa vda --active --verbose --pivot Block commit: [100 %]error: failed to pivot job for disk vda error: block copy still active: disk 'vda' not ready for pivot yet # virsh domblklist rasa

On Jun 30, 2017 6:22 AM, "Peter Krempa" <pkrempa@redhat.com> wrote: > > On Fri, Jun 30, 2017 at 12:05:47 +0200, Peter Krempa wrote: > > On Thu, Jun 22, 2017 at 11:02:41 -0400, Doug Hughes wrote: > > > > [...] > > > > > virsh blockcommit $vm $DISK --active --pivot > > > > > > Normally this works fine, though something went

Dear All, using CentOS 7.2.1511, and libvirt from ovirt repositories (currently 1.2.17-13.el7_2.5, but without otherwise using ovirt) I am regularly backing up my VMs which are on qcow2 files. In general, I am trying to follow http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit A typical backup script would be #!/bin/bash dt=`date +%y%m%d` if virsh dominfo dockers10a | grep

On Monday 13 October 2014 16:35:15 Thomas Stein wrote: > Am 13.10.14 16:25, schrieb Eric Blake: > > On 10/13/2014 03:56 AM, Thomas Stein wrote: > >> Hello. > >> > >>> blockcommit vm1 vda --active --verbose --pivot > >> > >> That's where libvirt stops working at the moment, right? > >> > >> virsh # blockcommit

Il 07-09-2018 21:26 Eric Blake ha scritto: > We're also trying to add support for incremental backups into a future > version of libvirt on top of the qemu 3.0 feature of persistent > bitmaps in qcow2 images, which could indeed guarantee that you > transfer only the portions of the guest disk that were touched since > the last backup. But as that's still something I'm