Xen Dom0 on USB or SD - Revision history

Sertonix: link to udev/eudev article

2023-11-10T11:07:53Z

link to udev/eudev article

← Older revision		Revision as of 11:07, 10 November 2023
Line 73:		Line 73:
	</pre>		</pre>

	The last step is to configure startup services. We will need udev and xencommons to start at boot time:		The last step is to configure startup services. We will need [[udev]] and xencommons to start at boot time:

	<pre>		<pre>

Sertonix: update url

2023-08-25T21:47:55Z

update url

← Older revision		Revision as of 21:47, 25 August 2023
Line 63:		Line 63:
	</pre>		</pre>

	Change the UUID to the correct one, and add the necessary modules for your system.<BR>It's also a good idea to check [~~http~~://~~wiki~~.xen.org/~~wiki~~/~~Xen_Hypervisor_Boot_Options~~ Xen Boot options] and set, dom0_mem, dom0_vcpus_pin and dom0_max_vcpus.		Change the UUID to the correct one, and add the necessary modules for your system.<BR>It's also a good idea to check [https://xenbits.xen.org/docs/unstable/misc/xen-command-line.html Xen Boot options] and set, dom0_mem, dom0_vcpus_pin and dom0_max_vcpus.

	The next step is to load the necessary kernel modules for Xen. We will add them to /etc/modules so they will be loaded automatically at boot time:		The next step is to load the necessary kernel modules for Xen. We will add them to /etc/modules so they will be loaded automatically at boot time:

EvTheFuture: Typo

2022-12-22T09:04:58Z

Typo

← Older revision		Revision as of 09:04, 22 December 2022
Line 11:		Line 11:
	# ifup eth0		# ifup eth0
	</pre>		</pre>
	{{Note\| you may need to change <i>eth0</i> to the name of your ~~interfaces~~}}		{{Note\| you may need to change <i>eth0</i> to the name of your interface}}

	Continue by setting up the apk repositories:		Continue by setting up the apk repositories:

EvTheFuture: Added information about bringing up the network interface after configuration

2022-12-22T09:03:25Z

Added information about bringing up the network interface after configuration

← Older revision		Revision as of 09:03, 22 December 2022
Line 5:		Line 5:
	Once you finish installing Alpine Linux on your device, boot from it and configure your newly installed system:		Once you finish installing Alpine Linux on your device, boot from it and configure your newly installed system:

	Set up the network interfaces ~~and apk repositories~~:		Set up the network interfaces:

	<pre>		<pre>
	# setup-interfaces		# setup-interfaces
			# ifup eth0
			</pre>
			{{Note\| you may need to change <i>eth0</i> to the name of your interfaces}}

			Continue by setting up the apk repositories:

			<pre>
	# setup-apkrepos		# setup-apkrepos
	[...]		[...]

Bt129 at 11:42, 6 August 2021

2021-08-06T11:42:20Z

← Older revision		Revision as of 11:42, 6 August 2021
Line 1:		Line 1:
	This guide will show you how to perform a Xen Dom0 install on a USB or SD card, so you can have your Dom0 running from tmpfs. This has some benefits, but you will need a place to store your guests (virtual machines) and a syslog server to redirect the logs to.		This guide will show you how to perform a Xen Dom0 install on a USB device or SD card, so you can have your Dom0 running from tmpfs. This has some benefits, but you will need a place to store your guests (virtual machines) and a syslog server to redirect the logs to.

	The first step is to set up a basic usb or SD install, ~~to do this~~ boot from the Alpine install CD (minimal is fine) and follow one of the following guides: [[Create a Bootable USB]] or [[Create a Bootable Compact Flash]].		The first step is to set up a basic usb or SD install. To do that, boot from the Alpine install CD (minimal is fine) and follow one of the following guides:<BR>[[Create a Bootable USB]] or [[Create a Bootable Compact Flash]].

	Once you ~~finished~~ installing Alpine Linux on your device, boot from it and configure your newly installed system:		Once you finish installing Alpine Linux on your device, boot from it and configure your newly installed system:

	~~Setup~~ the network interfaces and apk repositories:		Set up the network interfaces and apk repositories:

	<pre>		<pre>
Line 23:		Line 23:
	</pre>		</pre>

	Now we have Xen installed, ~~but~~ we ~~will~~ need to modify the usb [[Bootloaders\|bootloader]] in order to load the Xen kernel. The first step is to remount /media/usb with write permissions:		Now that we have Xen installed, we need to modify the usb [[Bootloaders\|bootloader]] in order to load the Xen kernel. The first step is to remount /media/usb with write permissions:

	<pre>		<pre>
Line 36:		Line 36:
	</pre>		</pre>

	Now we have ~~all~~ the necessary files to boot Xen from the usb, it's time to change the bootloader and add a Xen entry~~, to~~ do so open /media/usb/syslinux.cfg with your favorite editor and add one of the following entries:		Now that we have the necessary files to boot Xen from the usb device, it's time to change the bootloader and add a Xen entry.<BR>
			To do so, open /media/usb/syslinux.cfg with your favorite editor and add one of the following entries:

	Normal boot:		Normal boot:
Line 45:		Line 46:
	</pre>		</pre>

	{{Note\|<nowiki>you might have to use alpine_dev=UUID=XXXX-XXXX:vfat ~~might work as well~~. UUID can be read using blkid.</nowiki>}}		{{Note\|<nowiki>you might have to use alpine_dev=UUID=XXXX-XXXX:vfat. UUID can be read using blkid.</nowiki>}}
	{{Note\|<nowiki>alternatively, ~~using~~ /media/UUID=XXX-XXXX instead of /media/usb, see /proc/mounts to ~~detected~~ where is your usb/cf card mounted.</nowiki>}}		{{Note\|<nowiki>alternatively, to use /media/UUID=XXX-XXXX instead of /media/usb, see /proc/mounts to detect where your usb/cf card is mounted.</nowiki>}}

	Serial console boot:		Serial console boot:
Line 55:		Line 56:
	</pre>		</pre>

	Change the UUID to the correct one, and add the necessary modules for your system. It's also a good idea to check [http://wiki.xen.org/wiki/Xen_Hypervisor_Boot_Options Xen Boot options] and set dom0_mem, dom0_vcpus_pin and dom0_max_vcpus ~~at least~~.		Change the UUID to the correct one, and add the necessary modules for your system.<BR>It's also a good idea to check [http://wiki.xen.org/wiki/Xen_Hypervisor_Boot_Options Xen Boot options] and set, dom0_mem, dom0_vcpus_pin and dom0_max_vcpus.

	The next step is to load the necessary kernel modules for Xen~~, we~~ will add them to /etc/modules, so they will be loaded automatically on boot:		The next step is to load the necessary kernel modules for Xen. We will add them to /etc/modules so they will be loaded automatically at boot time:

	<pre>		<pre>
Line 65:		Line 66:
	</pre>		</pre>

	The last step is to configure startup services~~, we~~ will need udev and xencommons at ~~least to be started on~~ boot:		The last step is to configure startup services. We will need udev and xencommons to start at boot time:

	<pre>		<pre>
Line 74:		Line 75:
	</pre>		</pre>

	~~Ok, now~~ you have a fully functional Xen install~~, it~~'s time to save your changes and boot into it.		Now you have a fully functional Xen install. It's time to save your changes and boot into it.

	<pre>		<pre>
Line 81:		Line 82:
	</pre>		</pre>

	~~Also remember~~ to configure at least one network bridge ~~following~~ the [[Bridge]] guide.		Remember to configure at least one network bridge. Follow the [[Bridge]] guide.

	== See also ==		== See also ==

Richtrabing: Updating syslinux configuration with new kernel, initrd and modloop filenames; some changes to setting up apk repos and some of the notes on edge cases.

2017-10-23T15:49:01Z

Updating syslinux configuration with new kernel, initrd and modloop filenames; some changes to setting up apk repos and some of the notes on edge cases.

← Older revision		Revision as of 15:49, 23 October 2017
Line 1:		Line 1:
	This guide will show you how to perform a Xen Dom0 install on a USB or SD card, so you can have your Dom0 running from tmpfs. This has some benefits, but you will need a place to store your guests (virtual machines) and a syslog server to redirect the logs to.		This guide will show you how to perform a Xen Dom0 install on a USB or SD card, so you can have your Dom0 running from tmpfs. This has some benefits, but you will need a place to store your guests (virtual machines) and a syslog server to redirect the logs to.

	The first step is to set up a basic usb or SD install, to do this boot from the Alpine install CD (minimal is fine) and follow one of the following guides: [[Create a Bootable USB]] or [[Create a Bootable Compact Flash]]. ~~Once you finished installing Alpine Linux on your device, boot from it and configure your newly installed system:~~		The first step is to set up a basic usb or SD install, to do this boot from the Alpine install CD (minimal is fine) and follow one of the following guides: [[Create a Bootable USB]] or [[Create a Bootable Compact Flash]].

	~~{{Note\|~~you ~~might have to edit /etc/~~apk/repositories ~~and change the first line so it points to /media/usb/apks.}}~~		Once you finished installing Alpine Linux on your device, boot from it and configure your newly installed system:

			Setup the network interfaces and apk repositories:

	<pre>		<pre>
	# setup-~~alpine~~		# setup-interfaces
			# setup-apkrepos
	[...]		[...]
	# apk update		# apk update
	</pre>		</pre>

			{{Note\| you may need to edit /etc/apk/repositories and change the first line so it points to /media/usb/apks.}}

	Now that you have your system properly configured, it's time to install Xen:		Now that you have your system properly configured, it's time to install Xen:
Line 19:		Line 24:

	Now we have Xen installed, but we will need to modify the usb [[Bootloaders\|bootloader]] in order to load the Xen kernel. The first step is to remount /media/usb with write permissions:		Now we have Xen installed, but we will need to modify the usb [[Bootloaders\|bootloader]] in order to load the Xen kernel. The first step is to remount /media/usb with write permissions:

	~~{{Note\|<nowiki>you might have to use /media/UUID=XXX-XXXX instead of /media/usb, see /proc/mounts to detected where is your usb/cf card mounted.</nowiki>}}~~

	<pre>		<pre>
Line 39:		Line 42:
	LABEL xen		LABEL xen
	KERNEL /boot/mboot.c32		KERNEL /boot/mboot.c32
	APPEND /boot/xen.gz --- /boot/~~grsec~~ alpine_dev=~~UUID=XXXX-XXXX~~:vfat modules=loop,squashfs,sd-mod,usb-storage modloop=/boot/~~grsec.~~modloop~~.squashfs~~ --- /boot/~~grsec.gz~~		APPEND /boot/xen.gz --- /boot/vmlinuz-hardened alpine_dev=usbdisk:vfat modules=loop,squashfs,sd-mod,usb-storage modloop=/boot/modloop-hardened --- /boot/initramfs-hardened
	</pre>		</pre>

			{{Note\|<nowiki>you might have to use alpine_dev=UUID=XXXX-XXXX:vfat might work as well. UUID can be read using blkid.</nowiki>}}
			{{Note\|<nowiki>alternatively, using /media/UUID=XXX-XXXX instead of /media/usb, see /proc/mounts to detected where is your usb/cf card mounted.</nowiki>}}

	Serial console boot:		Serial console boot:
Line 46:		Line 52:
	LABEL xen		LABEL xen
	KERNEL /boot/mboot.c32		KERNEL /boot/mboot.c32
	APPEND /boot/xen.gz com1=115200,8n1 console=com1 --- /boot/~~grsec~~ alpine_dev=~~UUID=XXXX-XXXX~~:vfat modules=loop,squashfs,sd-mod,usb-storage modloop=/boot/~~grsec.~~modloop~~.squashfs~~ --- /boot/~~grsec.gz~~		APPEND /boot/xen.gz com1=115200,8n1 console=com1 --- /boot/vmlinuz-hardened alpine_dev=usbdisk:vfat modules=loop,squashfs,sd-mod,usb-storage modloop=/boot/modloop-hardened --- /boot/initramfs-hardened
	</pre>		</pre>

John3-16: Added internal link to Bootloaders

2017-09-15T00:12:53Z

Added internal link to Bootloaders

← Older revision		Revision as of 00:12, 15 September 2017
Line 18:		Line 18:
	</pre>		</pre>

	Now we have Xen installed, but we will need to modify the usb bootloader in order to load the Xen kernel. The first step is to remount /media/usb with write permissions:		Now we have Xen installed, but we will need to modify the usb [[Bootloaders\|bootloader]] in order to load the Xen kernel. The first step is to remount /media/usb with write permissions:

	{{Note\|<nowiki>you might have to use /media/UUID=XXX-XXXX instead of /media/usb, see /proc/mounts to detected where is your usb/cf card mounted.</nowiki>}}		{{Note\|<nowiki>you might have to use /media/UUID=XXX-XXXX instead of /media/usb, see /proc/mounts to detected where is your usb/cf card mounted.</nowiki>}}

Donoban: xend was removed on newest xen versions.

2016-04-26T07:55:12Z

xend was removed on newest xen versions.

← Older revision		Revision as of 07:55, 26 April 2016
Line 66:		Line 66:
	# rc-update add xenstored		# rc-update add xenstored
	# rc-update add xenconsoled		# rc-update add xenconsoled
	~~</pre>~~

	~~If you need the xm toolstack, also add xend to startup services:~~

	~~<pre>~~
	~~# rc-update add xend~~
	</pre>		</pre>

Andre at 13:24, 10 October 2014

2014-10-10T13:24:42Z

← Older revision		Revision as of 13:24, 10 October 2014
Line 11:		Line 11:
	</pre>		</pre>

	Now ~~you~~ that you have your system properly configured, it's time to install Xen:		Now that you have your system properly configured, it's time to install Xen:

	<pre>		<pre>

Ben: Question about missing xen.gz

2013-06-02T00:43:16Z

Question about missing xen.gz

← Older revision		Revision as of 00:43, 2 June 2013
Line 14:		Line 14:

	<pre>		<pre>
			# Should this not be apk add xen xen-hypervisor ?
	# apk add xen		# apk add xen
	</pre>		</pre>