From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: migration fails with virtio-blk Date: Mon, 10 May 2010 22:57:57 +0400 Message-ID: <4BE85735.4000006@msgid.tls.msk.ru> References: <4BE7D695.9020002@msgid.tls.msk.ru> <4BE851BF.7060003@msgid.tls.msk.ru> <4BE8529B.90705@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list To: Anthony Liguori Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:32897 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755874Ab0EJS57 (ORCPT ); Mon, 10 May 2010 14:57:59 -0400 In-Reply-To: <4BE8529B.90705@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: 10.05.2010 22:38, Anthony Liguori wrote: > On 05/10/2010 01:34 PM, Michael Tokarev wrote: >>> In short: 2.6.26 (guest) + 0.12.3 + virtio-blk fails. >>> 2.6.32 guest works, 0.11 works, non-virtio-blk works. >> >> It looks like a problem reported on qemu-devel >> list should fix the issue here: >> http://marc.info/?l=qemu-devel&m=127350821419989 > > Can't be, that's a vhost patch and 0.12.3 doesn't support vhost. Well, that was really close. qemu-kvm-0.12 has the following code in that place: vdev->features = features; the patch mentioned has this: + if (vdev->set_features) + vdev->set_features(vdev, features); so basically kvm had the same code here, just not wrapped into a function ;) And sure thing you're right, it does not help any. :) Thanks! /mjt