From: Stefan Hajnoczi <stefanha@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] net: Next steps to deprecate -net (was: [RFC PATCH] Enable vlans and dump for -netdev, too)
Date: Fri, 17 Jul 2015 09:16:25 +0100 [thread overview]
Message-ID: <20150717081625.GA16079@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <55A8A654.5070003@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1935 bytes --]
On Fri, Jul 17, 2015 at 08:53:08AM +0200, Thomas Huth wrote:
> On 05/26/2015 04:29 PM, Markus Armbruster wrote:
> > Stefan Hajnoczi <stefanha@redhat.com> writes:
> [...]
> >> We thought the QEMU "vlan" concept would be dropped completely in the
> >> future, so it was never added to -netdev. No patches to do that have
> >> been posted over the years, so I think it was more of a conceptual goal
> >> than a concrete requirement.
> >
> > Well, patches to do that first need to replace the VLAN-only dump
> > feature.
> >
> > To fully deprecate -net, we also have to replace -net nic for
> > configuring onboard NICs.
> >
> > Prior discussion:
> > http://lists.nongnu.org/archive/html/qemu-devel/2013-02/msg03743.html
> >
> > We haven't really tried either.
>
> 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?
Take a look at nd_table[] and nb_nics. That's the array of -net nic
devices. The boards look into the array to grab NICs.
The default NIC is set in net_init_clients() as a "-net nic" option.
The weird thing about "-net nic" is that the device is not created in
net/net.c by the "-net nic" command-line option. It just adds the
information to the nd_table[] array.
It's the board that has to instantiate nd_table[] entries. For example,
pc_nic_init() adds devices for x86 guests.
That's about all I know or have thought about so far. It would be nice
to get rid of -net but it will take some work and is a QEMU 3.0 feature
since it breaks backwards compatibility.
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-07-17 8:16 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 ` [Qemu-devel] net: Next steps to deprecate -net Thomas Huth
2015-07-22 13:40 ` Markus Armbruster
2015-07-22 16:20 ` Michael S. Tsirkin
2015-07-22 16:45 ` Thomas Huth
2015-07-17 8:16 ` Stefan Hajnoczi [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=20150717081625.GA16079@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).