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
>>
>>Please, what does it mean ?
>
>It means, according to libvirt, there's an unfinished `blockcopy` (Copy
>a disk backing image chain to destination ) operation.
>
>If you can find the associated libvirt guest name, you can try the
>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 of `virsh` for more details.
>
Thank for your response, I'm quite new on libvirt...
1) virsh blockjob ... -info gave me an empyt list
2( virsh blockjob ... -abort gave me this error: error: Requested operation
is not valid: another job on disk 'vda' is still being ended....
..but what ?
Seems like you're hitting an old bug[1] where 'blockcopy' (or
'blockcommit') missed to execute a cleanup routine which destroys a
reference to the active block operation -- resulting in the error you're
seeing when you attempted to 'abort' the block operation manually.
This bug is fixed in libvirt-1.2.8 and above. I see you're using
libvirt-1.2.7, if you can update libvirt in your environment, that
should fix your issue.
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1135169 -- blockcopy job
was cancel by "CTRL+C" while it show there still be one block job in
background
--
/kashyap