%META:TOPICPARENT{}%
  • XenDualPIII - DECOMMISIONED Oct2006
    • Dual PIII 833MHz, 768Meg RAM, 40+30Gig HD
    • need to boot debian with acpi=off
    • 10.10.10.11
i'm trying out Xen to see if it will help me manage the testing of systems, and maybe later use the automatic migration.

Install log

  • installed minimal sarge from netinst CD
    • boot with linux26 apci-off
    • on 20Gig Ext3 partition, 2 Gig Swap, 18+30 Gig LVM
  • manually add static ip setup to /etc/network/interfaces * (this breaks the xen network bridging frown ) don't add a dhclient.conf alias to 10.10.10.11 to give us a static IP while still configuring everything else from DHCP (that way no configuration is required on the rather dumb adsl gateway router we have (Belkin54g from iinet)
  • add the following to /etc/apt/sources and allow the install to finish
  • apt-get install bridge-utils iproute python python-twisted gcc zlib1g zlib1g-dev
  • follow http://www.debian-administration.org/articles/304
  • apt-get install xen-tools reiserfsprogs xfsprogs lvm-common xfsdump attr dvhtool quot

create and run a new image

  • xen-create-image --hostname='vm01' --dir=/home/xen --size=5Gb --swap=128Mb --dhcp
  • xm create vm01.cfg -c to start it
  • xm shutdown vm01.cfg to shut it down

start the DomU?'s at boot

  • ln -s /etc/xen/vm01.cfg /etc/xen/auto

now to set up the Dom0 to forward tcp requests to the correct virtual host depending on domain name?

  • iptables is such a joy
  • i wanted to play with crossroads? later

Note:

  1. acpi=off is is important with the default 2.6 kernels, otherwise you loose network altogether
  2. setting a dhclient.conf alias on the Dom0 breaks the xen network scripts (as it creates an eth0.0)
  3. don't try to run the xen-tools from where you extracted them they expect to be installed, but don't complain loudly enough if it can't find the supporting scripts

Edit • Attach • Print version • History: r12 < r11 < r10 < r9 < r8 • Backlinks • Raw View • Raw edit • More topic actions...