search for: blockjob

...a qemu-kvm guest fail (initiated via nova), in which the guest remained running on the source, but if I try to re-initiate the live migration it returns libvirtError: Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainMigratePerform3Params). Looking at blockjob --info I see there is a block copy that has been stuck at 23 % for a few hours now. Is it safe to issue a —abort to the blockjob without impacting the vm and will that resolve the lock? Source: libvirt-4.5.0-23.el7_7.5.x86_64 qemu-kvm-ev-2.10.0-21.el7_5.7.1.x86_64 Destination: libvirt-4.5.0-23.el...

...ty-info dom > dom.xml > virsh undefine dom Hello. Someone was talking about this (undefining the VM) would not be neccessary anymore when qemu-1.5 has been released. Is that true? > virsh blockcopy dom vda /path/to/backup-vda > polling loop - check periodically until 'virsh blockjob dom vda' > shows 100% completion > virsh suspend dom > virsh save dom /path/to/memory-backup --running This does not work for me. hn ~ # virsh blockjob gentoo-template vda Block Copy: [100 %] hn ~ # virsh save gentoo-template /opt/virt-backup-blockcopy/gentoo-template/gentoo-t...

...The original image is still there. Only the 1st and > only top-level snapshot is deleted. > the blockcommit fails though: > [root@vm1 ~]# virsh blockcommit serv1r2 vda --active --pivot > error: block copy still active: disk 'vda' already in active block job What does 'virsh blockjob serv1r2 vda' report? If it's something like this: $ virsh blockjob fedora23 vda Active Block Commit: [100 %] Then you just need to finalize the block job by: virsh blockjob --pivot serv1r2 vda If that's not the case, please post what virsh blockjob is reporting and the <disk>...

...> it is ended); I'm also trying to figure out what API additions are > needed to libvirt to expose that capability as an alternative. Okay, understood. >> >>> virsh blockcopy dom vda /path/to/backup-vda >>> polling loop - check periodically until 'virsh blockjob dom vda' >>> shows 100% completion >>> virsh suspend dom >>> virsh save dom /path/to/memory-backup --running >> >> This does not work for me. >> >> hn ~ # virsh blockjob gentoo-template vda >> Block Copy: [100 %] >> >&gt...

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 (held...

...below maybe. > > For the Nova libvirt guest that you're trying to create a snapshot of, > find the location of its current block device: > > $ virsh domblklist instance-YYYYYYYYY > > Then check if there are active block operaations for that disk: > > $ virsh blockjob instance-YYYYYYYYY /path/to/libvirt/disk/ --info > > If there is any operation and if it is a test environment, you can > run the below to abort the block operation in progress: > > $ virsh blockjob instance-YYYYYYYYY /path/to/libvirt/disk/ --abort. > > Please the man page...

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? oot@vm1 ~]# virsh blockjob serv1r2 vda Active Block Commit: [100 %] [root@vm1 ~]# virsh blockjob --pivot serv1r2 vda [root@vm1 ~]# [root@vm1 ~]# ls -l /var/lib/libvirt/images/serv1r2.qcow2 -rw-r--r--. 1 qemu qemu 54200696832 Jun 30 10:39 /var/lib/libvirt/images/serv1r2.qcow2 [root@vm1 ~]# date Fri Jun 30 10:39:12 EDT 201...

...a qemu-kvm guest fail (initiated via nova), in which the guest remained running on the source, but if I try to re-initiate the live migration it returns libvirtError: Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainMigratePerform3Params). Looking at blockjob --info I see there is a block copy that has been stuck at 23 % for a few hours now. Is it safe to issue a —abort to the blockjob without impacting the vm and will that resolve the lock? The domain job lock is held by the whole migration API not just the blockjob. Aborting the blockjob or the migra...

...nt in time where it is started, not where it is ended); I'm also trying to figure out what API additions are needed to libvirt to expose that capability as an alternative. > >> virsh blockcopy dom vda /path/to/backup-vda >> polling loop - check periodically until 'virsh blockjob dom vda' >> shows 100% completion >> virsh suspend dom >> virsh save dom /path/to/memory-backup --running > > This does not work for me. > > hn ~ # virsh blockjob gentoo-template vda > Block Copy: [100 %] > > hn ~ # virsh save gentoo-template >...

