From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>, PReP <qemu-ppc@nongnu.org>,
Alexander Graf <agraf@suse.de>,
Anthony Liguori <anthony@codemonkey.ws>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC PATCH] spapr: add ibmveth to the supported network adapters list
Date: Mon, 04 Nov 2013 11:22:03 +0100 [thread overview]
Message-ID: <5277754B.2090107@redhat.com> (raw)
In-Reply-To: <8738nfxazm.fsf@blackfin.pond.sub.org>
Il 02/11/2013 13:07, Markus Armbruster ha scritto:
>> Why do you even need a new category? Just take everything in the
>> network category and put it in the help.
>
> You *can't* currently construct -net nic,model=help output from
> registered qdev NICs, because:
>
> * -net nic generally doesn't accept all qdev NICs, and
>
> * the model names accepted by -net nic need *not* match the qdev device
> model names (example: virtio != virtio-net), and
Both could be solved by accepting legacy aliases, plus all non-no_user NICs.
> * -net nic may accept model names that map to a non-qdevified NIC (not
> sure such NICs still exist).
I think any of those (and also SysBus NICs) would only accept the
default model.
Paolo
next prev parent reply other threads:[~2013-11-04 10:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 3:09 [Qemu-devel] [RFC PATCH] spapr: add ibmveth to the supported network adapters list Alexey Kardashevskiy
2013-10-18 5:39 ` Alexey Kardashevskiy
2013-10-27 18:03 ` Alexander Graf
2013-11-01 10:52 ` Alexey Kardashevskiy
2013-11-01 12:47 ` Alexander Graf
2013-11-02 11:51 ` Markus Armbruster
2013-11-02 22:52 ` Alexander Graf
2013-11-02 10:56 ` Paolo Bonzini
2013-11-02 12:07 ` Markus Armbruster
2013-11-04 10:22 ` Paolo Bonzini [this message]
2013-11-02 12:26 ` Alexey Kardashevskiy
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=5277754B.2090107@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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.