From: "Sebastian Herbszt" <herbszt@gmx.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] ne2k_isa: how to specify a custom iobase and irq?
Date: Fri, 18 Dec 2009 22:43:17 +0100 [thread overview]
Message-ID: <934349ECE007414393806679A9601B59@FSCPC> (raw)
In-Reply-To: <4B2BEBF4.6070202@codemonkey.ws>
Anthony Liguori wrote:
> Sebastian Herbszt wrote:
>> Gerd Hoffmann wrote:
>>> On 12/18/09 07:12, Markus Armbruster wrote:
>>>> "Sebastian Herbszt"<herbszt@gmx.de> writes:
>>>>
>>>>> The default iobase and irq for the ne2k_isa card are 0x300 and 9.
>>>>> It should be possible to override both using the "-net" syntax like
>>>>> "-net nic,model=ne2k_isa,irq=5,iobase=0x280".
>>>>
>>>> -device ne2k_isa,irq=5,iobase=0x280
>>>
>>> Also needs vlan=0, otherwise you'll end up with an unconnected nic.
>>
>> Shouldn't vlan have a default value of 0 like it does with the "-net"
>> syntax?
>
> No, you don't actually have to tie it to a vlan.
Actually you have to else networking doesn't work at all. Without specifying
"vlan" with the "-device" syntax you end up with vlan=<null> and not vlan=0
with "info qtree".
- Sebastian
next prev parent reply other threads:[~2009-12-18 21:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 21:29 [Qemu-devel] ne2k_isa: how to specify a custom iobase and irq? Sebastian Herbszt
2009-12-18 6:12 ` Markus Armbruster
2009-12-18 8:37 ` Gerd Hoffmann
2009-12-18 20:00 ` Sebastian Herbszt
2009-12-18 20:54 ` Anthony Liguori
2009-12-18 21:43 ` Sebastian Herbszt [this message]
2009-12-18 23:23 ` Anthony Liguori
2009-12-18 19:58 ` Sebastian Herbszt
2009-12-18 20:56 ` Anthony Liguori
2009-12-18 20:24 ` Sebastian Herbszt
2009-12-18 20:56 ` Anthony Liguori
2009-12-18 21:16 ` Sebastian Herbszt
2009-12-21 12:37 ` Markus Armbruster
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=934349ECE007414393806679A9601B59@FSCPC \
--to=herbszt@gmx.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=kraxel@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).