Setting up a xen server

i've configured and played with xen on laze.

to set create the parent server (out of date?)

as long as you don't read the documentation(at least, i found it very confusing and intimidating), it's actually not much more difficult than vserver.

apt-get install xen-linux-system-2.6.18-3-xen-vserver-686 xen-tools libc6-xen

(alternately, you could install xen-linux-system-2.6.18-3-xen-686, or xen-linux-system-2.6.18-3-xen-vserver-686)

martin noticed that you likely will need to edit /etc/xen-tools/xen-tools.conf:

kernel = /boot/vmlinuz-2.6.18-3-xen-vserver-686
initrd = /boot/initrd.img-2.6.18-3-xen-vserver-686

to match the kernel you have installed

[1]

i've been unable to verify if this helps at all, but:

[2]

echo 'hwcap 0 nosegneg' > /etc/ld.so.conf.d/libc6-xen.conf

appears to not help at all, at least on laze.

When it's all finished, review values in /etc/xen-tools/xen-tools.conf ???

to create an instance on the parent server

you create new xen instances with:

sudo xen-create-image --hostname NAME --debootstrap --mirror http://mirrors.kernel.org/debian --dist etch --ip IP_ADDRESS

Prepare to wait awhile while this all installs. Kill your time by editing the appropriate dns files and the purpose file in the ass svn project, check your work, and then commit the changes. Then ssh into dns1 and:

cd /var/cache/bind
svn update
/etc/init.d/bind9 reload
sudo /etc/init.d/bind9 reload

Continue waiting for your install to happen. Go help out at the Front Desk or something.

It will ask for a root password. Have one prepared and ready to go.

Your configuration file will be in:

/etc/xen/NAME.cfg

Check to see that it is there.

To start the xen instance:

xm create /etc/xen/NAME.cfg

To list the running xen instances and how much resources they're using:

xm list

AAAAACK! It seems to have screwed up all networking on all instances on that xen server.

Cannot log in at this point. What step is missing? Should we do the following? (Seems wrong.)

To get networking to work, i had to uncomment in /etc/xen/xend-config.sxp:

(network-script network-bridge) 

and then restart xend:

invoke-rc.d xend restart

reclaim memory for the host machine stolen by stopped xen instances:

xm mem-set Domain-0 700

(for 700MB of ram)

To get to a login screen on the vm, either ssh in, or:

xm console NAME

To get out of the instance, the secret keystroke is Ctrl-].

There's some mechanism to start instances at boot time i haven't yet explored, but it doesn't sound difficult.