qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Regression "Warning: more nics requested than this machine supports"
Date: Fri, 20 May 2011 12:19:33 +0100	[thread overview]
Message-ID: <BANLkTinM3s8CA05KfXASmyfB-WN7DrJ3rQ@mail.gmail.com> (raw)
In-Reply-To: <m3sjsevay8.fsf@blackfin.pond.sub.org>

On 16 May 2011 17:58, Markus Armbruster <armbru@redhat.com> wrote:
>    $ qemu-system-x86_64 -nodefaults -enable-kvm -m 384 -vnc :0 -S -netdev user,id=net0 -device e1000,netdev=net0
>    Warning: more nics requested than this machine supports; some have been ignored
>    (qemu) info network
>    Devices not on any VLAN:
>      net0: net=10.0.2.0, restricted=n peer=e1000.0
>      e1000.0: model=e1000,macaddr=52:54:00:12:34:56 peer=net0
>
> Culprit is
>    net: Improve the warnings for dubious command line option combinations

> Its count of requested NICs is blissfully unaware of -device.  In my
> example, it comes up with nb_nics == 0 and seen_nics == 1.

As far as I can determine, "-device e1000,netdev=0" doesn't go through
net_init_nic() and doesn't put an entry in the nd_table[] for the NIC.
This means it's broken, because a lot of board models look in nd_table[]
to determine whether the user requested a NIC and whether it's the right
type. So I think that in some ways this is just showing up an existing
problem with trying to instantiate a network card with -device.

-- PMM

  reply	other threads:[~2011-05-20 11:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 16:58 [Qemu-devel] Regression "Warning: more nics requested than this machine supports" Markus Armbruster
2011-05-20 11:19 ` Peter Maydell [this message]
2011-05-20 11:50   ` Jan Kiszka

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=BANLkTinM3s8CA05KfXASmyfB-WN7DrJ3rQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=armbru@redhat.com \
    --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 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).