From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] tun/tap networking: patch for existing tun
Date: Sun, 2 Oct 2005 15:39:12 -0400 [thread overview]
Message-ID: <20051002193912.GB13825@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <43402ABC.3040805@us.ibm.com>
On Sun, Oct 02, 2005 at 01:45:16PM -0500, Anthony Liguori wrote:
> I don't understand, why is this patch needed?
>
It makes qemu easier to use.
A lot easier to use a persistent tap by doing "qemu -use-already-open-tap tap1"
instead of hacking around with persistenttapdev.c
> It's a pretty simple C program to create a tun device by whatever name
> you want and just pass the fd to qemu via -tun-fd. I think it's
> generally better to have the least number of options necessary to make
> things easier to understand.
>
Like the way vdeq/vdeqemu does it? That works, but is that really the best way
to handle it?
vdeq works the way it does because the odds of getting a special "-vde-socket"
option in qemu were moot. And perhaps so the author of VDE could have control
over what options vdeq supported. (In the case of vdeq, its a clever hack: both
tuntap devices and sockets are controlled via fds, so vdeq sends a socket fd
instead of a tuntap fd and qemu is none the wiser. Hypothetically one could
even pass a regular file via -tun-fd.)
Having an option for specifying tuntap devices by name on the command line
(persistent or not) is the cleanest way to do it, and also the easiest for the
user. Maybe even make it so we just pass an option "-tap tap0": if tap0 doesnt
exist then qemu creates a new device with that name, if it does exist then
qemu opens it as if it were a persistent tuntap.
In fact, if qemu supported both these things, then I don't see a reason for
-tun-fd at all (except for something like VDE).
> Is it really something that so many people would want to use that it
> warrants making it an option? Is there a concrete use-case that this
> enables?
What it really boils down to is cleaning up the command line options for the
network interface(s), which up to now have been added in a hackish, piece-wise
manner.
>
> Regards,
>
> Anthony Liguori
>
> >Maybe can I propose to joint our effort ?
>
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-10-02 19:41 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 22:13 [Qemu-devel] tun/tap networking Don Kitchen
2005-09-30 22:21 ` Henrik Nordstrom
2005-09-30 22:21 ` Paul Brook
2005-09-30 23:01 ` Jim C. Brown
2005-10-01 8:12 ` Jean-Christian de Rivaz
2005-10-01 13:12 ` Jim C. Brown
2005-10-01 20:24 ` Jean-Christian de Rivaz
2005-10-01 21:09 ` Jim C. Brown
2005-10-01 21:17 ` Jean-Christian de Rivaz
2005-10-01 20:47 ` [Qemu-devel] tun/tap networking: patch for existing tun Jean-Christian de Rivaz
2005-10-02 2:42 ` Henrik Nordstrom
2005-10-02 7:56 ` Jean-Christian de Rivaz
2005-10-02 10:24 ` Henrik Nordstrom
2005-10-02 16:53 ` Lars Munch
2005-10-02 17:50 ` Jean-Christian de Rivaz
2005-10-02 19:47 ` Jim C. Brown
2005-10-02 20:27 ` Jean-Christian de Rivaz
2005-10-02 18:45 ` Anthony Liguori
2005-10-02 19:39 ` Jim C. Brown [this message]
2005-10-02 20:23 ` Jean-Christian de Rivaz
2005-10-02 22:37 ` Jim C. Brown
2005-10-03 9:46 ` Jean-Christian de Rivaz
2005-10-03 12:04 ` Jim C. Brown
2005-10-03 13:10 ` Jean-Christian de Rivaz
2005-10-03 13:19 ` Henrik Nordstrom
2005-10-03 13:13 ` Henrik Nordstrom
2005-10-03 14:14 ` Jean-Christian de Rivaz
2005-10-03 13:07 ` Henrik Nordstrom
2005-10-03 14:00 ` Jean-Christian de Rivaz
2005-10-03 15:04 ` Jim C. Brown
2005-10-03 13:01 ` Henrik Nordstrom
2005-10-03 13:58 ` Jean-Christian de Rivaz
2005-10-03 15:06 ` Jim C. Brown
2005-10-03 12:54 ` Henrik Nordstrom
2005-10-03 15:14 ` Jim C. Brown
2005-10-03 18:29 ` Fabrice Bellard
2005-10-03 19:22 ` Christian MICHON
2005-10-03 20:29 ` Jean-Christian de Rivaz
2005-10-04 7:09 ` Christian MICHON
2005-10-04 7:56 ` Jean-Christian de Rivaz
2005-10-03 21:36 ` Jim C. Brown
2005-10-04 8:23 ` Matteo
2005-10-04 11:34 ` Jim C. Brown
2005-10-01 17:49 ` [Qemu-devel] tun/tap networking Henrik Nordstrom
2005-10-01 20:54 ` Jean-Christian de Rivaz
2005-10-01 11:30 ` Oliver Gerlich
2005-10-01 13:07 ` Jim C. Brown
2005-10-01 13:50 ` Paul Brook
2005-10-01 21:15 ` Jim C. Brown
2005-10-02 2:21 ` Henrik Nordstrom
2005-10-01 17:52 ` Henrik Nordstrom
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=20051002193912.GB13825@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--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).