From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Regression "Warning: more nics requested than this machine supports"
Date: Fri, 20 May 2011 13:50:17 +0200 [thread overview]
Message-ID: <4DD65579.6090901@siemens.com> (raw)
In-Reply-To: <BANLkTinM3s8CA05KfXASmyfB-WN7DrJ3rQ@mail.gmail.com>
On 2011-05-20 13:19, Peter Maydell wrote:
> 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.
qemu_new_nic must call net_init_nic so that this works properly. Of
course we need to avoid calling it multiple times when the adapter is
still instantiated via the old -net or via board init code.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2011-05-20 11:50 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
2011-05-20 11:50 ` Jan Kiszka [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=4DD65579.6090901@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=armbru@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 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).