From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] net: Next steps to deprecate -net
Date: Fri, 17 Jul 2015 09:48:34 +0200 [thread overview]
Message-ID: <55A8B352.2090605@redhat.com> (raw)
In-Reply-To: <CAFEAcA_y1eF9HA52r1EJj7L70CLajF7Ybpeu3sHBozpC=D7tWA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
On 07/17/2015 09:25 AM, Peter Maydell wrote:
> On 17 July 2015 at 07:53, Thomas Huth <thuth@redhat.com> wrote:
>> Ok, assuming that my "Network traffic dumping for -netdev devices" patch
>> series is going to solve the dumping-for-netdev problem, how do we
>> tackle the remaining problems that we have to solve before we can
>> deprecate -net? Does anybody have a survey of the (onboard) NICs that
>> can only be configured with -net but not with -device? Could they
>> nowadays be changed to work with -device, too, or are there still major
>> obstacles to solve first?
>
> The problem is that "-device" says "create a new device and
> configure it like this". But onboard NICs are created by
> the board, so we want let the user say how to configure
> those devices, not create new ones...
Ok, I see ... maybe it makes sense to simply keep "-net nic" to be able
to configure the default/onboard NIC, and only to remove all the other
-net options instead ("-net user" etc.). The disliked vlan/hub concept
could then be removed, too, since "-net nic" can be used together with
"-netdev" nowadays by using something like "-net nic,netdev=xxx" as far
as I know. That would clean up most points of confusion, I think, and
would not cause too much code churn for the onboard NICs. Does that
sound feasible?
Thomas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-07-17 7:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 19:22 [Qemu-devel] [RFC PATCH] net: Enable vlans and dump for -netdev, too, Thomas Huth
2015-05-22 19:42 ` Eric Blake
2015-05-26 12:52 ` Stefan Hajnoczi
2015-05-26 13:07 ` Thomas Huth
2015-05-26 18:25 ` Paolo Bonzini
2015-05-26 14:29 ` Markus Armbruster
2015-05-26 14:36 ` Daniel P. Berrange
2015-05-26 16:43 ` Stefan Hajnoczi
2015-05-26 18:15 ` Thomas Huth
2015-05-27 7:22 ` Markus Armbruster
2015-07-17 6:53 ` [Qemu-devel] net: Next steps to deprecate -net (was: [RFC PATCH] Enable vlans and dump for -netdev, too) Thomas Huth
2015-07-17 7:25 ` Peter Maydell
2015-07-17 7:48 ` Thomas Huth [this message]
2015-07-22 13:40 ` [Qemu-devel] net: Next steps to deprecate -net Markus Armbruster
2015-07-22 16:20 ` Michael S. Tsirkin
2015-07-22 16:45 ` Thomas Huth
2015-07-17 8:16 ` [Qemu-devel] net: Next steps to deprecate -net (was: [RFC PATCH] Enable vlans and dump for -netdev, too) Stefan Hajnoczi
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=55A8B352.2090605@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).