similar to: Efficient live disk backup with active blockcommit : Failed 'block-commit': Could not reopen file: Permission denied

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

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.

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:

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.

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 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 (Eric?), A couple of questions while using the 'virsh blockpull' Summary: 1] Created snapshots this way: base<-snap1<-snap2<-snap3 (online, external snapshot --disk-only) 2] I did a 'virsh blockpull' from snap2 into snap3 3] Next, did another 'virsh blockpull' from snap1 into snap3 - Here, 'qemu-img info /path/to/snap3' shows its backing file

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

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

Hello, I recently compiled libvirt 1.0.1 and qemu 1.3.0 on Ubuntu 12.04. I have performed live snapshots on VMs using "virsh snapshot-create-as" and then later re-merge the images together using "virsh blockpull". I am wondering how I can do a couple of other operations on the images while the VM is running. For example, VM1 is running from the snap3 image, with the following

Hi all, I have a kvm virtual machine running (qemu version 2.0), and I had took several external snapshots of the disk( using "virsh snapshot-create-as"). Now, the existed disk files relationship look like: base <- snap1 <-snap2 <- current using disk file. Now I want to remove snap1 and snap2, and let current disk using the base image file as back file directly. Unfortunately,

Hi!   I want to print the output all together with a single column name   s21<-c(1:1000); var21<-lapply(s21,function(x){    ns<-rnorm(78,8,9);    n<-length(ns);    Mn<-mean(ns)    Sn2<-var(ns)    return(cbind(x,Mn,Sn2)); }); var21 but my code is giving me somewhat like the following [[1]] x   Mn          Sn2   [1,] 1 7.86 10.56540 [[2]] x   Mn          Sn2  

On Tue, Oct 14, 2014 at 02:08:41PM -0600, Eric Blake wrote: > On 10/14/2014 11:52 AM, Jd wrote: > > 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 > > Ouch. qemu-monitor-command is explicitly

On 04/22/2014 01:47 AM, Thomas Stein wrote: > Hello. > > The Changelog of qemu-2.0.0 mentioned "Live snapshot merging". Someone > has an idea what could be ment by this? I'm asking because i'm still > struggling with finding a reliable backup solution for running kvm > machines. Blockcopy is my current solution. "Live snapshot merging" means going

Hi, I'm using R to do a series of calculation and I have gotten several warnings that say "NaNS produced". Whatever I could read on line gives me an idea that this warning is produced when the number is use is a negative log or otherwise mathematically problematic. I'm getting this error while using factorial() and gamma () on strictly positive numbers (always greater than zero).

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

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

Hello all, 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 following error: error: internal error: unable to execute QEMU command 'block-commit': Could not reopen file: Permission denied I checked directory und image file permissions, app-armor profiles