From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Networking possibilities
Date: Mon, 27 Dec 2004 16:34:51 -0500 [thread overview]
Message-ID: <20041227213451.GA8166@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <001101c4ec0f$5ec240f0$8916fea9@freelance>
On Mon, Dec 27, 2004 at 08:26:56PM +0800, Ming-Ching Tiew wrote:
>
> I would like to know if it is possible to run a few instances
> of Qemu's ( ie a few guest OS'es ) and make them network
> with one another ? In each of the instance there maybe
> multiple network cards, I would like to be able to specify each
> network card to go to which tun device and then allow another
> instance to connect specifically to that particular tun device,
> instead of only connected to the host OS.
You don't need multiple tuntap devices in the guest, you only need one.
>
> That's tun/tap devices are used to connect multiple instances
> of qemu together or with the host OS.
There are two ways I can think of to do this.
The easy way is to use VDE (vde.sourceforge.net), which allows you to share a
single tuntap device amoung all qemu instances. (Or, if you don't have root
permissions, it can even emulate a tuntap device for you). The VDE HOWTO should
give the basics on how to do this.
The hard way is to set up each qemu instance normally, and then connect them
together thru the host, either with bridging or iptable tricks.
>
> Bottomline I would like to be able to set up a farm of guest OS's
> which could perform internetworking among each other. This is
> extremely useful for testing/developing networking software.
> Is it possible ?
Yes.
>
> Cheers
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2004-12-27 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 12:26 [Qemu-devel] Networking possibilities Ming-Ching Tiew
2004-12-27 16:12 ` Doug Stanley
2004-12-27 16:22 ` Felipe Sanchez
2004-12-27 18:11 ` Tim
2004-12-27 21:34 ` Jim C. Brown [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=20041227213451.GA8166@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.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 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).