Index: trunk/shell/c-i-a-b.common
===================================================================
--- trunk/shell/c-i-a-b.common	(revision 17)
+++ trunk/shell/c-i-a-b.common	(revision 18)
@@ -1,11 +1,23 @@
 # ST - 2012-03-09
 # Constants that no one should not change.
-CONST_NULL_DISK_SIZE=0G
+CONST_NULL_DISK_SIZE=0G # For several configuration files.
 #
+# Constant that may change with another Xen version.
+CONST_DOM0_CPUS_ALL="(dom0-cpus 0)"
+CONST_DOM0_NAME=Domain-0
+CONST_NOSWAP="noswap = 1" # For /etc/xen-tools/xen-tools.conf.
+CONST_NETWORK_SCRIPT_KEYWORD=network-script # For /etc/xen/xend-config.sxp.
+#
 # Common user defined configuration variables
 #
+CLUSTER_ARCH=amd64
+CLUSTER_BRIDGE_SCRIPT=network-bridge-internal
+CLUSTER_BRIDGE_CLAUSE="($CONST_NETWORK_SCRIPT_KEYWORD $CLUSTER_BRIDGE_SCRIPT)"
+CLUSTER_IMAGE=full
 CLUSTER_DOMAIN_NAME=ciab.lip.ens-lyon.fr
+CLUSTER_NOSWAP="$CONST_NOSWAP"
 CLUSTER_STATIC_NETWORK_PREFIX="192.168.1"
+CLUSTER_SWAP_SIZE=$CONST_NULL_DISK_SIZE
 COMPUTE_NODE_BRIDGE=internal
 COMPUTE_NODE_CPUS_FILE=compute-nodes-cpus
 COMPUTE_NODE_DISK_MOUNT_POINT=/mnt/compute-node-system-disk
@@ -20,6 +32,9 @@
 COMPUTE_NODE_NAME_PREFIX="compute-node-"
 COMPUTE_NODE_STATIC_NETWORK_PREFIX=$CLUSTER_STATIC_NETWORK_PREFIX
 DHCP_HOSTSFILE_BASENAME=dhcp-hostsfile
+DOM0_CPUS_LIST="0 4"
+DOM0_CPUS_NUM=2
+DOM0_CPUS_CLAUSE="(dom0-cpus $DOM0_CPUS_NUM)"
 FRONT_END_HOME_DISK_SIZE=512G
 FRONT_END_INTERFACES_TEMPLATE=interfaces.front-end
 FRONT_END_HOME_VOLUME_GROUP=vg_slow
Index: trunk/shell/templates/etc/xen/front-end.cfg
===================================================================
--- trunk/shell/templates/etc/xen/front-end.cfg	(revision 17)
+++ trunk/shell/templates/etc/xen/front-end.cfg	(revision 18)
@@ -1,27 +1,26 @@
 #
-# Template file for the Xen instance compute-node.
+# Configuration file for the Xen instance skanda.lip.ens-lyon.fr, created
+# by xen-tools 4.2 on Mon Feb 28 17:41:00 2011.
 #
 
 #
 #  Kernel + memory size
 #
-kernel      = '__COMPUTE_NODE_KERNEL__'
-ramdisk     = '__COMPUTE_NODE_RAMDISK__'
+kernel      = '/boot/vmlinuz-2.6.32-5-xen-amd64'
+ramdisk     = '/boot/initrd.img-2.6.32-5-xen-amd64'
 
-memory      = '__COMPUTE_NODE_MEMORY__'
+vcpus       = '4'
+cpus        = '1,9,5,13'
+memory      = '3072'
 
-# (V)CPU management
-
-vcpus       = '__COMPUTE_NODE_VCPUS__'
-cpus        = '__COMPUTE_NODE_CPUS__'
-
 #
 #  Disk device(s).
 #
 root        = '/dev/xvda2 ro'
 disk        = [
-                  'phy:__COMPUTE_NODE_SYSTEM_DISK__,xvda2,w',
-                  'phy:__COMPUTE_NODE_SWAP_DISK__,xvda1,w',
+                  'phy:/dev/vg_guests/users-home-disk,xvda3,w',
+                  'phy:/dev/vg_guests/skanda.lip.ens-lyon.fr-disk,xvda2,w',
+                  'phy:/dev/vg_guests/skanda.lip.ens-lyon.fr-swap,xvda1,w',
               ]
 
 
