From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:33706) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TKxt9-00071r-Dw for qemu-devel@nongnu.org; Sun, 07 Oct 2012 16:55:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TKxt7-0006y7-Ke for qemu-devel@nongnu.org; Sun, 07 Oct 2012 16:55:51 -0400 Received: from mout.web.de ([212.227.17.11]:56943) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TKxt7-0006y0-A6 for qemu-devel@nongnu.org; Sun, 07 Oct 2012 16:55:49 -0400 Message-ID: <5071EC4E.7050308@web.de> Date: Sun, 07 Oct 2012 22:55:42 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <5071BAE5.1060003@web.de> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig349669F7DFC3A078874BEBCF" Subject: Re: [Qemu-devel] Win2k broken by kvmvapic List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: Avi Kivity , qemu-devel This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig349669F7DFC3A078874BEBCF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2012-10-07 20:40, Blue Swirl wrote: > On Sun, Oct 7, 2012 at 5:24 PM, Jan Kiszka wrote: >> On 2012-10-07 17:23, Blue Swirl wrote: >>> Hi, >>> >>> Win2k does not work in HEAD, it resets the machine. I bisected this t= o >>> 0b57e287138728f72d88b06e69b970c5d745c44a, but that does not look so >>> buggy. >>> >>> Digging deeper, the problem is introduced by kvmvapic: >>> Breakpoint 1, cpu_physical_memory_write_rom (addr=3D0xca300, >>> buf=3D0x7fffec66b500 "", len=3D0x5) at /src/qemu/exec.c:3536 >>> 3536 invalidate_and_set_dirty(addr1, l); >>> (gdb) bt >>> #0 cpu_physical_memory_write_rom (addr=3D0xca300, buf=3D0x7fffec66b5= 00 "", >>> len=3D0x5) at /src/qemu/exec.c:3536 >>> #1 0x0000000000644089 in apic_sync_vapic (s=3D0x1a6ba60, sync_type=3D= 0x2) >>> at /src/qemu/hw/i386/../apic.c:132 >>> >>> It looks like vapic is enabled even with KVM disabled >> >> Which is intentional. The VAPIC is provided in a KVM-independent way t= o >> the guest. Used to work fine with XP, but I never had my finger on a 2= k >> version. >> >>> and this causes >>> chaos. With -global apic.vapic=3Dfalse Win2k works. >> >> And that means we have a bug somewhere. Can you specify the chaos you >> see in more details? Does your Win2k boot with KVM (and kvmvapic)? >=20 > It works with KVM both with and without kvmvapic. There are these > error messages though: > (qemu) Invalid write to memory region kvm-pic > Invalid write to memory region kvm-pic Weird, that's a PIO region. And the KVM kernel module should catch all accesses. >=20 > Here's 'info mtree' output, kvmvapic-rom line may be interesting: >=20 > memory > 0000000000000000-7ffffffffffffffe (prio 0, RW): system > 0000000000000000-000000000fffffff (prio 0, RW): alias ram-below-4g > @pc.ram 0000000000000000-000000000fffffff > 00000000000a0000-00000000000bffff (prio 1, RW): alias smram-region > @pci 00000000000a0000-00000000000bffff > 00000000000c0000-00000000000c3fff (prio 1, R-): alias pam-rom > @pc.ram 00000000000c0000-00000000000c3fff > 00000000000c4000-00000000000c7fff (prio 1, R-): alias pam-rom > @pc.ram 00000000000c4000-00000000000c7fff > 00000000000c8000-00000000000cbfff (prio 1, R-): alias pam-rom > @pc.ram 00000000000c8000-00000000000cbfff > 00000000000ca000-00000000000ccfff (prio 1000, RW): alias > kvmvapic-rom @pc.ram 00000000000ca000-00000000000ccfff Looks ok - it's kind of an option ROM. Guess I need to dig for a Win2k CD... Jan --------------enig349669F7DFC3A078874BEBCF 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.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBx7FEACgkQitSsb3rl5xTGywCeNQsIppDMVYfEiWdUm5INh6aZ e+cAnA4a1MO3xOaq+lXY+PtvvALbk9l0 =iWjp -----END PGP SIGNATURE----- --------------enig349669F7DFC3A078874BEBCF--