From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: migration fails with virtio-blk Date: Mon, 10 May 2010 13:49:09 +0400 Message-ID: <4BE7D695.9020002@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: KVM list Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:49340 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756247Ab0EJJtL (ORCPT ); Mon, 10 May 2010 05:49:11 -0400 Sender: kvm-owner@vger.kernel.org List-ID: 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