From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] net: Inform the user about deprecated -net options
Date: Tue, 15 Dec 2015 17:33:44 +0100 [thread overview]
Message-ID: <567040E8.3000605@redhat.com> (raw)
In-Reply-To: <CAFEAcA_E+vDpOmM-oV1nxheJtiUMhHYYVvQXNwz+mmYNMhwYig@mail.gmail.com>
On 15/12/15 17:17, Peter Maydell wrote:
> On 15 December 2015 at 12:51, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Honestly, I still do not believe that they will be removed. They are
>> little more than syntactic sugar at this point.
>
> If they're just syntactic sugar, what is the new-style command
> line mechanism for configuring boards with embedded network
> controller devices? Last time I looked at this that was just
> impossible...and as long as it is, you can't get rid of any
> of the backend -net config either, because it has to be either
> all -net or all new-style and not a mix (I think).
No, you can use "-netdev user,id=mynet -net nic,netdev=mynet" for
example to wire an embedded network controller to a netdev device, so
that's not a problem anymore.
Thomas
next prev parent reply other threads:[~2015-12-15 16:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 11:46 [Qemu-devel] [PATCH] net: Inform the user about deprecated -net options Thomas Huth
2015-12-15 12:51 ` Paolo Bonzini
2015-12-15 16:01 ` Thomas Huth
2015-12-15 16:21 ` Paolo Bonzini
2015-12-15 16:46 ` Eric Blake
2015-12-15 17:15 ` Thomas Huth
2015-12-15 17:31 ` Paolo Bonzini
2015-12-15 17:50 ` Thomas Huth
2015-12-15 18:08 ` Paolo Bonzini
2015-12-16 7:20 ` Thomas Huth
2015-12-16 8:50 ` Paolo Bonzini
2015-12-15 16:17 ` Peter Maydell
2015-12-15 16:33 ` Thomas Huth [this message]
2015-12-15 16:46 ` Peter Maydell
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=567040E8.3000605@redhat.com \
--to=thuth@redhat.com \
--cc=jasowang@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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.