From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55427) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XKt3j-0002SD-S6 for qemu-devel@nongnu.org; Fri, 22 Aug 2014 13:55:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XKt3c-0004MJ-BY for qemu-devel@nongnu.org; Fri, 22 Aug 2014 13:55:31 -0400 Received: from mx1.redhat.com ([209.132.183.28]:30224) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XKt3b-0004Jk-Ve for qemu-devel@nongnu.org; Fri, 22 Aug 2014 13:55:24 -0400 Message-ID: <53F78403.6040207@redhat.com> Date: Fri, 22 Aug 2014 19:55:15 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <53D8DEE1.8080905@beyond.pl> <53D8F546.4010803@redhat.com> <53D96DBE.2040700@beyond.pl> <53DA283F.4030709@beyond.pl> <53DFB511.70700@beyond.pl> <53DFD158.3070203@redhat.com> <20140808213730.GA13545@amt.cnet> <688822096.25778377.1407566113211.JavaMail.zimbra@redhat.com> <53F62201.1050805@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] latest rc: virtio-blk hangs forever after migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andrey Korolyov Cc: Amit Shah , Fam Zheng , Marcelo Tosatti , =?UTF-8?B?TWFyY2luIEdpYnXFgmE=?= , "qemu-devel@nongnu.org" Il 22/08/2014 18:44, Andrey Korolyov ha scritto: >> >> I`m running 3.10, so patches are not here, will try 3.16 soon. Even if >> problem will be fixed, it still will be specific for 2.1, earlier >> releases working well and I`ll bisect at a time. > > Thanks, using 3.16 helped indeed. Though the bug remains as is at 2.1 > on LTS 3.10, should I find the breaking commit, or it is better to > backport kvm subsystem changes related to apic to 3.10? I think I'd suggest the latter. If the fix was brought by those ioapic patches, the bug has always been latent as far as I could see. I'm afraid that bisection would be pretty time consuming, also because the bug didn't reproduce 100% for me (and at some point stopped reproducing even on 3.10, causing some serious wtf...). Paolo