qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Fleytman <dmitry.fleytman@ravellosystems.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Alex Fishman <alex.fishman@ravellosystems.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	yvugenfi@redhat.com, Izik Eidus <izik.eidus@ravellosystems.com>,
	qemu-devel@nongnu.org, Dmitry Fleytman <dmitry@daynix.com>,
	Yan Vugenfirer <yan@daynix.com>
Subject: Re: [Qemu-devel] [PATCH v2] VMXNET3 paravirtual NIC device implementation
Date: Thu, 1 Mar 2012 15:31:15 +0200	[thread overview]
Message-ID: <CAOMtbakYLgMkCY_K33PgVsiroh6jrN4FGfch3dQ04ajHBxrx_A@mail.gmail.com> (raw)
In-Reply-To: <4F4F6221.2050406@msgid.tls.msk.ru>

On Thu, Mar 1, 2012 at 1:48 PM, Michael Tokarev <mjt@tls.msk.ru> wrote:
>
> On 29.02.2012 16:49, Dmitry Fleytman wrote:
>
> > Implementation of VMWare VMXNET3 paravirtual NIC device.
> > Supports of all the device features including offload capabilties,
> > VLANs and etc.
> [..]
>
> Not a review or anything (I don't know qemu networking
> internals much), just a question: does it support PXE
> booting?
>
> There appears to be an etherboot/iPXE boot rom for it, maybe
> it is  a good idea to enable pxe in this "anti-driver" too?

Hello, Michael
Thanks for your suggestion.

Boot from this device is not supported in this version.
Indeed this could be useful, we'll consider adding this feature in the future.

>
> Thanks,
>
> /mjt

  reply	other threads:[~2012-03-01 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 12:49 [Qemu-devel] [PATCH v2] VMXNET3 paravirtual NIC device implementation Dmitry Fleytman
2012-03-01 11:48 ` Michael Tokarev
2012-03-01 13:31   ` Dmitry Fleytman [this message]
2012-03-03 16:55 ` Gerhard Wiesinger
2012-03-04 17:09   ` 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=CAOMtbakYLgMkCY_K33PgVsiroh6jrN4FGfch3dQ04ajHBxrx_A@mail.gmail.com \
    --to=dmitry.fleytman@ravellosystems.com \
    --cc=alex.fishman@ravellosystems.com \
    --cc=dmitry@daynix.com \
    --cc=izik.eidus@ravellosystems.com \
    --cc=mjt@tls.msk.ru \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yan@daynix.com \
    --cc=yvugenfi@redhat.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).