From: Dmitry Fleytman <dmitry@daynix.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vmxnet3 iPXE compatibility
Date: Wed, 27 Mar 2013 18:56:15 +0200 [thread overview]
Message-ID: <CAGHCxhf82aZd834zCA5SApcb8HU599DeULOFmd_NHF8f=XtDEg@mail.gmail.com> (raw)
In-Reply-To: <CAJSP0QWUGn+63qruemfoV6yPnykavD7niXk7JEO+nR9VXZBb7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Hi Stefan,
The issue is we never tested this device with iPXE, so according to
Murphy's law it cannot work :).
We'll take a look...
Dmitry.
On Mon, Mar 25, 2013 at 2:26 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> Hi Dmitry,
> QEMU vmxnet3 produces the following warning with iPXE
> (77f64b11f764e721f4f8704b7b90317e52d85fc3):
>
> $ cd ~/ipxe/src
> $ make bin/vmxnet3.rom
> $ qemu-system-x86_64 -netdev user,id=netdev0 -device
> vmxnet3,netdev=netdev0,romfile=bin/vmxnet3.rom
> [vmxnet3][WR][vmxnet3_peer_has_vnet_hdr]: Peer has no virtio
> extension. Task offloads will be emulated.
> [vmxnet3][WR][vmxnet3_get_command_status]: Received request for
> unknown command: cafe0002
>
> The warning about virtio extensions is expected since I chose slirp
> networking.
>
> iPXE does not show the NIC ('ifstat' command). I guess the driver
> gave up during initialization:
>
> https://git.ipxe.org/ipxe.git/blob/HEAD:/src/drivers/net/vmxnet3.c#l613
>
> Any ideas?
>
> Stefan
>
> PS: I discovered this when testing net patches for the pull request I
> just sent out. It's not a blocker, so vmxnet3 will finally be in
> qemu.git/master very soon!
>
[-- Attachment #2: Type: text/html, Size: 1799 bytes --]
next prev parent reply other threads:[~2013-03-27 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 12:26 [Qemu-devel] vmxnet3 iPXE compatibility Stefan Hajnoczi
2013-03-27 16:56 ` Dmitry Fleytman [this message]
2013-03-28 8:42 ` Dmitry Fleytman
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='CAGHCxhf82aZd834zCA5SApcb8HU599DeULOFmd_NHF8f=XtDEg@mail.gmail.com' \
--to=dmitry@daynix.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).