similar to: Disk backup for live and offline domains

Hi, I followed the instructions on the wiki https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit for a live disk backup. Unfortunately this is not working when the domain is offline because the active blockcommit throws error: Requested operation is not valid: domain is not running For my use case it should be possible for the domain to shut down while the backup is in

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

Hi! I was reading the Wiki about 'Live Disk Backup with Active Blockcommit, https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit and see that example shown seems to be using two different names for the same file. First showing the current block device in use: $ virsh domblklist vm1 Target Source ------------------------------------------------ vda

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

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

Thanks Kashyap for replying. QEMU has permissions to the directory which is having images. I will look into the AppArmor issue and find out more about this. Also as per suggestion from the link i have uncommented the user and group from the qemu.conf file - https://github.com/jedi4ever/veewee/issues/996 By checking more on the AppArmor and sVirt issue , i have modified the qemu.conf for

This is not a libvirt/redhat question… With your method you can only revert to versions which are available in the standard repositories. You’ll have to download the packages manually to force a different version. Use with caution. There is a reason why the version isn’t in the standard repositories. Van: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] Namens Keyur

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

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

All, I have a service that takes new live KVM snapshots Si regularly, keeps a fixed number N (Si ,..,Si-N+1), and therefore needs to delete Si-N in this cycle. Until libvirt includes support for this capability that is said to be available in qemu, what is a safe workflow to delete old live KVM snapshots w/o losing data. Do I need to pause/shut down the VM? The development environment is

Hi , Based on the discussion and links referred as mentioned in earlier thread , I could able to perform the block commit and other operations successfully. Here are the changes required to perform block commit 1. Used Ubuntu 15.04 which has following versions of Libvirt and Qemu Compiled against library: libvirt 1.2.12 Using library: libvirt 1.2.12 Using API: QEMU 1.2.12 Running hypervisor:

Hi Was trying to get specific qemu-kvm version. Do you know any way to get the 2.1.2 installed. Was trying sudo apt-get install qemu-kvm=1.2.1 but its not working. Tried with sudo apt-get install qemu-kvm tree=1.2.1 But both have failed for Version not found. Thanks Keyur On Tue, Dec 8, 2015 at 11:21 AM, Keyur Bhalerao <keyurbhalerao@gmail.com> wrote: > Thanks Kashyap for replying.

On Mon, Dec 07, 2015 at 12:52:34PM -0800, Keyur Bhalerao wrote: [. . .] ubuntu@keyurubuntu:~$ virsh blockcommit vm-01 vda --active --verbose --pivot > error: internal error: unable to execute QEMU command 'block-commit': Could > not reopen file: Permission denied Fairly obvious suggestions, ensure permissions are set so that QEMU has permissions to the dir that contains images.

On standard Fedora 18 I was attempting blockcommit on a *live* VM, libvirt said it was not supported, so I tried fedora-virt-preview as recommended. We found a problem with qemu 1.4, there seems to be an acknowledged bug, a missing library. On a different system we loaded Fedora 18, and then pulled qemu (1.3) and libvirt (1.0.2) from rawhide. I tried blockcommit with domain shut down, it said

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. > 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 qemuDomainBlockCommit cheers t.

Am 26.07.16 um 10:25 schrieb Prof. Dr. Michael Schefczyk: > 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

On 09/11/2015 06:45 AM, Jérôme wrote: > AFAIU, live backups using libvirt may be done thanks to blockcommit as > explained here on the wiki [2]. > > -> Considering our use case, is this the recommended way? Yes, using active block-commit is the ideal way to perform a live backup. > > Assuming yes, here is the plan. > > I wrote a script that does > > #

Hello, one of my VM's blockcommit job always fails. How can I find the reason? Error message is not clear. virsh snapshot-create-as --domain my-vm backup-snapshot \ --diskspec vda,file=/foo/my-vm-snapshot.img \ --disk-only --atomic --no-metadata virsh blockcommit my-vm vda --active --verbose --wait --async virsh blockjob my-vm vda --pivot internal error: unable to execute QEMU