similar to: domain has active block job

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 >

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 there, I'm running KVM under Openstack . When I give virsh list command, I see some VM in NON persistent state. What does it mean? How can I move it to a persisten state ? I found that I cannot make a snapshot, from Openstack , of a machine which is in a NON PERSISTENT state. Regards Fiorenza -- Spazio Web S.r.l. V. Dante, 10 13900 Biella Tel.: +39 015 2431982 Fax.: +39 015 2522600

Hi there, I upgraded the package and now I receive this error while trying to start libvirtd. Is there a solution ? BUG: /build/buildd-libnl3_3.2.7-4-amd64-WWfXnH/libnl3-3.2.7/./lib/route/tc.c:970 Regards Fiorenza Meini -- Spazio Web S.r.l. V. Dante, 10 13900 Biella Tel.: +39 015 2431982 Fax.: +39 015 2522600 Numero d'Iscrizione al Registro Imprese presso CCIAA Biella, Cod.Fisc.e

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 why the operation failed. > Exception during message handling: block copy still active:

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

On 3/23/2015 12:49 PM, Michal Privoznik wrote: > On 23.03.2015 16:02, Fiorenza Meini wrote: >> Hi there, >> I'm running KVM under Openstack . >> >> When I give virsh list command, I see some VM in NON persistent state. >> What does it mean? How can I move it to a persisten state ? > You can do that by running: > > virsh dumpxml $dom > dom.xml

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

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

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

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

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

Hello, I'm looking for a method to track stream performance problems, I mean : why does listeners got buffering ? We are using two "front relay" that are hosted by differents providers. The front relays are connected to our main server (which encode) that is using two ADSL connections from two differents providers. How can I do to know if there is a problem between "Front relay

Hello. I've experience a rather surprising behaviour of the AMI 1.1 > Event: Newstate^M > Privilege: call,all^M > Channel: SIP/XXXXXX-089c63b8^M > ChannelState: 4^M > ChannelStateDesc: Ring^M > CallerIDNum: XXXXXXXX^M > CallerIDName: YYYYYYYYY^M > Uniqueid: 1256089773.59^M Usually ChannelStateDesc gives me 'Ringing' but sometimes it only gives me

Hello, We are running Asterisk-1.0.12 in a CentOS 4-4.2 system, kernel 2.6.9-42.0.3.ELsmp. We have some custom AGI, and when we launch Asterisk the system works fine. But **after some time**, each AGI execution generates a zombie <defunct> process. We believe that it's not a problem in the AGI code, because Asterisk+AGI is working fine in the first "n" minutes/hours. This