...e API call) Apparently in your case the waiting part failed for some reason and thus the job was not finished, lingering in the synchronised state. The unfortunate part is that you don't know which operation failed. Unfortunately it does not seem that we have wa waiting version of 'virsh blockjob' that could be used to do the waiting. You can do the polling manualy though. The third operation can be split out by default, since you can specify --wait instead of --pivot for 'virsh blockcommit' and it will finish after step 2 above. Also one of the cases which would help is that...

Hi there, I receive this error when I run nova image-create <VM name> <Vm Sanpshot name>: Exception during message handling: block copy still active: domain has active block job In libvirt log file I can see: error : qemuDomainDefineXML:6312 : block copy still active: domain has active block job Libvirt is 1.2.7 version, linux system is Debian Wheezy Please, what does it mean ?

...omblklist rasa Target Source ------------------------------------------------ vda /var/lib/libvirt/images/rasa-sn1.qcow2 If blockcommit had succeeded, it would be now: vda /var/lib/libvirt/images/rasa.qcow2 Now both files rasa.qcow2 and rasa-sn1.qcow2 are written to, and # virsh blockjob rasa vda Active Block Commit: [100 %] But trying to virsh blockcommit rasa vda --active --verbose --pivot once more: error: block copy still active: disk 'vda' already in active block job How do I make rasa.qcow2 the only active vda? I use qemu-kvm-ev-2.3.0-29.1.el7. Thanks, Nerijus

...mlog} done This has worked great for us, but all of the sudden (eventually triggered by an update, since of course we do regular security/package updates on this machine) we are having problems. For some virtual machines, it still works perfectly, but for others, virsh tells us that a blockjob is still active and therefore the backup fails. This seems to happen to machines at random. However, when we then try to query the active blockjob, virsh tells us that no blockjob is active. Consider the following log from the shell: root@gfii-host:~# virsh undefine Gitolite...

...Nova libvirt guest that you're trying to create a snapshot of, > >find the location of its current block device: > > > > $ virsh domblklist instance-YYYYYYYYY > > > >Then check if there are active block operaations for that disk: > > > > $ virsh blockjob instance-YYYYYYYYY /path/to/libvirt/disk/ --info > > > >If there is any operation and if it is a test environment, you can > >run the below to abort the block operation in progress: > > > > $ virsh blockjob instance-YYYYYYYYY /path/to/libvirt/disk/ --abort. > &g...

Nerijus Baliunas <nerijus@...> writes: > But trying to virsh blockcommit rasa vda --active --verbose --pivot once more: > error: block copy still active: disk 'vda' already in active block job > > How do I make rasa.qcow2 the only active vda? "virsh blockjob rasa vda --abort" aborts the blockcommit and then I can try to blockcommit again: # virsh blockjob rasa vda --abort # 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 read...

...isk 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 following in the morning succeeds and successfully pivotes the snapshot into the base image while the vm is live: $ virsh blockjob domain hda --abort $ virsh blockcommit domain hda --active --pivot Successfully pivoted We run the backup process every day once and it failed on the following days: 2017-07-07 2017-07-20 2017-07-27 2017-08-12 2017-08-14 Looking at this it roughly happens once a week and the guest from then on w...

On 01/13/2015 07:21 AM, Kashyap Chamarthy wrote: > On Tue, Jan 13, 2015 at 03:07:07PM +0100, Fiorenza Meini wrote: >> Il 13/01/2015 10:51, Kashyap Chamarthy ha scritto: > > [. . .] > >>>> In libvirt log file I can see: >>>> error : qemuDomainDefineXML:6312 : block copy still active: domain has >>>> active block job > > Seems like

...all 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 = self.vm._dom.blockJobAbort(self.drive.name, flags) File "/usr/share/vdsm/virt/virdomain.py", line 68, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 124, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-pack...

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

...000000 00:00000000 > 00000000 107 0 931295 1 ffff88043a27f840 99 0 0 10 -1 > > 4: 00000000:170D 00000000:0000 0A 00000000:00000000 00:00000000 > 00000000 107 0 931297 1 ffff88043a27f140 99 0 0 10 -1 > > [root@source ~]# Further, on the source, if I query the blockjobs status, it says no blockjob is running: [root@source ~]# virsh list > Id Name State > ---------------------------------------------------- > 11 test_vm paused > [root@source ~]# virsh blockjob 11 vda > No current block job f...