qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Eric Blake <eblake@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 7/8] net: Add a new convenience option "-n" to configure default/on-board NICs
Date: Mon, 19 Feb 2018 17:37:41 +0100	[thread overview]
Message-ID: <f5a42ed6-a52a-7220-46f2-7cbbb7863e21@redhat.com> (raw)
In-Reply-To: <7c298a4a-97cd-4b7a-d170-b70ab2970aac@redhat.com>

On 19.02.2018 17:20, Paolo Bonzini wrote:
> On 19/02/2018 10:15, Thomas Huth wrote:
>> The legacy "-net" option can be quite confusing for the users since most
>> people do not expect to get a "vlan" hub between their emulated guest
>> hardware and the host backend. But so far, we are also not able to get
>> rid of "-net" completely, since it is the only way to configure on-board
>> NICs that can not be instantiated via "-device" yet. It's also a little
>> bit shorter to type "-net nic -net tap" instead of "-device xyz,netdev=n1
>> -netdev tap,id=n1".
>>
>> So what we need is a new convenience option that is shorter to type than
>> the full -device + -netdev stuff, and which can be used to configure the
>> on-board NICs that can not be handled via -device yet. Thus this patch now
>> provides such a new option "-n": It adds an entry in the nd_table to
>> configure a on-board / default NIC, creates a host backend and connects
>> the two directly, without a confusing "vlan" hub inbetween.
> 
> Sorry for the bikeshedding, but... perhaps "-n" is a bit bold.  While I
> initially couldn't come up with a better one, after putting some thought
> into it "-nic" came to mind.  There's precedent in naming the option for
> the *front-end* device that it creates, whereas the arguments define
> either the front-end (e.g. "model") or the back-end; see for example
> "-drive".  "-nic tap,model=e1000" and "-nic none" both make nice sense.

Actually, I like the idea with "--nic", that indeed makes sense here and
is still quite short to type. I'll use that in v2 (but I'll wait one or
two more days for some more review comments before sending that out).

 Thomas

  reply	other threads:[~2018-02-19 16:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19  9:15 [Qemu-devel] [PATCH v1 0/8] Improvements and clean-ups related to -net Thomas Huth
2018-02-19  9:15 ` [Qemu-devel] [PATCH v1 1/8] net: Move error reporting from net_init_client/netdev to the calling site Thomas Huth
2018-02-19 13:38   ` Eric Blake
2018-02-19 16:07   ` Paolo Bonzini
2018-02-19  9:15 ` [Qemu-devel] [PATCH v1 2/8] net: List available netdevs with "-netdev help" Thomas Huth
2018-02-19 16:08   ` Paolo Bonzini
2018-02-19 17:18   ` Eric Blake
2018-02-19  9:15 ` [Qemu-devel] [PATCH v1 3/8] net: Only show vhost-user in the help text if CONFIG_POSIX is defined Thomas Huth
2018-02-19 16:10   ` Paolo Bonzini
2018-02-19  9:15 ` [Qemu-devel] [PATCH v1 4/8] net: Make net_client_init() static Thomas Huth
2018-02-19 16:12   ` Paolo Bonzini
2018-02-19  9:15 ` [Qemu-devel] [PATCH v1 5/8] net: Remove the deprecated way of dumping network packets Thomas Huth
2018-02-19 16:13   ` Paolo Bonzini
2018-02-19 17:14   ` Eric Blake
2018-02-19  9:15 ` [Qemu-devel] [PATCH v1 6/8] net: Remove the deprecated 'host_net_add' and 'host_net_remove' HMP commands Thomas Huth
2018-02-19 16:13   ` Paolo Bonzini
2018-02-19  9:15 ` [Qemu-devel] [PATCH v1 7/8] net: Add a new convenience option "-n" to configure default/on-board NICs Thomas Huth
2018-02-19 16:20   ` Paolo Bonzini
2018-02-19 16:37     ` Thomas Huth [this message]
2018-02-19  9:15 ` [Qemu-devel] [PATCH v1 8/8] qemu-doc: Make "-net" less prominent Thomas Huth
2018-02-19 13:29 ` [Qemu-devel] [PATCH v1 0/8] Improvements and clean-ups related to -net Eric Blake
2018-02-19 13:37   ` Thomas Huth

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=f5a42ed6-a52a-7220-46f2-7cbbb7863e21@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).