From: JP Senior <jp.senior@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 589827] Re: QEMU netdev tap type id name is not used on linux host
Date: Thu, 10 Jun 2010 03:59:51 -0000 [thread overview]
Message-ID: <20100610035951.9142.70876.malone@soybean.canonical.com> (raw)
In-Reply-To: 20100604184053.4709.16201.malonedeb@soybean.canonical.com
Thanks to IRC, the correct syntax is: -netdev
tap,id=asa1_eth0_tap,ifname=asa1_eth0_tap -device
e1000,netdev=asa1_eth0_tap,mac=00:aa:cd:dd:01:01
(noted, fd=h option doesn't work on -netdev)
--
QEMU netdev tap type id name is not used on linux host
https://bugs.launchpad.net/bugs/589827
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: New
Bug description:
Tested with 0.12.3, 0.12.4, and latest git as of 4 jun 2010.
The new -netdev type seems to ignore manual specifications of tap ifname.
qemu-system-x86_64 -hda disk.img -netdev tap,id=ids_e0 -device e1000,netdev=ids_e0
**creates tap0 instead of ids_e0. tap0 passes traffic, ids_e0 doesn't exist
(I tried -netdev type=tap as well for brevity)
QEMU creates a tap0 (or appropriate) interface and does not name this "ids_e0" as would be expected. I also tried 'pre' creating the tap interface.
Previous alterantive was
qemu-system-x86_64 -hda disk.img -net nic,model=e1000,vlan=99 -net tap,ifname=ids_e0,vlan=99
**creates ids_e0 as expected, and passes traffic as expected.
next prev parent reply other threads:[~2010-06-10 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 18:40 [Qemu-devel] [Bug 589827] [NEW] QEMU netdev tap type id name is not used on linux host JP Senior
2010-06-10 3:59 ` JP Senior [this message]
2017-01-10 8:56 ` [Qemu-devel] [Bug 589827] " 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=20100610035951.9142.70876.malone@soybean.canonical.com \
--to=jp.senior@gmail.com \
--cc=589827@bugs.launchpad.net \
--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 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.