Xen on Fedora 13 - Revision history

Digimer at 00:17, 9 September 2010

2010-09-09T00:17:33Z

← Older revision		Revision as of 00:17, 9 September 2010
Line 1:		Line 1:
	{{howto_header}}		{{howto_header}}

	'''~~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~~.		'''''NOTICE''''': This section has been moved to [[Two_Node_Fedora_13_Cluster_-_Xen-Based_Virtual_Machine_Host_on_DRBD%2BCLVM#Setting_up_Xen.27s_dom0\|Two Node Fedora 13 Cluster - Xen-Based Virtual Machine Host on DRBD+CLVM]]. This will be removed shortly.

	----		----

Digimer: /* dom0 */

2010-09-07T19:47:20Z

dom0

← Older revision		Revision as of 19:47, 7 September 2010
Line 62:		Line 62:
	<source lang="bash">		<source lang="bash">
	title Xen 3.4.x, Linux kernel 2.6.32.21-167.xendom0.fc12.x86_64		title Xen 3.4.x, Linux kernel 2.6.32.21-167.xendom0.fc12.x86_64
	root (hd0,0)		root (hd0,2)
	kernel /xen.gz dom0_mem=1024M		kernel /xen.gz dom0_mem=1024M
	module /vmlinuz-2.6.32.21-167.xendom0.fc12.x86_64 ...		module /vmlinuz-2.6.32.21-167.xendom0.fc12.x86_64 ...

Digimer: /* dom0 */

2010-09-07T19:00:14Z

dom0

← Older revision		Revision as of 19:00, 7 September 2010
Line 64:		Line 64:
	root (hd0,0)		root (hd0,0)
	kernel /xen.gz dom0_mem=1024M		kernel /xen.gz dom0_mem=1024M
	module /vmlinuz-2.6.32.21-167.xendom0.fc12.x86_64 ~~ro root=/dev/mapper/vg_01-lv_root rd_MD_UUID=4f48439e:39ec22e8:a6154857:c340036f rd_LVM_LV=vg_01/lv_root rd_LVM_LV=vg_01/lv_swap rd_NO_LUKS rd_NO_DM LANG=en_US~~.~~UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us~~		module /vmlinuz-2.6.32.21-167.xendom0.fc12.x86_64 ...
	module /initramfs-2.6.32.21-167.xendom0.fc12.x86_64.img		module /initramfs-2.6.32.21-167.xendom0.fc12.x86_64.img
	</source>		</source>

Digimer: /* dom0 */

2010-09-07T18:58:35Z

dom0

← Older revision		Revision as of 18:58, 7 September 2010
Line 50:		Line 50:

	<source lang="bash">		<source lang="bash">
	yum install kernel-2.6.32.21-167.xendom0.fc12.x86_64~~.rpm~~		yum install kernel-2.6.32.21-167.xendom0.fc12.x86_64
	</source>		</source>

	The entry in grub's <span class="code">/boot/grub/menu.lst</span> won't work. You will need to edit it to look like this:		The entry in grub's <span class="code">/boot/grub/menu.lst</span> 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! Your <span class="code">root=</span> is likely different and your <span class="code">rd_MD_UUID=</span> will definitely be different, even on the same machine across installs. Generally speaking, what follows the <span class="code">kernel /vmlinuz-2.6.32.17-~~157~~.xendom0.fc12.x86_64 ...</span> entry made by the dom0 kernel can be copied after the <span class="code">module /vmlinuz-2.6.32.17-~~157~~.xendom0.fc12.x86_64 ...</span> entry in the example below.		'''Note''': Copy and modify the entry created by the RPM. Simply copying this entry will almost certainly not work! Your <span class="code">root=</span> is likely different and your <span class="code">rd_MD_UUID=</span> will definitely be different, even on the same machine across installs. Generally speaking, what follows the <span class="code">kernel /vmlinuz-2.6.32.21-167.xendom0.fc12.x86_64 ...</span> entry made by the dom0 kernel can be copied after the <span class="code">module /vmlinuz-2.6.32.21-167.xendom0.fc12.x86_64 ...</span> entry in the example below.

	<source lang="bash">		<source lang="bash">
Line 61:		Line 61:
	</source>		</source>
	<source lang="bash">		<source lang="bash">
	title Xen 3.4.x, Linux kernel 2.6.32.17-~~157~~.xendom0.fc12.x86_64		title Xen 3.4.x, Linux kernel 2.6.32.21-167.xendom0.fc12.x86_64
	root (hd0,0)		root (hd0,0)
	kernel /xen.gz dom0_mem=1024M		kernel /xen.gz dom0_mem=1024M
	module /vmlinuz-2.6.32.17-~~157~~.xendom0.fc12.x86_64 ro root=/dev/mapper/vg_01-lv_root rd_MD_UUID=4f48439e:39ec22e8:a6154857:c340036f rd_LVM_LV=vg_01/lv_root rd_LVM_LV=vg_01/lv_swap rd_NO_LUKS rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us		module /vmlinuz-2.6.32.21-167.xendom0.fc12.x86_64 ro root=/dev/mapper/vg_01-lv_root rd_MD_UUID=4f48439e:39ec22e8:a6154857:c340036f rd_LVM_LV=vg_01/lv_root rd_LVM_LV=vg_01/lv_swap rd_NO_LUKS rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us
	module /initramfs-2.6.32.17-~~157~~.xendom0.fc12.x86_64.img		module /initramfs-2.6.32.21-167.xendom0.fc12.x86_64.img
	</source>		</source>

Digimer: /* dom0 */

2010-09-07T18:57:19Z

dom0

← Older revision		Revision as of 18:57, 7 September 2010
Line 50:		Line 50:

	<source lang="bash">		<source lang="bash">
	yum install kernel-2.6.32.17-~~157~~.xendom0.fc12.x86_64		yum install kernel-2.6.32.21-167.xendom0.fc12.x86_64.rpm
	</source>		</source>

Digimer: /* Make xend play nice with clustering */

2010-09-01T23:52:43Z

Make xend play nice with clustering

@@ Line 161: / Line 161: @@
 By default under Fedora 13, <span class="code">cman</span> will start before <span class="code">xend</span>. This is a problem because <span class="code">xend</span> takes the network down as part of it's setup. This causes [[totem]] communication to fail which leads to fencing.
-To avoid this, edit <span class="code">/etc/init.d/xend</span> and tell it to start earlier than position <span class="code">98</span>. This is done by changing the line <span class="code">chkconfig: 2345 98 01</span> to <span class="code">chkconfig: 2345 11 98</span>.
+To avoid this, edit <span class="code">/etc/init.d/xend</span> and tell it to start earlier than position <span class="code">98</span>. This is done by changing the line <span class="code">chkconfig: 2345 98 01</span> to <span class="code">chkconfig: 2345 11 98</span>. We also don't want it to stop until <span class="code">cman</span> has stopped. We accomplish this by adding <span class="code">cman</span> to the <span class="code">Required-Stop</span> line.
 <source lang="bash">
@@ Line 179: / Line 179: @@
 # Required-Start:    $syslog $remote_fs
 # Should-Start:
-# Required-Stop:     $syslog $remote_fs
+# Required-Stop:     $syslog $remote_fs cman
 # Should-Stop:
 # Default-Start:     3 4 5
@@ Line 189: / Line 189: @@
 </source>
-Lastly, remove and re-add the <span class="code">xend</span> daemon in the start list:
+With <span class="code">xend</span> set to start at a position lower than <span class="code">98</span>, we now have room for <span class="code">chkconfig</span> to put other daemons after it in the start order. First and foremost, we now need to tell <span class="code">cman</span> to not start until after <span class="code">xend</span> is up.
 <source lang="bash">
-chkconfig xend off
+#!/bin/bash
 chkconfig xend on
 </source>

Digimer at 21:10, 1 September 2010

2010-09-01T21:10:46Z

← Older revision		Revision as of 21:10, 1 September 2010
Line 54:		Line 54:

	The entry in grub's <span class="code">/boot/grub/menu.lst</span> won't work. You will need to edit it to look like this:		The entry in grub's <span class="code">/boot/grub/menu.lst</span> 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! Your <span class="code">root=</span> is likely different and your <span class="code">rd_MD_UUID=</span> will definitely be different, even on the same machine across installs. Generally speaking, what follows the <span class="code">kernel /vmlinuz-2.6.32.17-157.xendom0.fc12.x86_64 ...</span> entry made by the dom0 kernel can be copied after the <span class="code">module /vmlinuz-2.6.32.17-157.xendom0.fc12.x86_64 ...</span> entry in the example below.

	<source lang="bash">		<source lang="bash">

Digimer: /* dom0 */

2010-09-01T21:09:41Z

dom0

← Older revision		Revision as of 21:09, 1 September 2010
Line 134:		Line 134:
	</source>		</source>

	'''Note''': Copy and modify the entry created by the RPM. Simply copying this entry will almost certainly not work!		'''Note''': Copy and modify the entry created by the RPM. Simply copying this entry will almost certainly not work! Your <span class="code">root=</span> is likely different and your <span class="code">rd_MD_UUID=</span> will definitely be different, even on the same machine across installs. Generally speaking, what follows the <span class="code">kernel /vmlinuz-2.6.32.17-157.xendom0.fc12.x86_64 ...</span> entry made by the dom0 kernel can be copied after the <span class="code">module /vmlinuz-2.6.32.17-157.xendom0.fc12.x86_64 ...</span> entry in the example below.

	'''Xen 4.0.1''':		'''Xen 4.0.1''':
Line 142:		Line 142:
	root (hd0,0)		root (hd0,0)
	kernel /xen-4.0.1.gz dom0_mem=1024M		kernel /xen-4.0.1.gz dom0_mem=1024M
	module /vmlinuz-2.6.32.17-157.xendom0.fc12.x86_64 ro root=/dev/mapper/vg_01-lv_root rd_MD_UUID=~~4f48439e:39ec22e8:a6154857:c340036f~~ rd_LVM_LV=vg_01/lv_root rd_LVM_LV=vg_01/lv_swap rd_NO_LUKS rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet		module /vmlinuz-2.6.32.17-157.xendom0.fc12.x86_64 ro root=/dev/mapper/vg_01-lv_root rd_MD_UUID=<your UUID> rd_LVM_LV=vg_01/lv_root rd_LVM_LV=vg_01/lv_swap rd_NO_LUKS 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		module /initramfs-2.6.32.17-157.xendom0.fc12.x86_64.img
	</source>		</source>

Digimer: /* Creating domU VMs */

2010-09-01T20:29:28Z

Creating domU VMs

← Older revision		Revision as of 20:29, 1 September 2010
Line 202:		Line 202:
	= Creating domU VMs =		= Creating domU VMs =

	~~Once~~ you ~~have ..~~.		If you are running on top of DRBD in a cluster, please see "[[DRBD on Fedora 13]]" before proceeding.

			'''ToDo'''

	{{footer}}		{{footer}}

Digimer: /* Make cman and xend play nice */

2010-09-01T20:27:41Z

Make cman and xend play nice

← Older revision		Revision as of 20:27, 1 September 2010
Line 155:		Line 155:
	</source>		</source>

	= Make ~~cman and~~ xend play nice =		= Make xend play nice with clustering =

	By default under Fedora 13, <span class="code">cman</span> will start before <span class="code">xend</span>. This is a problem because <span class="code">xend</span> takes the network down as part of it's setup. This causes [[totem]] communication to fail which leads to fencing.		By default under Fedora 13, <span class="code">cman</span> will start before <span class="code">xend</span>. This is a problem because <span class="code">xend</span> takes the network down as part of it's setup. This causes [[totem]] communication to fail which leads to fencing.

	To avoid this, edit <span class="code">/etc/init.d/~~cman~~</span> and tell it to start ~~after~~ <span class="code">~~xend~~</span> by ~~adding "~~<span class="code">~~xend~~</span>" to <span class="code">~~Required-Start</span> and <span class="code">Required-Stop~~</span> ~~boot facility lists~~.		To avoid this, edit <span class="code">/etc/init.d/xend</span> and tell it to start earlier than position <span class="code">98</span>. This is done by changing the line <span class="code">chkconfig: 2345 98 01</span> to <span class="code">chkconfig: 2345 11 98</span>.

	~~When done, the <span class="code">cman</span> LSB header should look like this:~~

	<source lang="bash">		<source lang="bash">
	vim /etc/init.d/~~cman~~		vim /etc/init.d/xend
	~~</source>~~
	~~<source lang="bash">~~
	~~### 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~~
	~~</source>~~

	Next, we need to tell <span class="code">xend</span> not to default to start position <span class="code">98</span>. Without this change, services we want to start after <span class="code">xend</span> (<span class="code">xman</span> -> <span class="code">drbd</span> -> <span class="code">clvmd</span> -> <span class="code">xendomains</span>) would all fall to start position <span class="code">99</span>. This would mean that the start order would become dependent on the daemon name, which is a bad idea. For example, this would cause <span class="code">clvmd</span> to start before <span class="code">cman</span>, which we don't want.

	~~Change <span class="code">chkconfig: 2345 98 01</span> to <span class="code">chkconfig: 2345 11 98</span>.~~

	~~<source lang="bash">~~
	~~vim /etc/init.d/drbd~~
	</source>		</source>
	<source lang="bash">		<source lang="bash">
			#!/bin/bash
			#
			# xend Script to start and stop the Xen control daemon.
			#
			# Author: Keir Fraser <keir.fraser@cl.cam.ac.uk>
			#
	# chkconfig: 2345 11 98		# chkconfig: 2345 11 98
	# description: Starts and stops the Xen control daemon.		# description: Starts and stops the Xen control daemon.
	### BEGIN INIT INFO		### BEGIN INIT INFO
	# Provides: xend		# Provides: xend
	# Required-Start: $syslog		# Required-Start: $syslog $remote_fs
	# Should-Start: ~~$remote_fs~~		# Should-Start:
	# Required-Stop: $syslog		# Required-Stop: $syslog $remote_fs
	# Should-Stop: ~~$remote_fs~~		# Should-Stop:
	# Default-Start: 3 4 5		# Default-Start: 3 4 5
	# Default-Stop: 0 1 2 6		# Default-Stop: 0 1 2 6
Line 202:		Line 187:
	</source>		</source>

	Lastly, remove and re-add the ~~<span class="code">cman</span> and~~ <span class="code">xend</span> daemon to the start list:		Lastly, remove and re-add the <span class="code">xend</span> daemon in the start list:

	~~'''Note'''': This has extra entries to make sure all relevant entries are sorted when re-added. If you do not have some of the daemons listed below installed yet, simply skip them.~~

	<source lang="bash">		<source lang="bash">
	chkconfig xend ~~off; chkconfig cman off; chkconfig drbd off; chkconfig clvmd off; chkconfig xendomains off; chkconfig gfs2~~ off		chkconfig xend off
	chkconfig xend ~~on; chkconfig cman on; chkconfig drbd on; chkconfig clvmd on; chkconfig xendomains on; chkconfig gfs2~~ on		chkconfig xend on
	</source>		</source>