From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mfs29-0000on-LN for qemu-devel@nongnu.org; Tue, 25 Aug 2009 05:09:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mfs24-0000mw-D4 for qemu-devel@nongnu.org; Tue, 25 Aug 2009 05:09:40 -0400 Received: from [199.232.76.173] (port=58399 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mfs24-0000mq-7M for qemu-devel@nongnu.org; Tue, 25 Aug 2009 05:09:36 -0400 Received: from mail-bw0-f227.google.com ([209.85.218.227]:50084) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mfs23-0004iF-LP for qemu-devel@nongnu.org; Tue, 25 Aug 2009 05:09:36 -0400 Received: by bwz27 with SMTP id 27so2200800bwz.34 for ; Tue, 25 Aug 2009 02:09:34 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4A93A7EC.6090704@web.de> References: <48A297F0.9000700@web.de> <48A8574B.6010704@web.de> <4A938B26.5040609@web.de> <52d4a3890908250124g74e25441x262fc7926bfdbe36@mail.gmail.com> <4A93A7EC.6090704@web.de> Date: Tue, 25 Aug 2009 12:09:34 +0300 Message-ID: <52d4a3890908250209y76ecaf1tf68117635a03820d@mail.gmail.com> Subject: Re: [Qemu-devel] Re: Breakage with local APIC routing From: Mohammed Gamal Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Avi Kivity , qemu-devel@nongnu.org qemu-system-x86_64 -hda /dev/null -cdrom I was using qemu-kvm, but I assume that using -no-kvm would be equivalent to using plain qemu, no? On Tue, Aug 25, 2009 at 11:59 AM, Jan Kiszka wrote: > Mohammed Gamal wrote: >> On Tue, Aug 25, 2009 at 9:56 AM, Jan Kiszka wrote: >>> Johannes Schindelin wrote: >>>> Hi, >>>> >>>> On Sun, 17 Aug 2008, Jan Kiszka wrote: >>>> >>>>> Johannes Schindelin wrote: >>>>> >>>>>> On Wed, 13 Aug 2008, Jan Kiszka wrote: >>>>>> >>>>>>> Johannes Schindelin wrote: >>>>>>>> due to the change in revision 3371 (well, at that time, CVS was us= ed, >>>>>>>> which was no better than Subversion) installation of win64 is brok= en >>>>>>>> in QEmu. =A0The commit message reads like this: >>>>>>>> >>>>>>>> =A0 Don't route PIC interrupts through the local APIC if the local >>>>>>>> =A0 APIC config says so. By Ari Kivity. >>>>>>> I recalled some earlier post on this which claimed to fix the issue= and >>>>>>> found it in the archive: >>>>>>> >>>>>>> http://permalink.gmane.org/gmane.comp.emulators.qemu/25415 >>>>>> I tried this, and it changes the symptoms, indeed. =A0Instead of an = endless >>>>>> loop, it results in a bluescreen. >>>>>> >>>>>> As the OP said that it worked for him, I guess it is either in commi= ts >>>>>> that came after his post, or in my add-on patches. >>>>> So we are likely on the wrong path. Maybe we have to understand what >>>>> happens here first... >>>>> >>>>>> Hopefully I will find some time to work more on this bug. >>>>> Would be interesting to know >>>>> =A0- if pic_irq_request is continuously called or if it stops when wi= ndows >>>>> =A0 =A0hangs >>>>> =A0- what IRQ vectors are delivered >>>>> =A0- in what state the apic is, namely the s->lvt[APIC_LVT_LINT0] >>>> Sorry for the long delay. =A0I just don't have time to take care of th= e >>>> issue, but I quickly verified that it still does not work, with aa0cba= 4 >>>> (Aug 13 2009). >>>> >>>> If you are still interested in this issue, could you give me a hint >>>> _where_ I should output _which_ values? =A0I'll gladly take time for t= hat >>>> now. >>> If some OS does not properly install due to a possible emulation bug, I >>> am interested, for sure. Let's restart this by specifying the test case >>> more precisely: What version of Windows are you trying to install? What >>> is your qemu command line? Where does the installation fail? Are there >>> specific steps required during the installation to reproduce the proble= m? >>> >>> And one more question: Did you check that you were using the >>> corresponding BIOS to aa0cba4? >>> >>> Jan >>> >>> >> >> In case this is considered relevant. I am also facing a bug with >> installing amd64 version of ubuntu-9.04. I first thought it was a >> possible bug in KVM, but even when using -no-kvm the guest still hangs >> just when starting to load the kernel. > > Might be the same, might be a different issue. Same questions to you: > what is your command line, and are there specific steps required to > reproduce the issue? And I assume you also tried plain qemu, right? > > Jan > >