From: Jedrzej Kalinowski <kalinoj1@iem.pw.edu.pl>
To: qemu-devel@nongnu.org
Cc: Charles Duffy <Charles_Duffy@messageone.com>
Subject: Re: [Qemu-devel] Re: Connecting two tap interfaces to one qemu instance
Date: Sat, 30 May 2009 12:56:57 +0200 [thread overview]
Message-ID: <4A2110F9.8020808@iem.pw.edu.pl> (raw)
In-Reply-To: <gvn6rn$2i8$1@ger.gmane.org>
Charles Duffy wrote:
> Jedrzej Kalinowski wrote:
>> Hello,
>>
>> I've found a problem when trying to run one qemu instance with two tap
>> devices connected to a bridge.
>>
>> I mean a commandline like this:
>> qemu -net nic -net tap -net nic -net tap ...
>
> Do this instead:
>
> qemu -net nic,vlan=0 -net tap,vlan=0 -net nic,vlan=1 -net tap,vlan=1 ...
>
>
>
It helped, thank you!
--
Jędrzej Kalinowski
prev parent reply other threads:[~2009-05-30 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 20:23 [Qemu-devel] Connecting two tap interfaces to one qemu instance Jedrzej Kalinowski
2009-05-28 20:39 ` Brian Jackson
2009-05-28 22:13 ` Jedrzej Kalinowski
2009-05-29 11:54 ` Paul Brook
2009-05-28 23:31 ` [Qemu-devel] " Charles Duffy
2009-05-30 10:56 ` Jedrzej Kalinowski [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=4A2110F9.8020808@iem.pw.edu.pl \
--to=kalinoj1@iem.pw.edu.pl \
--cc=Charles_Duffy@messageone.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).