From: Alex Williamson <alex.williamson@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] is it just me or is ne2k broken in qemu?
Date: Fri, 15 Apr 2011 08:17:21 -0600 [thread overview]
Message-ID: <1302877041.3110.26.camel@x201> (raw)
In-Reply-To: <4DA6B0E8.2050608@msgid.tls.msk.ru>
On Thu, 2011-04-14 at 12:31 +0400, Michael Tokarev wrote:
> I performed several tests of various emulated NICs
> booting with iPXE, and discovered that ne2k_pci (*)
> emulated device does not quite work, for quite some
> time already, at least with linux guests.
>
> The NIC works for a while, but after a few packets,
> or a few 1000s of packets, it stalls. In tcpdump
> on the host I see many ARP requests coming from the
> guest and each has corresponding ARP reply, but
> nothing is actually reaching the guest.
>
> This behavour is consistent since qemu-kvm 0.12,
> and is demonstrated by guest kernel 2.6.32 and
> 2.6.38, either 32 or 64bit.
>
> Anyone seen something similar?
For testing the iPXE ROMs I booted up each NIC, including ne2k_pci, to a
network loaded kernel (~4M) and installation initrd (~8M). I stopped
the test at the point where the installer kernel was able to
successfully DHCP with the boot NIC. ne2k_pci was definitely the
slowest of the cards at loading the images, but I didn't notice any
functionality issues. Maybe I didn't let it run long enough, but the
boot ROM seems ok with it.
Alex
next prev parent reply other threads:[~2011-04-15 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 8:31 [Qemu-devel] is it just me or is ne2k broken in qemu? Michael Tokarev
2011-04-14 12:29 ` Mulyadi Santosa
2011-04-15 14:17 ` Alex Williamson [this message]
2011-04-16 20:37 ` Michael Tokarev
2011-04-26 19:26 ` Luiz Capitulino
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=1302877041.3110.26.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=mjt@tls.msk.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.