root@ubuntu:~# virsh blockcommit testvm vda --active --verbose --pivot --wait
Block commit: [100 %]error: failed to pivot job for disk vda
error: block copy still active: disk 'vda' not ready for pivot yet
- Upgraded to proposed and tested again, and problem is gone:
The package is looking good. We have also asked the customer to install the test package and verify that it works under their workload. We might just wait for their confirmation before marking this as verified, in order to give this a little more time to soak in -proposed.
The following is verification performed by Fabio in a lab:
- Tested with the original libvirt to make sure I was able to reproduce:
root@ubuntu:~# apt-cache policy libvirt-bin archive. ubuntu. com/ubuntu xenial-updates/main amd64 Packages security. ubuntu. com/ubuntu xenial- security/ main amd64 Packages dpkg/status archive. ubuntu. com/ubuntu xenial/main amd64 Packages
libvirt-bin:
Installed: 1.3.1-1ubuntu10.27
Candidate: 1.3.1-1ubuntu10.27
Version table:
*** 1.3.1-1ubuntu10.27 500
500 http://
500 http://
100 /var/lib/
1.3.1-1ubuntu10 500
500 http://
root@ubuntu:~# virsh blockcommit testvm vda --active --verbose --pivot --wait
Block commit: [100 %]error: failed to pivot job for disk vda
error: block copy still active: disk 'vda' not ready for pivot yet
- Upgraded to proposed and tested again, and problem is gone:
root@ubuntu:~# apt-cache policy libvirt-bin archive. ubuntu. com/ubuntu xenial- proposed/ main amd64 Packages dpkg/status archive. ubuntu. com/ubuntu xenial-updates/main amd64 Packages security. ubuntu. com/ubuntu xenial- security/ main amd64 Packages archive. ubuntu. com/ubuntu xenial/main amd64 Packages
libvirt-bin:
Installed: 1.3.1-1ubuntu10.29
Candidate: 1.3.1-1ubuntu10.29
Version table:
*** 1.3.1-1ubuntu10.29 500
500 http://
100 /var/lib/
1.3.1-1ubuntu10.27 500
500 http://
500 http://
1.3.1-1ubuntu10 500
500 http://
root@ubuntu:~# virsh blockcommit testvm vda --active --verbose --pivot --wait
Block commit: [100 %]
Successfully pivoted
End of test by Fabio.
The package is looking good. We have also asked the customer to install the test package and verify that it works under their workload. We might just wait for their confirmation before marking this as verified, in order to give this a little more time to soak in -proposed.
Will update again soon.