Description of problem: After creating an external snapshot with the goal of performing live VM backups, blockcommit fails with "error: block copy still active: disk 'vda' already in active block job". Since this has happened only with Windows VMs (win2k12) until now, I cannot say with certainty if it affects other guest operating systems too. The VMs in question have qemu-guest-agent installed and running, all (stable) virtio drivers are installed, disk image format is qcow2, disk caching is set to none and backing storage is a distributed filesystem (MooseFS). Version-Release number of selected component (if applicable): libvirt 1.2.18.3 QEMU 2.4.1 How reproducible: 60% Steps to Reproduce: 1. virsh # snapshot-create-as --domain XYZ --no-metadata --disk-only --atomic --quiesce 2. virsh # blockcommit --domain XYZ vda --active --pivot --verbose Actual results: 1. Domain snapshot 1464895920 created 2. error: block copy still active: disk 'vda' already in active block job Expected results: 1. Domain snapshot 1464895920 created 2. Block Commit: [100 %] Successfully pivoted Additional info: virsh # blockjob --domain XYZ vda Active Block Commit: [100 %]
Do you still get the error if you drop --quiesce? I'm curious if it's due to some interaction with qemu-guest-agent... temporarily uninstalling the guest agent will be the authoritative way to remove that element from the equation. Another thing to try: enable fedora-virt-preview repo, then try updating libvirt and see if it reproduces, and if so, try updating qemu. Maybe that will tell us if it's already fixed upstream, and where the culprit lies https://fedoraproject.org/wiki/Virtualization_Preview_Repository
I first got this error when I was not using --quiesce. Later, I decided to add --quiesce (and setup qemu-guest-agent) hoping that the error would go away. Unfortunately it didn't. I am afraid that trying the fedora-virt-preview repo is out of the question due to the fact that this is our production KVM cluster and I currently have no spare machines for testing.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Closing this, since it has lingered for a while and F23 is almost out of support. If anyone can reproduce with f24+, please reopen