From: Stefan Weil <weil@mail.berlios.de>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] Make the e1000 the default network adapter for the pc target.
Date: Tue, 25 Aug 2009 15:51:34 +0200 [thread overview]
Message-ID: <4A93EC66.7010000@mail.berlios.de> (raw)
In-Reply-To: <4A93C0C4.7060409@redhat.com>
Avi Kivity schrieb:
> On 08/14/2009 07:23 PM, Anthony Liguori wrote:
>> The ne2k is an ancient card that performs pretty terribly under
>> QEMU. In many
>> modern OSes, there is no longer drivers available for the ne2k.
>>
>> Switch the default network adapter to e1000. This card is more widely
>> suppported and performs rather well under QEMU. There may be very
>> old OSes
>> that had a ne2k driver but not an e1000 driver but I think this is
>> likely the
>> exception.
>>
>> I think the average user is better served with an e1000 vs ne2k.
>>
>
> 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).
>
Hi
rtl8139 did not work on big endian hosts: link was down in linux guests.
For kvm on little endian hosts, this did not matter.
The only adapter working in any combination of host / guest endianess
was pcnet (which had the lowest performance under QEMU).
My tests are rather old (2007-09-15), so maybe this was fixed later.
And of course, e1000 was added after my tests, so I assume it is
well programmed and passes endianess tests. Did anybody check this?
Today, my latest eepro100 (e100) emulation also passes all endianess
tests, but it still does not work with any Windows OS. This might
change with the patches published recently.
Regards
Stefan
PS. For endianess tests with 32 and 64 bit, QEMU's mips emulation
was very helpful. Without mips host support, this test environment
is no longer working. This is the main reason why I have no newer
test results.
prev parent reply other threads:[~2009-08-25 13:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 16:23 [Qemu-devel] [PATCH 1/1] Make the e1000 the default network adapter for the pc target Anthony Liguori
2009-08-15 21:58 ` [Qemu-devel] Re: [PATCH 1/1] Make the e1000 the default network adapterfor " Sebastian Herbszt
2009-08-17 10:34 ` [Qemu-devel] [PATCH 1/1] Make the e1000 the default network adapter for " Mark McLoughlin
2009-08-24 15:12 ` Anthony Liguori
2009-08-24 15:36 ` Gerd Hoffmann
2009-08-24 16:14 ` Anthony Liguori
2009-08-25 10:45 ` Avi Kivity
2009-08-25 12:39 ` Anthony Liguori
2009-08-25 15:55 ` Avi Kivity
2009-08-25 13:23 ` Lennart Sorensen
2009-08-25 13:34 ` Anthony Liguori
2009-08-25 14:23 ` Lennart Sorensen
2009-08-25 16:00 ` Avi Kivity
2009-08-25 15:58 ` Avi Kivity
2009-08-25 16:30 ` Lennart Sorensen
2009-08-25 16:39 ` Anthony Liguori
2009-08-25 16:56 ` Avi Kivity
2009-08-25 17:11 ` Lennart Sorensen
2009-08-25 17:13 ` Avi Kivity
2009-08-25 18:19 ` Anthony Liguori
2009-08-26 8:32 ` Avi Kivity
2009-08-25 17:28 ` Reimar Döffinger
2009-08-26 5:47 ` Amit Shah
2009-08-25 20:20 ` [Qemu-devel] " Bjørn Mork
2009-08-26 9:57 ` Avi Kivity
2009-08-25 13:51 ` Stefan Weil [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A93EC66.7010000@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).