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/
Home Products Support Community News


Re: [Xen-users] Assumption is the mother...

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Assumption is the mother...
From: Andy Smith <andy@xxxxxxxxxxxxxx>
Date: Wed, 29 Jun 2005 13:17:42 +0000
Delivery-date: Wed, 29 Jun 2005 13:16:36 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050629145735.16c63f7a.netman1@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Openpgp: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc
References: <20050629145735.16c63f7a.netman1@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Wed, Jun 29, 2005 at 02:57:34PM +0200, John Smith wrote:
> Hi all,
>       you know how to finish that line. Recently started trying xen
> (awsome!) and since the documentation is in some aspects still a bit 
> vague, I would like to get a few assumptions confirmed/denied and
> some questions answered.

I am fairly new to Xen myself but may be able to clarify a few things.

>       Domain0 is the top level kernel and manages a series of domainu
> kernels which can be of several different flavours at the moment, name-
> ly at least Linux, Free-, Open and NetBSD.

FreeBSD is still in development, I don't think an OpenBSD port
exists.  I have heard of a few people using NetBSD but don't know
how well it works.  Liux works well enough for production use.

> Windows is in the works and expected to be supported with release
> 3.0.

Windows or any other unmodified guest OS would require
VT-capable CPUs.

> All domainu kernels run as child processes of the domain0 proces.

No; the way I understand it all domains interface with the actual
Xen kernel that your boot process loads.  dom0 is special in that it
has access to the hardware and it is privileged to manage other

>       All kernels still have to be separately compiled with xen spe-
> cific options (so no really native kernels now).


>       All kernels and their direct dependencies (/lib/modules for 
> Linux, -how about the *BSD's?-) are stored on domain0's filesystem, the 
> domains are described in domain0:/etc/xen/auto and started by 
> domain0:/etc/init.d/xendomains.

A domU's modules would need to be stored inside the filesystem of
the domU itself.

>       A kernel on disc can be shared by an unlimited number of domains.

dom0 just reads the kernel image as a normal file so yes.

>       It is recommended that each of the domains (or virtual machines)
> including domain0, have their own filesystem(s), although it may be wise
> to share read-only filesystem like /usr. 

It isn't possible to mount a normal block device more than once for
writing.  I'm not even sure if it's possible to mount it read-only
if there is another writer somewhere.

You could share filesystems with an already-existing network-aware
or clustering filesystem like NFS, GFS or OCFS.

>       Can vm's share local filesystems and if so how do they look at 
> them, NFS, local ..., and how are conflicts -filelocking etc.- handled?

You share filesystems using normal methods for sharing filesystems,
e.g. NFS, SMB, GFS, ... each of which will have their own semantics
for locking which aren't related to Xen.  It is the same issue as if
you had multiple distinct hosts on a local network and you wanted to
share filesystems between them.

>       All network communication with domain0 on a single nic machine
> (the default) is handled through a virtual bridge interface on the 
> single nic which allows access to the localhost ( address of
> domain0.

A virtual interface (vif) is created and a real network device in
dom0 (e.g. eth0) is bridged to it.  Thus it behaves a bit like a
switching hub and all traffic hitting eth0 can get to the vifs it is
bridged with.  This happens below the layer where IP addresses
matter, but you would not normally see addresses since
they only pass lo (loopback) and you would not bridge with lo.


Attachment: signature.asc
Description: Digital signature

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>