Xen

Xen virtual console device driver.

Xen driver for secondary virtual consoles.

This driver implements the front-end of the Xen virtual block device
driver.  It communicates with a back-end driver in another domain
which drives the actual block device.

The block-device backend driver allows the kernel to export its block
devices to other guests via a high-performance shared-memory
interface.

The corresponding Linux frontend driver is enabled by the
CONFIG_XEN_BLKDEV_FRONTEND configuration option.

The backend driver attaches itself to a any block device specified
in the XenBus configuration. There are no limits to what the block
device as long as it has a major and minor.

If you are compiling a kernel to run in a Xen block backend driver
domain (often this is domain 0) you should say Y here. To compile this
driver as a module, chose M here: the module will be called
xen-blkback.

This driver provides support for Xen paravirtual network
devices exported by a Xen network driver domain (often domain 0).

The corresponding Linux backend driver is enabled by the
CONFIG_XEN_NETDEV_BACKEND option.

If you are compiling a kernel for use as Xen guest, you
should say Y here. To compile this driver as a module, chose
M here: the module will be called xen-netfront.

This driver allows the kernel to act as a Xen network driver domain
which exports paravirtual network devices to other Xen domains. These
devices can be accessed by any operating system that implements a
compatible front end.

The corresponding Linux frontend driver is enabled by the
CONFIG_XEN_NETDEV_FRONTEND configuration option.

The backend driver presents a standard network device endpoint for
each paravirtual network device to the driver domain network stack.
These can then be bridged or routed etc in order to provide full
network connectivity.

If you are compiling a kernel to run in a Xen network driver domain
(often this is domain 0) you should say Y here. To compile this driver
as a module, chose M here: the module will be called xen-netback.

The balloon driver allows the Xen domain to request more memory from
the system to expand the domain's memory allocation, or alternatively
return unneeded memory to the system.

Scrub pages before returning them to the system for reuse by
other domains.  This makes sure that any confidential data is not
accidentally visible to other domains.  Is it more secure, but
slightly less efficient. If in doubt, say yes.

The evtchn driver allows a userspace process to trigger event
channels and to receive notification of an event channel
firing. If in doubt, say yes.

Support for backend device drivers that provide I/O services
to other virtual machines.

The xen filesystem provides a way for domains to share information
with each other and with the hypervisor. For example, by reading and
writing the "xenbus" file, guests may pass arbitrary information to
the initial domain. If in doubt, say yes.

The old xenstore userspace tools expect to find "xenbus" under
/proc/xen, but "xenbus" is now found at the root of the xenfs
filesystem.  Selecting this causes the kernel to create
the compatibility mount point /proc/xen if it is running on a xen
platform. If in doubt, say yes.

Create entries under /sys/hypervisor describing the Xen hypervisor
environment.  When running native or in another virtual environment,
/sys/hypervisor will still be present, but will have no xen contents.

Allows userspace processes to use grants.

Allows userspace processes to create pages with access granted
to other domains. This can be used to implement frontend drivers or as
part of an inter-domain shared memory channel.

The PCI device backend driver allows the kernel to export arbitrary
PCI devices to other guests. If you select this to be a module, you
will need to make sure no other driver has bound to the device(s)
you want to make visible to other guests.

The parameter "passthrough" allows you specify how you want the PCI
devices to appear in the guest. You can choose the default (0) where
PCI topology starts at 00.00.0, or (1) for passthrough if you want
the PCI devices topology appear the same as in the host.

The "hide" parameter (only applicable if backend driver is compiled
into the kernel) allows you to bind the PCI devices to this module
from the default device drivers. The argument is the list of PCI BDFs:
xen-pciback.hide=(03:00.0)(04:00.0)

If in doubt, say m.

This ACPI processor uploads Power Management information to the Xen
hypervisor.

To do that the driver parses the Power Management data and uploads
said information to the Xen hypervisor. Then the Xen hypervisor can
select the proper Cx and Pxx states. It also registers itself as the
SMM so that other drivers (such as ACPI cpufreq scaling driver) will
not load.

To compile this driver as a module, choose M here: the module will be
called xen_acpi_processor  If you do not know what to choose, select
M here. If the CPUFREQ drivers are built in, select Y here.

# /etc/init.d/xendomains status
Name                  ID   Mem VCPUs  State  Time(s)
Domain-0              0  2048     4  r----- 6.8

rc-update add xendomains default
cd /etc/xen/auto
ln -s /xen/conf/mylilVM.conf

mkdir -p /xen/kernels
cp /boot/vmlinuz-3.14.xed-xen /xen/kernels/
mkdir /xen/disks
dd if=/dev/zero of=/xen/disks/ext4-gen2-core.img bs=1M count=10240
mkfs.ext4 -F -L XENGUEST  /xen/disks/ext4-gen2-core.img
mkdir /mnt/img1
mount -o loop,rw /xen/disks/ext4-gen2-core /mnt/img1
mkdir /xen/configs

mkdir /mnt/img1
mount -o loop,rw /xen/disks/ext4-gen2-core.img /mnt/img1
wget -O - ftp://ftp.gtlib.gatech.edu/pub/gentoo/releases/amd64/current-iso/stage3-amd64-20140515.tar.bz2 | tar -xjf - -C /mnt/img1
mount -t proc none /mnt/img1/proc/
mount --rbind /dev /mnt/img1/dev/
cp -L /etc/resolv.conf /mnt/img1/etc/
chmod 644 /mnt/img1/etc/resolv.conf
cp /etc/portage/make.conf /mnt/img1/etc/portage/
mv /mnt/img1/etc/fstab /mnt/img1/etc/fstab.orig
echo "/dev/sda1   /  ext3  noatime 0 1" > /mnt/img1/etc/fstab
time rsync -aP /usr/portage /mnt/img1/usr/
chroot /mnt/img1 /bin/bash
echo America/Los_Angeles > /etc/timezone
ln -sf /usr/share/zoneinfo/America/Los_Angeles /etc/localtime
date MMDDhhmmYYYY.ss
time emerge --sync
time emerge -v1 portage
time emerge -v @system
time nice emerge -vuDN vim ssh vixie-cron metalog bc htop gentoolkit app-misc/screen lftp ntp
eselect editor set vim
vi /etc/profile
emerge -C nano
passwd

dns_servers="99.99.0.252"
bridge_br0="enp2s0"
config_br0="99.99.243.113 netmask 255.255.255.224"
routes_br0="default via 99.99.243.97"