From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MfyRO-0005uc-SL for qemu-devel@nongnu.org; Tue, 25 Aug 2009 12:00:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MfyRJ-0005r7-TS for qemu-devel@nongnu.org; Tue, 25 Aug 2009 12:00:09 -0400 Received: from [199.232.76.173] (port=35778 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MfyRJ-0005qy-Fo for qemu-devel@nongnu.org; Tue, 25 Aug 2009 12:00:05 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57891) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MfyRI-0000e6-C3 for qemu-devel@nongnu.org; Tue, 25 Aug 2009 12:00:04 -0400 Message-ID: <4A940A80.2090902@redhat.com> Date: Tue, 25 Aug 2009 19:00:00 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 1/1] Make the e1000 the default network adapter for the pc target. References: <1250267001-4431-1-git-send-email-aliguori@us.ibm.com> <4A93C0C4.7060409@redhat.com> <20090825132347.GB23700@csclub.uwaterloo.ca> <4A93E875.9030204@us.ibm.com> In-Reply-To: <4A93E875.9030204@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, Lennart Sorensen On 08/25/2009 04:34 PM, Anthony Liguori wrote: > Lennart Sorensen wrote: >> On Tue, Aug 25, 2009 at 01:45:24PM +0300, Avi Kivity wrote: >>> I am unable to get Windows XP to work with the e1000 device, either >>> with its built-in drivers or with Windows Update. I think it's >>> better to switch to rtl8139 (qemu-kvm's default for years now). >> >> It used to not work with win2003 as well, but I thought someone recently >> fixed the bug that caused that to happen. >> >> I use e1000 with win xp, although win xp has no driver at all for the >> e1000 and requires you to download the intel driver and install that. >> The intel driver also made win 2003 work before even though the >> microsoft >> supplied driver did not work. > > That seems to conflict with what Avi suggested (that there's a > built-in driver). > I misreported it, Windows does not find a driver either in media or in Windows Update. -- error compiling committee.c: too many arguments to function