Apparently there's an issue with migration when virtio-blk is in use at the time migration occurs.
See Debian bug #580649 for details: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580649 In short: 2.6.26 (guest) + 0.12.3 + virtio-blk fails. 2.6.32 guest works, 0.11 works, non-virtio-blk works. Debian qemu-kvm is compiled without --enable-iothread - JFYI. The bugreport contains a backtrace taken from guest. Now, one can say it's a bug in 2.6.26 kernel, which is quite old. But the problem does not occur with qemu-kvm-0.11, so it might be treated as a regression instead. Thanks! /mjt -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
