search for: blockjobs

Hi everyone, I have a question that you may be able to help me with. I had a live block migration of 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

> virsh dumpxml --security-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

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

Am 02.07.13 15:42, schrieb Eric Blake: > On 07/02/2013 06:55 AM, Thomas Stein wrote: >> >>> virsh dumpxml --security-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? > > Undefining

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

Il 13/01/2015 10:51, Kashyap Chamarthy ha scritto: > On Tue, Jan 13, 2015 at 10:10:53AM +0100, Fiorenza Meini wrote: >> Hi there, >> I receive this error when I run nova image-create <VM name> <Vm Sanpshot >> name>: > > Okay, you're talking in the context of OpenStack. > > You can also check the Nova compute.log for more contextual details of >

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

On Thu, Feb 27, 2020 at 18:28:44 -0700, Blake Anderson wrote: > > Hi everyone, > I have a question that you may be able to help me with. I had a live block migration of 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

On 07/02/2013 06:55 AM, Thomas Stein wrote: > >> virsh dumpxml --security-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? Undefining the VM will not be necessary after two things happen: 1. qemu supports persistent

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

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 ?

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

Hi everyone, we are suddenly having a problem with executing our backup jobs. For a long time, we have used a shell script which contains the following code to backup all our virtual machines: for domain in Testserver Faktura Fileserver Gitolite Jenkins Nexus SimpleHelp VpnGateway Wiki; do echo -n "$(date +"%Y-%m-%d %H:%M:%S") starting backup for vm

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 > >> > >>Libvirt is 1.2.7 version, linux system is Debian Wheezy > >> >

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

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

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

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 =

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