@@ -33,12 +32,12 @@
 #
 #  Hostname
 #
-name        = '__COMPUTE_NODE_HOST_NAME__'
+name        = 'skanda.lip.ens-lyon.fr'
 
 #
 #  Networking
 #
-vif         = [ 'ip=__COMPUTE_NODE_IP__,mac=__COMPUTE_NODE_MAC__,bridge=__COMPUTE_NODE_BRIDGE__', ]
+vif         = [ 'ip=140.77.13.40,mac=00:16:3E:33:A3:F1', 'ip=192.168.1.251,mac=00:16:3E:33:A3:F2,bridge=internal' ] 
 
 #
 #  Behaviour
Index: trunk/shell/templates/etc/xen/xend-config.sxp
===================================================================
--- trunk/shell/templates/etc/xen/xend-config.sxp	(revision 0)
+++ trunk/shell/templates/etc/xen/xend-config.sxp	(revision 18)
@@ -0,0 +1,284 @@
+# -*- sh -*-
+
+#
+# Xend configuration file.
+#
+
+# This example configuration is appropriate for an installation that 
+# utilizes a bridged network configuration. Access to xend via http
+# is disabled.  
+
+# Commented out entries show the default for that entry, unless otherwise
+# specified.
+
+#(logfile /var/log/xen/xend.log)
+#(loglevel DEBUG)
+
+# Uncomment the line below.  Set the value to flask, acm, or dummy to 
+# select a security module.
+
+#(xsm_module_name dummy)
+
+# The Xen-API server configuration.
+#
+# This value configures the ports, interfaces, and access controls for the
+# Xen-API server.  Each entry in the list starts with either unix, a port
+# number, or an address:port pair.  If this is "unix", then a UDP socket is
+# opened, and this entry applies to that.  If it is a port, then Xend will
+# listen on all interfaces on that TCP port, and if it is an address:port
+# pair, then Xend will listen on the specified port, using the interface with
+# the specified address.
+#
+# The subsequent string configures the user-based access control for the
+# listener in question.  This can be one of "none" or "pam", indicating either
+# that users should be allowed access unconditionally, or that the local
+# Pluggable Authentication Modules configuration should be used.  If this
+# string is missing or empty, then "pam" is used.
+#
+# The final string gives the host-based access control for that listener. If
+# this is missing or empty, then all connections are accepted.  Otherwise,
+# this should be a space-separated sequence of regular expressions; any host
+# with a fully-qualified domain name or an IP address that matches one of
+# these regular expressions will be accepted.
+#
+# Example: listen on TCP port 9363 on all interfaces, accepting connections
+# only from machines in example.com or localhost, and allow access through
+# the unix domain socket unconditionally:
+#
+#   (xen-api-server ((9363 pam '^localhost$ example\\.com$')
+#                    (unix none)))
+#
+# Optionally, the TCP Xen-API server can use SSL by specifying the private
+# key and certificate location:
+#
+#                    (9367 pam '' xen-api.key xen-api.crt)
+#
+# Default:
+#   (xen-api-server ((unix)))
+
+
+#(xend-http-server no)
+#(xend-unix-server no)
+#(xend-tcp-xmlrpc-server no)
+#(xend-unix-xmlrpc-server yes)
+#(xend-relocation-server no)
+#(xend-relocation-ssl-server no)
+#(xend-udev-event-server no)
+
+#(xend-unix-path /var/lib/xend/xend-socket)
+
+
+# Address and port xend should use for the legacy TCP XMLRPC interface, 
+# if xend-tcp-xmlrpc-server is set.
+#(xend-tcp-xmlrpc-server-address 'localhost')
+#(xend-tcp-xmlrpc-server-port 8006)
+
+# SSL key and certificate to use for the legacy TCP XMLRPC interface.
+# Setting these will mean that this port serves only SSL connections as
+# opposed to plaintext ones.
+#(xend-tcp-xmlrpc-server-ssl-key-file  xmlrpc.key)
+#(xend-tcp-xmlrpc-server-ssl-cert-file xmlrpc.crt)
+
+
+# Port xend should use for the HTTP interface, if xend-http-server is set.
+#(xend-port            8000)
+
+# Port xend should use for the relocation interface, if xend-relocation-server
+# is set.
+#(xend-relocation-port 8002)
+
+# Port xend should use for the ssl relocation interface, if
+# xend-relocation-ssl-server is set.
+#(xend-relocation-ssl-port 8003)
+
+# SSL key and certificate to use for the ssl relocation interface, if
+# xend-relocation-ssl-server is set.
+#(xend-relocation-server-ssl-key-file   xmlrpc.key)
+#(xend-relocation-server-ssl-cert-file  xmlrpc.crt)
+
+# Whether to use ssl as default when relocating.
+#(xend-relocation-ssl no)
+
+# Address xend should listen on for HTTP connections, if xend-http-server is
+# set.
+# Specifying 'localhost' prevents remote connections.
+# Specifying the empty string '' (the default) allows all connections.
+#(xend-address '')
+#(xend-address localhost)
+
+# Address xend should listen on for relocation-socket connections, if
+# xend-relocation-server is set.
+# Meaning and default as for xend-address above.
+#(xend-relocation-address '')
+
+# The hosts allowed to talk to the relocation port.  If this is empty (the
+# default), then all connections are allowed (assuming that the connection
+# arrives on a port and interface on which we are listening; see
+# xend-relocation-port and xend-relocation-address above).  Otherwise, this
+# should be a space-separated sequence of regular expressions.  Any host with
+# a fully-qualified domain name or an IP address that matches one of these
+# regular expressions will be accepted.
+#
+# For example:
+#  (xend-relocation-hosts-allow '^localhost$ ^.*\\.example\\.org$')
+#
+#(xend-relocation-hosts-allow '')
+
+# The limit (in kilobytes) on the size of the console buffer
+#(console-limit 1024)
+
+##
+# NOTE:
+# Please read /usr/share/doc/xen-utils-common/README.Debian for Debian specific
+# informations about the network setup.
+
+##
+# To bridge network traffic, like this:
+#
+# dom0: ----------------- bridge -> real eth0 -> the network
+#                            |
+# domU: fake eth0 -> vifN.0 -+
+#
+# use
+#
+# (network-script network-bridge)
+# Use a modified script to create an internal bridge. ST-2012-03-06.
+__CLUSTER_BRIDGE_CLAUSE__
+# Your default ethernet device is used as the outgoing interface, by default. 
+# To use a different one (e.g. eth1) use
+#
+# (network-script 'network-bridge netdev=eth1')
+#
+# The bridge is named xenbr0, by default.  To rename the bridge, use
+#
+# (network-script 'network-bridge bridge=<name>')
+#
+# It is possible to use the network-bridge script in more complicated
+# scenarios, such as having two outgoing interfaces, with two bridges, and
+# two fake interfaces per guest domain.  To do things like this, write
+# yourself a wrapper script, and call network-bridge from it, as appropriate.
+#
+
+# The script used to control virtual interfaces.  This can be overridden on a
+# per-vif basis when creating a domain or a configuring a new vif.  The
+# vif-bridge script is designed for use with the network-bridge script, or
+# similar configurations.
+#
+# If you have overridden the bridge name using
+# (network-script 'network-bridge bridge=<name>') then you may wish to do the
+# same here.  The bridge name can also be set when creating a domain or
+# configuring a new vif, but a value specified here would act as a default.
+#
+# If you are using only one bridge, the vif-bridge script will discover that,
+# so there is no need to specify it explicitly.
+#
+(vif-script vif-bridge)
+
+
+## Use the following if network traffic is routed, as an alternative to the
+# settings for bridged networking given above.
+#(network-script network-route)
+#(vif-script     vif-route)
+
+
+## Use the following if network traffic is routed with NAT, as an alternative
+# to the settings for bridged networking given above.
+#(network-script network-nat)
+#(vif-script     vif-nat)
+
+# dom0-min-mem is the lowest permissible memory level (in MB) for dom0.
+# This is a minimum both for auto-ballooning (as enabled by
+# enable-dom0-ballooning below) and for xm mem-set when applied to dom0.
+(dom0-min-mem 1024)
+
+# Whether to enable auto-ballooning of dom0 to allow domUs to be created.
+# If enable-dom0-ballooning = no, dom0 will never balloon out.
+# ST 2012-03-06: ballooning is disabled since memory of dom0 is set
+# in GRUB.
+(enable-dom0-ballooning no)
+
+# 32-bit paravirtual domains can only consume physical
+# memory below 168GB. On systems with memory beyond that address,
+# they'll be confined to memory below 128GB.
+# Using total_available_memory (in GB) to specify the amount of memory reserved
+# in the memory pool exclusively for 32-bit paravirtual domains.
+# Additionally you should use dom0_mem = <-Value> as a parameter in 
+# xen kernel to reserve the memory for 32-bit paravirtual domains, default 
+# is "0" (0GB).  
+(total_available_memory 0) 
+
+# In SMP system, dom0 will use dom0-cpus # of CPUS
+# If dom0-cpus = 0, dom0 will take all cpus available
+__DOM0_CPUS_CLAUSE__
+
+# Whether to enable core-dumps when domains crash.
+#(enable-dump no)
+
+# The tool used for initiating virtual TPM migration
+#(external-migration-tool '')
+
+# The interface for VNC servers to listen on. Defaults
+# to 127.0.0.1  To restore old 'listen everywhere' behaviour
+# set this to 0.0.0.0
+#(vnc-listen '127.0.0.1')
+
+# The default password for VNC console on HVM domain.
+# Empty string is no authentication.
+(vncpasswd '')
+
+# The VNC server can be told to negotiate a TLS session
+# to encryption all traffic, and provide x509 cert to
+# clients enabling them to verify server identity. The
+# GTK-VNC widget, virt-viewer, virt-manager and VeNCrypt
+# all support the VNC extension for TLS used in QEMU. The
+# TightVNC/RealVNC/UltraVNC clients do not.
+#
+# To enable this create x509 certificates / keys in the
+# directory ${XEN_CONFIG_DIR} + vnc
+#
+#  ca-cert.pem       - The CA certificate
+#  server-cert.pem   - The Server certificate signed by the CA
+#  server-key.pem    - The server private key
+#
+# and then uncomment this next line
+# (vnc-tls 1)
+
+# The certificate dir can be pointed elsewhere..
+#
+# (vnc-x509-cert-dir vnc)
+
+# The server can be told to request & validate an x509
+# certificate from the client. Only clients with a cert
+# signed by the trusted CA will be able to connect. This
+# is more secure the password auth alone. Passwd auth can
+# used at the same time if desired. To enable client cert
+# checking uncomment this:
+#
+# (vnc-x509-verify 1)
+
+# The default keymap to use for the VM's virtual keyboard
+# when not specififed in VM's configuration
+#(keymap 'en-us')
+
+# Script to run when the label of a resource has changed.
+#(resource-label-change-script '')
+
+# Rotation count of qemu-dm log file.
+#(qemu-dm-logrotate-count 10)
+
+# Path where persistent domain configuration is stored.
+# Default is /var/lib/xend/domains/
+#(xend-domains-path /var/lib/xend/domains)
+
+# Number of seconds xend will wait for device creation and
+# destruction
+#(device-create-timeout 100)
+#(device-destroy-timeout 100)
+
+# When assigning device to HVM guest, we use the strict check for HVM guest by
+# default. (For PV guest, we use loose check automatically if necessary.)
+# When we assign device to HVM guest, if we meet with the co-assignment
+# issues or the ACS issue, we could try changing the option to 'no' -- however,
+# we have to realize this may incur security issue and we can't make sure the
+# device assignment could really work properly even after we do this.
+#(pci-passthrough-strict-check yes)
Index: trunk/shell/templates/etc/xen-tools/xen-tools.conf
===================================================================
--- trunk/shell/templates/etc/xen-tools/xen-tools.conf	(revision 0)
+++ trunk/shell/templates/etc/xen-tools/xen-tools.conf	(revision 18)
@@ -0,0 +1,341 @@
+##
+#  /etc/xen-tools/xen-tools.conf
+##
+#
+#  This is the global configuration file for the scripts included
+# within the xen-tools package.
+#
+#  For more details please see:
+#
+#        http://xen-tools.org/
+#
+##
+
+
+##
+#
+# File Format
+# -----------
+#
+#  Anything following a '#' character is ignored as a comment.
+#
+#  Otherwise the format of this file "key = value".  The value of
+# any keys in this file may be constructed via the output of a command.
+#
+#  For example:
+#
+#         kernel = /boot/vmlinuz-`uname -r`
+#
+##
+
+
+
+#
+##
+#  Output directory for storing loopback images.
+#
+#  If you choose to use loopback images, which are simple to manage but
+# slower than LVM partitions, then specify a directory here and uncomment
+# the line.
+#
+#  New instances will be stored in subdirectories named after their
+# hostnames.
+# 
+##
+# dir = /home/xen
+#
+
+#
+##
+#
+# If you don't wish to use loopback images then you may specify an 
+# LVM volume group here instead
+#
+##
+# lvm = vg0
+
+
+#
+##
+#
+#  Installation method.
+#
+#  There are four distinct methods which you may to install a new copy
+# of Linux to use in your Xen guest domain:
+#
+#   - Installation via the debootstrap command.
+#   - Installation via the rpmstrap command.
+#   - Installation via the rinse command.
+#   - Installation by copying a directory containing a previous installation.
+#   - Installation by untarring a previously archived image.
+#
+#  NOTE That if you use the "untar", or "copy" options you should ensure
+# that the image you're left with matches the 'dist' setting later in
+# this file.
+#
+#
+##
+#
+# 
+# install-method = [ debootstrap | rinse | rpmstrap | copy | tar ]
+#
+#
+install-method = debootstrap
+
+#
+# If you're using the "copy", or "tar" installation methods you must
+# need to specify the source location to copy from, or the source
+# .tar file to unpack.
+#
+# You may specify that with a line such as:
+#
+# install-source = /path/to/copy
+# install-source = /some/path/img.tar
+#
+#
+
+#
+##
+#  Command definitions.
+##
+#
+# The "rinse", and "rpmstrap" commands are hardwired into 
+# the script, but if you wish to modify the commands which are executed
+# when installing new systems by a "copy", "debootstrap", or "tar" method
+# you can do so here:
+#
+# (This allows you to install from a .tar.bz file, rather than a plain
+# tar file, use cdebootstrap, etc.)
+#
+# install-method = copy:
+# copy-cmd = /bin/cp -a $src/* $dest
+#
+# install-method = debootstrap:
+# debootstrap-cmd = /usr/sbin/debootstrap
+#
+# install-method = tar:
+# tar-cmd  = /bin/tar --numeric-owner -xvf $src
+#
+#
+
+
+
+#
+##
+#  Disk and Sizing options.
+##
+#
+size   = 4Gb      # Disk image size.
+memory = 128Mb    # Memory size
+swap   = __CLUSTER_SWAP_SIZE__    # Swap size
+__CLUSTER_NOSWAP__      # Don't use swap at all for the new system.
+fs     = ext3     # use the EXT3 filesystem for the disk image.
+dist   = `xt-guess-suite-and-mirror --suite` # Default distribution to install.
+image  = __CLUSTER_IMAGE__   # Specify sparse vs. full disk images.
+
+#
+#  See the README for currently supported and tested distributions. You can
+# either find it in the root directory of the unpacked source or, on Debian
+# and Ubuntu based systems, in /usr/share/doc/xen-tools/README.gz
+#
+
+
+
+##
+# Networking setup values.
+##
+
+#
+# Uncomment and adjust these network settings if you wish to give your
+# new instances static IP addresses.
+#
+# gateway    = 192.168.1.1
+# netmask    = 255.255.255.0
+# broadcast  = 192.168.1.255
+#
+# Uncomment this if you wish the images to use DHCP
+#
+# dhcp = 1
+
+#
+# Uncomment and adjust this setting if you wish to give your new
+# instances a specific nameserver.
+#
+# By default, nameserver is not set, and Dom0's /etc/resolv.conf will
+# be copied to guest.
+#
+# nameserver = 192.168.1.1
+#
+
+#
+# Setup bridge name for host vif. Usefull if you use bridged networking
+# for guests.
+#
+# bridge = xendmz
+#
+
+##
+# Misc options
+##
+
+#
+# Uncomment the following line if you wish to disable the caching
+# of downloaded .deb files when using debootstrap to install images.
+#
+# cache = no
+#
+
+#
+# The default cachedir is, /var/cache/apt/archives/, however if it
+# does not exist it will default to /var/cache/xen-tools/archives/
+# Uncomment the line below to set it to something else.
+#
+# cachedir = /var/cache/xen-tools/archives/
+#
+
+#
+# Uncomment the following line if you wish not to generate a new root
+# password for the new guest.
+#
+# genpass = 0
+#
+
+#
+# You can also change the password length by uncommenting and
+# changing the line below
+#
+# genpass_len = 8
+#
+
+#
+# You can yet change the hashing method to encrypt the generated
+# password by changing the line below.
+# Valid values : md5, sha256 and sha512.
+#
+# hash_method = sha256
+#
+
+#
+# Uncomment the following line if you wish to interactively setup a
+# new root password for images.
+#
+# passwd = 1
+#
+
+#
+# If you'd like all accounts on your host system which are not present
+# on the guest system to be copied over then uncomment the following line.
+#
+# accounts = 1
+#
+
+#
+# Default kernel and ramdisk to use for the virtual servers
+#
+kernel = /boot/vmlinuz-`uname -r`
+initrd = /boot/initrd.img-`uname -r`
+
+#
+#  The architecture to use when using debootstrap, rinse, or rpmstrap.
+#
+#  This is most useful on 64 bit host machines, for other systems it
+# doesn't need to be used.
+#
+arch = __CLUSTER_ARCH__
+
+
+#
+# The default mirror for debootstrap to install Debian-derived distributions
+#
+mirror = `xt-guess-suite-and-mirror --mirror`
+
+#
+# A mirror suitable for use when installing the Dapper release of Ubuntu.
+#
+# mirror = http://gb.archive.ubuntu.com/ubuntu/
+
+#
+#  If you like you could use per-distribution mirrors, which will
+# be more useful if you're working in an environment where you want
+# to regularly use multiple distributions. The following are the
+# default values used (for Debian the GeoIP feature is used, see
+# http://wiki.debian.org/DebianGeoMirror):
+#
+# mirror_sarge = http://archive.debian.org/debian
+# mirror_etch = http://archive.debian.org/debian
+# mirror_lenny = http://cdn.debian.net/debian
+# mirror_squeeze = http://cdn.debian.net/debian
+# mirror_wheezy = http://cdn.debian.net/debian
+# mirror_sid = http://cdn.debian.net/debian
+# mirror_dapper = http://archive.ubuntu.com/ubuntu
+# mirror_edgy = http://old-releases.ubuntu.com/ubuntu
+# mirror_feisty = http://old-releases.ubuntu.com/ubuntu
+# mirror_gutsy = http://old-releases.ubuntu.com/ubuntu
+# mirror_hardy = http://archive.ubuntu.com/ubuntu
+# mirror_intrepid = http://old-releases.ubuntu.com/ubuntu
+# mirror_karmic = http://archive.ubuntu.com/ubuntu
+# mirror_lucid = http://archive.ubuntu.com/ubuntu
+# mirror_maverick = http://archive.ubuntu.com/ubuntu
+# mirror_natty = http://archive.ubuntu.com/ubuntu
+
+
+#
+#  Filesystem options for the different filesystems we support.
+#
+ext3_options     = noatime,nodiratime,errors=remount-ro
+ext2_options     = noatime,nodiratime,errors=remount-ro
+xfs_options      = defaults
+reiserfs_options = defaults
+btrfs_options    = defaults
+
+#
+#  Uncomment if you wish newly created images to boot once they've been
+# created.
+#
+# boot = 1
+
+
+#
+#  If you're using the lenny or later version of the Xen guest kernel you will
+# need to make sure that you use 'hvc0' for the guest serial device,
+# and 'xvdX' instead of 'sdX' for serial devices.
+#
+#  You may specify the things to use here:
+#
+# serial_device = hvc0 #default
+# serial_device = tty1
+#
+# disk_device = xvda #default
+# disk_device = sda
+#
+
+
+#
+#  Here we specify the output directory which the Xen configuration
+# files will be written to, and the suffix to give them.
+#
+#  Historically xen-tools have created configuration files in /etc/xen,
+# and given each file the name $hostname.cfg.  If you want to change
+# that behaviour you may do so here.
+#
+#
+# output    = /etc/xen
+# extension = .cfg
+#
+
+#
+#  Here you can control weather your dom0's /etc/hosts file should be
+# appended with the new guest, and also if your dom0's /etc/hosts file
+# should be copied to the new guest.
+#
+#  Change the following options to 1 to set them
+# nohosts - don't touch the dom0's /etc/hosts file
+# copyhosts - copy the dom0's /etc/hosts to the guest
+#
+#  by default new guests ARE added to the dom0's /etc/hosts file
+# nohosts = 0 # default
+#
+#  by default the dom0's /etc/hosts IS NOT copied
+# copyhosts = 0 # default
+#
+
