Am Donnerstag, 18. Oktober 2012, 18:05:39 schrieb Avi Kivity: > On 10/18/2012 05:50 PM, Guido Winkelmann wrote: > > Am Mittwoch, 17. Oktober 2012, 13:25:45 schrieb Brian Jackson: > >> On Wednesday, October 17, 2012 10:45:14 AM Guido Winkelmann wrote: > >> > vda1, logical block 1858771 > >> > Oct 17 17:12:04 localhost kernel: [ 212.070600] Buffer I/O error on > >> > device > >> > vda1, logical block 1858772 > >> > Oct 17 17:12:04 localhost kernel: [ 212.070602] Buffer I/O error on > >> > device > >> > vda1, logical block 1858773 > >> > Oct 17 17:12:04 localhost kernel: [ 212.070605] Buffer I/O error on > >> > device > >> > vda1, logical block 1858774 > >> > Oct 17 17:12:04 localhost kernel: [ 212.070607] Buffer I/O error on > >> > device > >> > vda1, logical block 1858775 > >> > Oct 17 17:12:04 localhost kernel: [ 212.070610] Buffer I/O error on > >> > device > >> > vda1, logical block 1858776 > >> > Oct 17 17:12:04 localhost kernel: [ 212.070612] Buffer I/O error on > >> > device > >> > vda1, logical block 1858777 > >> > Oct 17 17:12:04 localhost kernel: [ 212.070615] Buffer I/O error on > >> > device > >> > vda1, logical block 1858778 > >> > Oct 17 17:12:04 localhost kernel: [ 212.070617] Buffer I/O error on > >> > device > >> > vda1, logical block 1858779 > >> > > >> > (I was writing a large file at the time, to make sure I actually catch > >> > I/O > >> > errors as they happen) > >> > >> What about newer versions of qemu/kvm? But of course if those work, your > >> next task is going to be git bisect it or file a bug with your distro > >> that > >> is using an ancient version of qemu/kvm. > > > > I've just upgraded both hosts to qemu-kvm 1.2.0 > > (qemu-1.2.0-14.fc17.x86_64, > > built from spec files under http://pkgs.fedoraproject.org/cgit/qemu.git/). > > > > The bug is still there. > > If you let the guest go idle (no I/O), then migrate it, then restart the > I/O, do the errors show? Just tested - yes, they do. Guido -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html