From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: winXP "Standard PC" HAL and qemu-kvm >= 0.15 Date: Tue, 06 Dec 2011 20:57:46 +0400 Message-ID: <4EDE498A.2040309@msgid.tls.msk.ru> References: <4EDC8D06.20308@msgid.tls.msk.ru> <4EDCC6FE.8040702@redhat.com> <4EDD2763.8010808@msgid.tls.msk.ru> <4EDDEF26.9030403@redhat.com> <4EDDF659.6040701@msgid.tls.msk.ru> <20111206122752.GA31385@redhat.com> <4EDE2AA0.7090001@msgid.tls.msk.ru> <4EDE42EB.2020101@msgid.tls.msk.ru> <4EDE450B.6090801@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "qemu-devel@nongnu.org" , Isaku Yamahata , Avi Kivity , KVM list , "Michael S. Tsirkin" To: Jan Kiszka Return-path: Received: from isrv.corpit.ru ([86.62.121.231]:60223 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751603Ab1LFQ5s (ORCPT ); Tue, 6 Dec 2011 11:57:48 -0500 In-Reply-To: <4EDE450B.6090801@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06.12.2011 20:38, Jan Kiszka wrote: > On 2011-12-06 17:29, Michael Tokarev wrote: [] >> It appears there are two issues here, one is fixed by >> 09de0f469c3c2a277c7874f6c60992c8b94719a9 and is 32bit-only, and >> another bisect leads to this commit: Or 3... :) >> commit 59539c913383fdd3350681301b44f02fa7ee2757 >> Author: Jan Kiszka >> Date: Mon Jun 27 12:22:28 2011 +0200 >> >> qemu-kvm: Fix in-kernel PIC reset [] >> Anything wrong with this patch? > > I tend to say "no". It may just reveals some issue elsewhere. > > To cross-check: Does this series [1] expose the same issue with vanilla > QEMU when enabling that in-kernel irqchip version? I cross-checked it the other way, which really should have been done at the very beginning instead of wasting so much time of so many people at once. I just tried qemu-kvm-1.0, which I wasn't due to an unrelated issue (1.0 does not work for me in my funky 32/64bit environment). Also, since the bug has been reported especially against 0.15 version (triggering by upgrading from 0.14 to 0.15), I didn't insist on trying 1.0, which was my biggest mistake. And in qemu-kvm-1.0, the problem guest Just Works. So i t must be something else which were fixed between 0.15 and 1.0. Upstream qemu 1.0 does not have this issue too. > [1] http://thread.gmane.org/gmane.comp.emulators.kvm.devel/82871 I'll try to verify this series in a moment, but hopefully it will work fine too :) Thanks! /mjt From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:60405) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXyKz-0002jP-PQ for qemu-devel@nongnu.org; Tue, 06 Dec 2011 11:57:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RXyKy-0004CU-LV for qemu-devel@nongnu.org; Tue, 06 Dec 2011 11:57:49 -0500 Received: from isrv.corpit.ru ([86.62.121.231]:55708) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXyKy-0004CN-EF for qemu-devel@nongnu.org; Tue, 06 Dec 2011 11:57:48 -0500 Message-ID: <4EDE498A.2040309@msgid.tls.msk.ru> Date: Tue, 06 Dec 2011 20:57:46 +0400 From: Michael Tokarev MIME-Version: 1.0 References: <4EDC8D06.20308@msgid.tls.msk.ru> <4EDCC6FE.8040702@redhat.com> <4EDD2763.8010808@msgid.tls.msk.ru> <4EDDEF26.9030403@redhat.com> <4EDDF659.6040701@msgid.tls.msk.ru> <20111206122752.GA31385@redhat.com> <4EDE2AA0.7090001@msgid.tls.msk.ru> <4EDE42EB.2020101@msgid.tls.msk.ru> <4EDE450B.6090801@siemens.com> In-Reply-To: <4EDE450B.6090801@siemens.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] winXP "Standard PC" HAL and qemu-kvm >= 0.15 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Isaku Yamahata , "Michael S. Tsirkin" , "qemu-devel@nongnu.org" , KVM list , Avi Kivity On 06.12.2011 20:38, Jan Kiszka wrote: > On 2011-12-06 17:29, Michael Tokarev wrote: [] >> It appears there are two issues here, one is fixed by >> 09de0f469c3c2a277c7874f6c60992c8b94719a9 and is 32bit-only, and >> another bisect leads to this commit: Or 3... :) >> commit 59539c913383fdd3350681301b44f02fa7ee2757 >> Author: Jan Kiszka >> Date: Mon Jun 27 12:22:28 2011 +0200 >> >> qemu-kvm: Fix in-kernel PIC reset [] >> Anything wrong with this patch? > > I tend to say "no". It may just reveals some issue elsewhere. > > To cross-check: Does this series [1] expose the same issue with vanilla > QEMU when enabling that in-kernel irqchip version? I cross-checked it the other way, which really should have been done at the very beginning instead of wasting so much time of so many people at once. I just tried qemu-kvm-1.0, which I wasn't due to an unrelated issue (1.0 does not work for me in my funky 32/64bit environment). Also, since the bug has been reported especially against 0.15 version (triggering by upgrading from 0.14 to 0.15), I didn't insist on trying 1.0, which was my biggest mistake. And in qemu-kvm-1.0, the problem guest Just Works. So i t must be something else which were fixed between 0.15 and 1.0. Upstream qemu 1.0 does not have this issue too. > [1] http://thread.gmane.org/gmane.comp.emulators.kvm.devel/82871 I'll try to verify this series in a moment, but hopefully it will work fine too :) Thanks! /mjt