So really this is an issue with lvm + libvirt but I'm not sure if its the fault of libvirt or lvm. libvirt is never receiving a failure from lvm as far as running commands. So I think its on the lvm side. The device nodes created are: lrwxrwxrwx 1 root root 7 Aug 14 10:09 build--bot-testslave.img -> ../dm-0 lrwxrwxrwx 1 root root 7 Aug 14 10:09 build--bot-testslave.img-cow -> ../dm-3 lrwxrwxrwx 1 root root 7 Aug 14 10:09 build--bot-testslave.img_vorigin -> ../dm-1 lrwxrwxrwx 1 root root 7 Aug 14 10:09 build--bot-testslave.img_vorigin-real -> ../dm-2 # lvdisplay /dev/build-bot/testslave.img /dev/build-bot/testslave.img: read failed after 0 of 4096 at 26843480064: Input/output error /dev/build-bot/testslave.img: read failed after 0 of 4096 at 26843537408: Input/output error /dev/build-bot/testslave.img: read failed after 0 of 4096 at 0: Input/output error /dev/build-bot/testslave.img: read failed after 0 of 4096 at 4096: Input/output error --- Logical volume --- LV Path /dev/build-bot/testslave.img LV Name testslave.img VG Name build-bot LV UUID iUsDpH-ZpJE-JkNz-wTeE-weoq-cf2d-3jRgiu LV Write Access read/write LV Creation host, time roids, 2013-08-14 10:09:26 -0500 LV snapshot status INACTIVE destination for testslave.img_vorigin LV Status available # open 1 LV Size 25.00 GiB Current LE 6400 COW-table size 4.00 MiB COW-table LE 1 Snapshot chunk size 4.00 KiB Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 Any attempts by QEMU to write to this device results in QEMU hanging indefinitely. It appears libvirt is creating this logical volume with: lvcreate --name testslave.img -L 4096K --virtualsize 26214400K I could have switched those arguments. Its possible its also passing a -s but I'm not sure what the path would be. maybe /dev/build-bot/testslave.img-cow ? or /dev/build-bot/testslave.img_vorigin
Try 2.02.100 which is now in Portage. I believe it's the next stabilization target if everything goes okay. Backporting patches to 2.02.97 to keep it feasible is... well... not feasible.
Cardoe: reping
Yep. This is good.
