My desktop just grew by two 500GB Western Digital Caviar drives. Having installed those, I loaded Gutsy-AMD64 on one using LVM. The partition schema is as follows:

Drive: 500GB #1
Volume Group: server1
Volumes:
	swap_1 - 6GB - swap
	root_1 - 30GB - ext3 - mounted as /
	home_1 - 20GB - ext3 - mounted as /home/
Free space: ~398GB

500GB number two will probably wind up being a RAID mirror via my motherboard. This LVM layout allows me to dynamically allocate space for the many potential Xen DomUs I create.

To install Xen on Gutsy-AMD64 desktop version:
sudo apt-get install ubuntu-xen-desktop-amd64


My /etc/xen-tools/xen-tools.conf:

lvm = server1               # LVM volume group to use
install-method = debootstrap
size   = 4Gb                # Disk image size.
memory = 256Mb              # Memory size
swap   = 512Mb              # Swap size
fs     = ext3               # use the EXT3 filesystem for the disk image.
dist   = gutsy              # Default distribution to install.
gateway = 10.0.1.1
netmask = 255.255.255.0
cache = yes                 # Cache downloaded debs
passwd = 1                  # Set up root password during creation
kernel = /boot/vmlinuz-`uname -r`
initrd = /boot/initrd.img-`uname -r`
arch = amd64                # 64-bit domU
mirror = http://us.archive.ubuntu.com/ubuntu
ext3_options = noatime,nodiratime,errors=remount-ro
serial_device = tty1

My /etc/xen/xend-config.sxp:

(xend-tcp-xmlrpc-server yes)
(xend-relocation-server yes)
(xend-relocation-server yes)
(xend-tcp-xmlrpc-server-address '')
(xend-tcp-xmlrpc-server-port 8006)
(xend-relocation-port 8002)
(xend-relocation-address '')
(xend-relocation-hosts-allow '')
(network-script network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)
(vncpasswd '')

Edit the file /etc/xen-tools/xm.tmpl as follows, around line 19:

memory      = '{$memory}'
extra='xencons=tty'

To generate one Gutsy-based DomU:
xen-create-image --hostname=gutsy1 --ip=10.0.1.3 --verbose --force

To boot created DomU:
xm create gutsy1.cfg -c