similar to: virsh blockcommit fails regularily (was: virtual drive performance)

On Mon, Aug 14, 2017 at 08:42:24 +0200, Dominik Psenner wrote: > Hi, 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.

Just a little catch-up. This time I was able to resolve the issue by doing: virsh blockjob domain hda --abort virsh blockcommit domain hda --active --pivot Last time I had to shut down the virtual machine and do this while being offline. Thanks Wang for your valuable input. As far as the memory goes, there's plenty of head room: $ free -h total used free

Hi, different day, same issue.. cronjob runs and fails: $ virsh snapshot-create-as --domain domain --name backup --no-metadata --atomic --disk-only --diskspec hda,snapshot=external error: failed to pivot job for disk hda error: block copy still active: disk 'hda' not ready for pivot yet Could not merge changes for disk hda of domain. VM may be in invalid state. Then running the

Hi, after a recent live backup done with a snapshot, blockcommit failed and a subsequent (manual) blockjob abort got stuck. Now we are unable to do basic operations on the virtual machine like if it was frozen and when issuing another command we see the following: $ virsh shutdown $domain error: Failed to shutdown domain $domain error: Timed out during operation: cannot acquire state change lock

Hi again, just today an issue I've thought to be resolved popped up again. We backup the machine by doing: virsh snapshot-create-as --domain domain --name backup --no-metadata --atomic --disk-only --diskspec hda,snapshot=external # backup hda.qcow2 virsh blockcommit domain hda --active --pivot Every now and then this process fails with the following error message: error: failed to pivot

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

mybe this is because you physic host memory is small then this will Causing instability of the virtual machine But I'm just guessing You can try to increase your memory Wang Liming 发件人: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] 代表 Dominik Psenner 发送时间: 2017年7月2日 16:22 收件人: libvirt-users@redhat.com 主题: Re: [libvirt-users] virtual drive

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

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 Fri, Jun 30, 2017 at 10:41:25 -0400, doug.hughes@keystonenap.com wrote: > sorry about top post, tablet mail client... > > brilliant! that did it! Any idea what happened to cause it to partially fail and get into this state? virsh blockcommit --pivot is actually 3 operations in sequence: 1) initiate the commit job 2) wait till it finishes 3) initiate the pivot job (this is

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:

It has been the version available on ubuntu 16.04 lts: $ virsh --version 1.3.1 Please file a bug for me if you think it is one. On 25 Oct 2017 2:34 p.m., "Michal Privoznik" <mprivozn@redhat.com> wrote: > On 10/22/2017 02:04 PM, Dominik Psenner wrote: > > Hi, > > > > after a recent live backup done with a snapshot, blockcommit failed and a > >

Hi, I use this procedure to backup my VM's: http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit It works on my current host: Compiled against library: libvirt 1.2.16 Using library: libvirt 1.2.16 Gebruikte API: QEMU 1.2.16 Draaiende hypervisor: QEMU 2.1.0 Now I'm doing a test on a testing host: Compiled against library: libvirt 1.2.21 Using library: libvirt 1.2.21

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

On 10/22/2017 02:04 PM, Dominik Psenner wrote: > Hi, > > after a recent live backup done with a snapshot, blockcommit failed and a > subsequent (manual) blockjob abort got stuck. Now we are unable to do basic > operations on the virtual machine like if it was frozen and when issuing > another command we see the following: > > $ virsh shutdown $domain > error: Failed to

I'm not familiar with the libvirt codebase, but the extension of libvirt-guests.sh indicates that it is a shell script. Maybe you can modify it to find the spot where it hangs? 2017-07-09 18:49 GMT+02:00 Jędrek Domański <jedrek.domanski@gmail.com>: > Yeah, I know. Sorry for my demanding attitude. > > Any hints how I could start debugging the problem? > > 2017-07-09 18:12

On Tue, Jun 20, 2017 at 04:24:32PM +0200, Gianluca Cecchi wrote: > On Tue, Jun 20, 2017 at 3:38 PM, Dominik Psenner <dpsenner@gmail.com> wrote: > > > > > to the following: > > > > <disk type='file' device='disk'> > > <driver name='qemu' type='qcow2' cache='none'/> > > <source

Hi guys, When performing live merge, in few cases, we see the following exception: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 736, in wrapper return f(*a, **kw) File "/usr/share/vdsm/virt/vm.py", line 5278, in run self.tryPivot() File "/usr/share/vdsm/virt/vm.py", line 5247, in tryPivot ret =

Yeah, I know. Sorry for my demanding attitude. Any hints how I could start debugging the problem? 2017-07-09 18:12 GMT+02:00 Dominik Psenner <dpsenner@gmail.com>: > You can't expect anyone to step up happily to fix a problem you > experience. If you're unhappy with the open source solution you have at > least 4 options: > > 1. buy a license for red hat > 2. get

Hi Dominik, So what is going on on my computer with the script *libvirt-guests.sh*? Why is it hanging on it? How should I address this problem? I really appreciate your help! Thank you! 2017-07-07 9:20 GMT+02:00 Dominik Psenner <dpsenner@gmail.com>: > And software is up to date to latest version in LTS: > > $ virsh --version > 1.3.1 > > > 2017-07-07 9:20 GMT+02:00