Ugo Bellavance wrote :
[...]
> In fact... yes. This is good advice, but I was wondering about the host
> node, not the VMs.
Oh, then a few more tips :-)
Install a minimal system, then install "xen" and "kernel-xen". If you
do it this way, don't forget to edit /etc/sysconfig/kernel so that you
have "kernel-xen" as your default kernel after updates are installed.
To save disk space and download when updates are available, you might
also want to remove all "kernel" packages and keep only "kernel-xen".
For the network, if you have a trivial setup (i.e. one network
interface), then let Xen handle everything for you. If you have two or
more network interfaces, then install a quick script like this one
as /etc/xen/scripts/network-bridges :
#!/bin/sh
dir=$(dirname "$0")
$dir/network-bridge $1 vifnum=0
$dir/network-bridge $1 vifnum=1
Then edit xend-config.sxp to use that instead of network-bridge
directly. If you have a more complex network setup (VLANs and/or
bridges), then use /bin/false and configure all of the bridges you want
Xen to use through ifcfg-* files.
>From here, what I usually do is deploy all of my /etc/xen/<host> files
based on a skeleton which looks like this :
--
# Xen Configuration File
name = "myhost"
memory = 256
maxmem = 512
vcpus = 2
disk = [ "phy:/dev/vg0/myhost,xvda,w",
"phy:/dev/vg0/swapmyhost,xvdb,w", ]
vif = [ "mac=00:16:3e:14:8e:de,bridge=xenbr0",
"mac=00:16:3e:14:8e:df,bridge=xenbr1", ]
uuid = "148ede92-7277-6907-4b2b-5172fe73b115"
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
--
Where the uuid is the md5sum of myhost's FQDN's string (i.e. echo
myhost.mydomain | md5sum) in order to have it be unique yet
predictable, and I use the first 6 characters for the primary MAC
address, then increment from there.
The vg0 LVs are pre-created and the minimal install image I previously
mentioned is rsync'ed there using the host. Just make sure you have
a /.autorelabel file in the guest and it'll take care of selinux when
it first boots.
I also make sure I have a /var/lib/xen/save filesystem mounted on the
host, which is the same size as the amount of RAM, for the xendomains
service to be able to save all running Guests properly.
The last thing to not forget is to create a /etc/xen/auto/myhost
-> ../myhost symlink for the guest to start automatically when the
host boots.
Of course, cobbler and koan are also worth looking into. But last I
did, they still had some limitations that were blockers for me.
HTH,
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 8 (Werewolf) - Linux kernel 2.6.24.4-64.fc8
Load : 0.51 0.24 0.13
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
