WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Does XEN use TUN/TAP interface?

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] Does XEN use TUN/TAP interface?
From: Daniel Stodden <stodden@xxxxxxxxxx>
Date: Sun, 16 Mar 2008 19:51:23 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Pavel Muller <pav.muller@xxxxxxxxx>
Delivery-date: Sun, 16 Mar 2008 11:58:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080316174129.GB6678@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Fakultät für Informatik I10, Technische Universität München
References: <73804daf0803160752h3d798739oa8ccffcbb1aa9cc2@xxxxxxxxxxxxxx> <1205686219.17474.7.camel@xxxxxxxxxxxxxxxxxxxx> <20080316171210.GA6678@xxxxxxxxxx> <1205688111.17474.24.camel@xxxxxxxxxxxxxxxxxxxx> <20080316174129.GB6678@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sun, 2008-03-16 at 17:41 +0000, Daniel P. Berrange wrote:

> > > Whether it is a separate hypervisor / Dom0, or a combined HV+Dom0 is not
> > > really relevant to this question. In both cases the driver backends are 
> > > in the Linux host OS and not the hypervisor itself.
> > 
> > Using TUN/TAP is absolutely pointless if the peer is not running in
> > userland. Because connecting userspace to a network interface is the
> > whole point there. 
> > 
> > And this is why the VMM type matters to answer the question.
> 
> No the distinction here is between kernel space & user space backends, not
> between host OS and hypervisor. The hypervisor doesn't get involved in the
> driver backends - it is delegated to the host OS to take care of.

Okay, you're certainly right. I hereby correct myself:

TUN/TAP is used when the VMM part doing I/O virtualization is in
userspace.  Whether the part of the VMM doing I/O virtualization ends up
as userspace on a UNIX system with TUN/TAP support depends on the VMM
type, with the exception of a type I VMM which is quite different from a
typical type I VMM in that it is delegating I/O virtualization to a
guest OS running QEMU.

Much better, thank you.

Kind Regards,
Daniel

-- 
Daniel Stodden
LRR     -      Lehrstuhl für Rechnertechnik und Rechnerorganisation
Institut für Informatik der TU München             D-85748 Garching
http://www.lrr.in.tum.de/~stodden         mailto:stodden@xxxxxxxxxx
PGP Fingerprint: F5A4 1575 4C56 E26A 0B33  3D80 457E 82AE B0D8 735B



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>