Xen on Fedora 13: Difference between revisions
Line 15: | Line 15: | ||
<source lang="bash"> | <source lang="bash"> | ||
yum groupinstall "Development Libraries" | yum -y groupinstall "Development Libraries" | ||
yum groupinstall "Development Tools" | yum -y groupinstall "Development Tools" | ||
yum install transfig wget texi2html libaio-devel dev86 glibc-devel e2fsprogs-devel gitk mkinitrd iasl xz-devel bzip2-devel pciutils-libs pciutils-devel SDL-devel libX11-devel gtk2-devel bridge-utils PyXML qemu-common qemu-img mercurial | yum -y install transfig wget texi2html libaio-devel dev86 glibc-devel e2fsprogs-devel gitk mkinitrd iasl xz-devel bzip2-devel pciutils-libs pciutils-devel SDL-devel libX11-devel gtk2-devel bridge-utils PyXML qemu-common qemu-img mercurial | ||
yum install glibc-devel.i686 | yum -y install glibc-devel.i686 | ||
</source> | </source> | ||
Revision as of 01:22, 24 August 2010
Alteeve Wiki :: How To :: Xen on Fedora 13 |
Warning: This is currently a dumping ground for notes. DO NOT FOLLOW THIS DOCUMENT'S INSTRUCTIONS. Seriously, it could blow up your computer or cause winter to come early.
Building from Source
All of this is from here.
Install Requirements
Install:
yum -y groupinstall "Development Libraries"
yum -y groupinstall "Development Tools"
yum -y install transfig wget texi2html libaio-devel dev86 glibc-devel e2fsprogs-devel gitk mkinitrd iasl xz-devel bzip2-devel pciutils-libs pciutils-devel SDL-devel libX11-devel gtk2-devel bridge-utils PyXML qemu-common qemu-img mercurial
yum -y install glibc-devel.i686
Build from source
Note: These are the tools, not dom0.
From mercurial, stable tag.
Get version 4.0.0 (or newer, depending on what the latest stable is):
hg clone -r RELEASE-4.0.0 http://xenbits.xen.org/xen-4.0-testing.hg
Go into the directory and compile the tools:
cd xen-4.0-testing.hg
make xen
make tools
make stubdom
Install the tools (assuming compile worked):
make install-xen
make install-tools
make install-stubdom
Done.
dom0
From RPM
This uses a kernel built for Fedora 12, but it works on Fedora 13.
Add the repo:
cd /etc/yum.repos.d/
wget -c http://myoung.fedorapeople.org/dom0/myoung.dom0.repo
Edit the repo file and change the two enabled=0 entries to enabled=1.
Install the Xen dom0 kernel (edit the version number if needed).
yum install kernel-2.6.32.17-157.xendom0.fc12.x86_64
The entry in grub's /boot/grub/menu.lst won't work. You will need to edit it to look like this:
Note: Copy and modify the entry created by the RPM. Simply copying this entry will almost certainly not work!
title Xen 4.0, Linux kernel 2.6.32.17-157.xendom0.fc12.x86_64
root (hd0,0)
kernel /xen-4.0.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all
module /vmlinuz-2.6.32.17-157.xendom0.fc12.x86_64 ro root=/dev/mapper/vg01-lv_root rd_LVM_LV=vg01/lv_root rd_LVM_LV=vg01/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
module /initramfs-2.6.32.17-157.xendom0.fc12.x86_64.img
</span>
Add this to <span class="code">/etc/fstab</span>
<source lang="text">
xenfs /proc/xen xenfs defaults 0 0
Make cman and xend play nice
By default under Fedora 13, cman will start before xend. This is a problem because xend takes the network down as part of it's setup. This causes totem communication to fail which leads to fencing.
To avoid this, edit /etc/init.d/cman and tell it to start after xend by adding "xend" to Required-Start and Required-Stop boot facility lists.
When done, the cman LSB header should look like this:
vim /etc/init.d/cman
### BEGIN INIT INFO
# Provides: cman
# Required-Start: $network $time xend
# Required-Stop: $network $time xend
# Default-Start:
# Default-Stop:
# Short-Description: Starts and stops cman
# Description: Starts and stops the Cluster Manager set of daemons
### END INIT INFO
Lastly, remove and re-add the cman daemon and add the xend daemon to the start list:
chkconfig cman off
chkconfig cman on
chkconfig xend on
Done. You should be able to reboot into the dom0 kernel now.
Any questions, feedback, advice, complaints or meanderings are welcome. | |||
Alteeve's Niche! | Alteeve Enterprise Support | Community Support | |
© 2025 Alteeve. Intelligent Availability® is a registered trademark of Alteeve's Niche! Inc. 1997-2025 | |||
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions. |