From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgCyy-00033C-1E for qemu-devel@nongnu.org; Wed, 26 Aug 2009 03:31:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgCys-00031D-Hm for qemu-devel@nongnu.org; Wed, 26 Aug 2009 03:31:46 -0400 Received: from [199.232.76.173] (port=57775 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgCys-00031A-7k for qemu-devel@nongnu.org; Wed, 26 Aug 2009 03:31:42 -0400 Received: from mx20.gnu.org ([199.232.41.8]:5290) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgCyr-0005Ep-Rn for qemu-devel@nongnu.org; Wed, 26 Aug 2009 03:31:42 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgCyq-0001Yw-7m for qemu-devel@nongnu.org; Wed, 26 Aug 2009 03:31:40 -0400 Message-ID: <4A94E4CE.4020903@web.de> Date: Wed, 26 Aug 2009 09:31:26 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <48A297F0.9000700@web.de> <48A8574B.6010704@web.de> <4A938B26.5040609@web.de> <4A93D986.4060206@web.de> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8AF40336E7ADC3921ED57CED" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: Breakage with local APIC routing List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Johannes Schindelin Cc: qemu-devel@nongnu.org, Avi Kivity This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8AF40336E7ADC3921ED57CED Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Johannes Schindelin wrote: > Hi, >=20 > On Tue, 25 Aug 2009, Jan Kiszka wrote: >=20 >> Johannes Schindelin wrote: >> >>> On Tue, 25 Aug 2009, Jan Kiszka wrote: >>> >>>> Johannes Schindelin wrote: >>>> >>>>> 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= =20 >>>>>>>>> used, which was no better than Subversion) installation of win6= 4=20 >>>>>>>>> is broken in QEmu. The commit message reads like this: >>>>>>>>> >>>>>>>>> Don't route PIC interrupts through the local APIC if the local= =20 >>>>>>>>> APIC config says so. By Ari Kivity. >>>>>>>> I recalled some earlier post on this which claimed to fix the is= sue=20 >>>>>>>> and found it in the archive: >>>>>>>> >>>>>>>> http://permalink.gmane.org/gmane.comp.emulators.qemu/25415 >>>>>>> I tried this, and it changes the symptoms, indeed. Instead of an= =20 >>>>>>> endless loop, it results in a bluescreen. >>>>>>> >>>>>>> As the OP said that it worked for him, I guess it is either in=20 >>>>>>> commits that came after his post, or in my add-on patches. >>>>>> So we are likely on the wrong path. Maybe we have to understand wh= at >>>>>> happens here first... >>>>>> >>>>>>> Hopefully I will find some time to work more on this bug. >>>>>> Would be interesting to know >>>>>> - if pic_irq_request is continuously called or if it stops when w= indows=20 >>>>>> hangs >>>>>> - what IRQ vectors are delivered >>>>>> - in what state the apic is, namely the s->lvt[APIC_LVT_LINT0] >>>>> Sorry for the long delay. I just don't have time to take care of t= he=20 >>>>> issue, but I quickly verified that it still does not work, with aa0= cba4=20 >>>>> (Aug 13 2009). >>>>> >>>>> If you are still interested in this issue, could you give me a hint= =20 >>>>> _where_ I should output _which_ values? I'll gladly take time for = that=20 >>>>> 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 c= ase >>>> more precisely: What version of Windows are you trying to install? >>> As far as I remember, it is a plain version of 64-bit XP Pro. (Maybe= it=20 >>> is a custom .iso for my day-job, but I think this is not the case). >>> >>>> What is your qemu command line? >>> test -h pc-bios/keymaps || ln -s ../keymaps pc-bios/ >>> >>> ./x86_64-softmmu/qemu-system-x86_64 \ >>> -L pc-bios/ \ >>> -m 1024 \ >>> -monitor stdio \ >>> -k en-us \ >>> -hda w64.img \ >>> -cdrom en_win_xp_pro_x64bit.iso \ >>> -fda fat:fat \ >>> -boot d \ >>> -net none \ >>> -localtime >>> >>>> Where does the installation fail? >>> "Setup is starting Windows". (Just after "Setup is loading files (...= )"=20 >>> phase.) >>> >>>> Are there specific steps required during the installation to reprodu= ce=20 >>>> the problem? >>> You need a 64-bit XP Pro, then call the command line as I did. It ha= ngs=20 >>> at >>> >>> (qemu) info cpus >>> * CPU #0: pc=3D0xfffff800010cabeb >>> >>> This is 100% reproducible. >>> >>>> And one more question: Did you check that you were using the=20 >>>> corresponding BIOS to aa0cba4? >>> Yes, I always use -L pc-bios/ in the same Git working directory, and = I=20 >>> just verified that indeed, the source is clean. >>> >>> A tiny, gentle reminder: the revision which is now available as 0e21e= 12b=20 >>> introduced this particular breakage. >> OK, just found some 64-bit Windows ISO (Server 2003) that also makes n= o >> progress at the point you described. Will play with it later today, >> specifically with the LAPIC changes you referred to. >=20 > Thank you very much! >=20 > If you need me to test something, just let me know; I'll try to squeeze= =20 > that into my time schedule. Very strange problem: I managed to get past this "Setup is starting Windows", but only when using KVM mode (both -enable-kvm from upstream as well as w/ or w/o -no-kvm-irqchip from qemu-kvm). It still takes ages (several minutes), but it works. The version before the commit you pointed out does not take so much time for this step. So we may see two issues here: some x86 emulation problem in TCG mode plus some IRQ delivery incorrectness. Did anyone here recently try to install XP-64 (desktop or server) into qemu or qemu-kvm recently? Can you confirm long delays or hangs during "Setup is starting Windows" (early text-mode installer)? Jan --------------enig8AF40336E7ADC3921ED57CED Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkqU5NMACgkQniDOoMHTA+mhPwCggIC1M8OlKelDqRypwrxtCEz+ aQ4An1yftkW6NoP1Xg+UzMkIo2/DeX0x =fz6d -----END PGP SIGNATURE----- --------------enig8AF40336E7ADC3921ED57CED--