I was able to block commit using libvirt, finally. Found the problem:
inaddy@(kvm02):~$ virsh snapshot-create-as --domain guest --disk-only --atomic
Domain snapshot 1487158333 created
Formatting '/var/lib/libvirt/images/guest.1487158333', fmt=qcow2
size=32212254720 backing_file='/var/lib/libvirt/images/guest.qcow2'
backing_fmt='qcow2' encryption=off cluster_size=65536 lazy_refcounts=off
inaddy@(kvm02):~$ virsh domblklist --domain guest
Target Source
------------------------------------------------
vda /var/lib/libvirt/images/guest.1487158333
inaddy@(kvm02):~$ virsh domblkinfo --domain guest --device
/var/lib/libvirt/images/guest.1487158333
Capacity: 32212254720
Allocation: 987136
Physical: 987136
inaddy@(kvm02):~$ virsh blockcommit --domain guest vda --base
/var/lib/libvirt/images/guest.qcow2 --top
/var/lib/libvirt/images/guest.1487158333 --wait --verbose
Block Commit: [100 %]
<VIRSH STUCKS HERE>
<in parallel>
inaddy@(kvm02):~$ virsh qemu-monitor-command guest --pretty -- '{ "execute":
"query-blockstats" }'
{
"return": [
{
"device": "drive-virtio-disk0",
"parent": {
"stats": {
"flush_total_time_ns": 0,
"wr_highest_offset": 1834496,
"wr_total_time_ns": 0,
"wr_bytes": 0,
"rd_total_time_ns": 0,
"flush_operations": 0,
"wr_operations": 0,
"rd_bytes": 0,
"rd_operations": 0
}
},
"stats": {
"flush_total_time_ns": 371338917,
"wr_highest_offset": 19362090496,
"wr_total_time_ns": 2418722218,
"wr_bytes": 434176,
"rd_total_time_ns": 18115039,
"flush_operations": 34,
"wr_operations": 76,
"rd_bytes": 385024,
"rd_operations": 63
},
"backing": {
"parent": {
"stats": {
"flush_total_time_ns": 0,
"wr_highest_offset": 5328862720,
"wr_total_time_ns": 0,
"wr_bytes": 0,
"rd_total_time_ns": 0,
"flush_operations": 0,
"wr_operations": 0,
"rd_bytes": 0,
"rd_operations": 0
}
},
"stats": {
"flush_total_time_ns": 42335832,
"wr_highest_offset": 23789047296,
"wr_total_time_ns": 82449902,
"wr_bytes": 926720,
"rd_total_time_ns": 318909795,
"flush_operations": 18,
"wr_operations": 90,
"rd_bytes": 62250496,
"rd_operations": 3336
}
}
},
{
"device": "drive-ide0-0-0",
"stats": {
"flush_total_time_ns": 0,
"wr_highest_offset": 0,
"wr_total_time_ns": 0,
"wr_bytes": 0,
"rd_total_time_ns": 284763,
"flush_operations": 0,
"wr_operations": 0,
"rd_bytes": 46,
"rd_operations": 2
}
}
],
"id": "libvirt-311"
}
inaddy@(kvm02):~$ virsh qemu-monitor-command guest --pretty -- '{ "execute":
"query-block-jobs" }'
{
"return": [
{
"io-status": "ok",
"device": "drive-virtio-disk0",
"busy": false,
"len": 32212254720,
"offset": 32212254720,
"paused": false,
"speed": 0,
"type": "commit"
}
],
"id": "libvirt-511"
}
inaddy@(kvm02):~$ virsh qemu-monitor-command guest --pretty -- '{ "execute":
"block-job-complete", "arguments": { "device": "drive-virtio-disk0" } }'
{
"return": {
},
"id": "libvirt-859"
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317491
Title:
virsh blockcommit hangs at 100%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1317491/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
