similar to: Using qemu active blockcommit results in 'Permission denied' error

Hi Peter, On 31.05.19 09:57, Peter Krempa wrote: > On Thu, May 30, 2019 at 22:12:14 +0200, Marcus Hoffmann wrote: >> Hello all, > > Hi, > >> >> I tried following this guide: >> https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit >> >> Unfortunately when I try to do the final virsh blockcommit step I always >> get the

On May 31, 2019 2:03:40 PM GMT+02:00, Marcus Hoffmann <bubu@bubu1.eu> wrote: >Hi Peter, > >On 31.05.19 09:57, Peter Krempa wrote: >> On Thu, May 30, 2019 at 22:12:14 +0200, Marcus Hoffmann wrote: >>> Hello all, >> >> Hi, >> >>> >>> I tried following this guide: >>>

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

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

Hi, currently i'm following https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit. I 'm playing around with it and it seems to be quite nice. What i want is a daily consistent backup of my image file of the guest. I have the idea of the following procedure: - Shutdown the guest (i can live with a downtime of a few minutes, it will happen in the night). And i think

Hi, I have another question, when I do the blockcommit command and get the result " Top image as the active layer is currently unsupported ", is it being developed? root@cvk-31:/vms/images# virsh blockcommit Vmtest /vms/images/Vmtest1;echo $? error: internal error unable to execute QEMU command 'block-commit': Top image as the active layer is currently unsupported 1 But as I

----- On Sep 7, 2018, at 9:26 PM, Eric Blake eblake@redhat.com wrote: > On 09/07/2018 12:06 PM, Lentes, Bernd wrote: >> Hi, >> >> currently i'm following >> https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit. I 'm >> playing around with it and it seems to be quite nice. >> What i want is a daily consistent backup of my image file

hi, i am trying to blockcommit a external qcow2 snapshot back into its raw backing file like: sudo virsh blockcommit myDomainName vda --wait --verbose the output just shows: Block Commit: [100 %] and stays like that (i waited about an hour or so...). No "Commit complete" message. - explicitly passing --base and/or --top arguments makes no difference. - did not find a related log

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

Hi, I'm running into problems with blockcommit and gluster network disks - wanted to check how to pass path for network disks. How's the protocol and host parameters specified? For a backing volume chain as below, executing virsh blockcommit fioo5 vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c --base

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

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

I had test the command virsh blockcommit, but it failed, with the libvirt version 1.1.0, and qemu version 1.6.0. Is this feature being developing? Thanks root at cvk-31:/vms/images# virsh -v 1.1.0 root at cvk-31:/vms/images# qemu-img -V qemu-img version 1.6.0, Copyright (c) 2004-2008 Fabrice Bellard usage: qemu-img command [command options] root at cvk-31:/vms/images# virsh blockcommit Vmtest

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, I am receiving the following error when I try to run blockcommit: ============================================================== root@farnsworth:/var/lib/libvirt/images# virsh blockcommit pg94-test vda --top /var/lib/libvirt/images/pg94-test.snap4 --active --pivot --verbose error: unsupported flags (0x4) in function qemuDomainBlockCommit

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

Hello one and all. Got a problem with libvirt 6.2.0 and qemu 5.0.0. virsh blockcommit mymachine vda --active --verbose --pivot works until it shows [100%] but it never actually pivots. It just sits there. Is this a known issue with 6.2.0 and i should try 6.3.0? For now i switched back to qemu 4.2.0 and this seems to solve the issue too. Any hints? Ahoi! t.

Hi, a small update on this. We have migrated the virtualized host to use the virtio drivers and now the drive performance is improved so that we can see a constant transfer rate. Before it used to be the same rate but regularly dropped to a few bytes/sec for a few seconds and then was fast again. However we still observe that the following fails regularily: $ virsh snapshot-create-as --domain

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