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

[John Smith <netman1@xxxxxxx>]

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.

        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. Windows is in the works and
expected to be supported with release 3.0. All domainu kernels run as
child processes of the domain0 proces.

        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 kernel on disc can be shared by an unlimited number of domains.

        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. 

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

        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 (127.0.0.1) address of
domain0.

        Thanks for commenting on my idiocy and for xen.

Sincerely,

Jan.

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