NetBSD as a Xen domU - Revision history

Jeff at 03:18, 6 September 2009

Jeff — Sun, 06 Sep 2009 03:18:43 GMT

←Older revision		Revision as of 03:18, 6 September 2009
Line 64:		Line 64:

	http://www.netbsd.org/ports/xen/howto.html		http://www.netbsd.org/ports/xen/howto.html
		+
		+	----
		+	[[User:Jeff\|Jeff]]

Jeff at 07:16, 1 August 2009

Jeff — Sat, 01 Aug 2009 07:16:55 GMT

←Older revision		Revision as of 07:16, 1 August 2009
Line 54:		Line 54:

	:<pre> disk = [ "phy:/dev/VolGroup00/netbsd,0x1,w",		:<pre> disk = [ "phy:/dev/VolGroup00/netbsd,0x1,w",
-	: "phy:/path/to/partition,0x2,w",	+	: "phy:/path/to/partition,0x2,w",
-	: "file:/path/to/image,0x3,r" ] </pre>	+	: "file:/path/to/image,0x3,r" ] </pre>

	For installation, I mounted the NetBSD ISO image in my FTP directory and started vsftpd. I had to temporarily disable SELinux because ISO-9660 lacks the special labeling otherwise required. After installation was finished, I re-enabled SELinux.		For installation, I mounted the NetBSD ISO image in my FTP directory and started vsftpd. I had to temporarily disable SELinux because ISO-9660 lacks the special labeling otherwise required. After installation was finished, I re-enabled SELinux.

Jeff at 07:13, 1 August 2009

Jeff — Sat, 01 Aug 2009 07:13:34 GMT

←Older revision		Revision as of 07:13, 1 August 2009
Line 60:		Line 60:

	The kernel images are available in the ISO image itself, but are compressed with gzip. I decompressed them in /var/lib/xen/images and tacked ".amd64" on to the file names so they would not be confused with 32-bit kernels if I eventually put such there.		The kernel images are available in the ISO image itself, but are compressed with gzip. I decompressed them in /var/lib/xen/images and tacked ".amd64" on to the file names so they would not be confused with 32-bit kernels if I eventually put such there.
		+
		+	==References==
		+
		+	http://www.netbsd.org/ports/xen/howto.html

Jeff at 07:08, 1 August 2009

Jeff — Sat, 01 Aug 2009 07:08:49 GMT

←Older revision		Revision as of 07:08, 1 August 2009
Line 50:		Line 50:

	:This refers to a physical partition I created with Linux LVM2. In NetBSD, it is apparently not extremely important to make the device ID match a real major and minor number combo.		:This refers to a physical partition I created with Linux LVM2. In NetBSD, it is apparently not extremely important to make the device ID match a real major and minor number combo.
		+
		+	:You could choose to give the domU more disks by extending the disk array in the Python definition file like this:
		+
		+	:<pre> disk = [ "phy:/dev/VolGroup00/netbsd,0x1,w",
		+	: "phy:/path/to/partition,0x2,w",
		+	: "file:/path/to/image,0x3,r" ] </pre>

	For installation, I mounted the NetBSD ISO image in my FTP directory and started vsftpd. I had to temporarily disable SELinux because ISO-9660 lacks the special labeling otherwise required. After installation was finished, I re-enabled SELinux.		For installation, I mounted the NetBSD ISO image in my FTP directory and started vsftpd. I had to temporarily disable SELinux because ISO-9660 lacks the special labeling otherwise required. After installation was finished, I re-enabled SELinux.

	The kernel images are available in the ISO image itself, but are compressed with gzip. I decompressed them in /var/lib/xen/images and tacked ".amd64" on to the file names so they would not be confused with 32-bit kernels if I eventually put such there.		The kernel images are available in the ISO image itself, but are compressed with gzip. I decompressed them in /var/lib/xen/images and tacked ".amd64" on to the file names so they would not be confused with 32-bit kernels if I eventually put such there.

Jeff at 07:00, 1 August 2009

Jeff — Sat, 01 Aug 2009 07:00:36 GMT

←Older revision		Revision as of 07:00, 1 August 2009
Line 3:		Line 3:
	In Xen parlaiance, dom0 (domain zero) refers to the first kernel launched by the hypervisor, the one which has direct access to all the hardware. Then, domU (domain unprivileged) refers to all the other kernels running in the hypervisor, that do not have direct access to hardware.		In Xen parlaiance, dom0 (domain zero) refers to the first kernel launched by the hypervisor, the one which has direct access to all the hardware. Then, domU (domain unprivileged) refers to all the other kernels running in the hypervisor, that do not have direct access to hardware.

-	/etc/xen/auto/netbsd	+	<code>/etc/xen/auto/netbsd</code>

	<pre>		<pre>
Line 52:		Line 52:

	For installation, I mounted the NetBSD ISO image in my FTP directory and started vsftpd. I had to temporarily disable SELinux because ISO-9660 lacks the special labeling otherwise required. After installation was finished, I re-enabled SELinux.		For installation, I mounted the NetBSD ISO image in my FTP directory and started vsftpd. I had to temporarily disable SELinux because ISO-9660 lacks the special labeling otherwise required. After installation was finished, I re-enabled SELinux.
		+
		+	The kernel images are available in the ISO image itself, but are compressed with gzip. I decompressed them in /var/lib/xen/images and tacked ".amd64" on to the file names so they would not be confused with 32-bit kernels if I eventually put such there.

Jeff at 06:48, 1 August 2009

Jeff — Sat, 01 Aug 2009 06:48:54 GMT

←Older revision		Revision as of 06:48, 1 August 2009
Line 1:		Line 1:
-	I used CentOS 5.3 x86_64 (Linux) as the dom0, but that should be irrelevant.	+	I used CentOS 5.3 x86_64 (Linux) as the dom0, but that should be irrelevant. This is how I installed NetBSD 5.0 amd64 as a Xen domU.
		+
		+	In Xen parlaiance, dom0 (domain zero) refers to the first kernel launched by the hypervisor, the one which has direct access to all the hardware. Then, domU (domain unprivileged) refers to all the other kernels running in the hypervisor, that do not have direct access to hardware.

	/etc/xen/auto/netbsd		/etc/xen/auto/netbsd
Line 36:		Line 38:

	:<pre> xm create -c netbsd </pre>		:<pre> xm create -c netbsd </pre>
		+
		+	;kernel, on_reboot, and on_crash
		+
		+	:Basically, when installing we want the domU to halt if it crashes or reboots, because otherwise it would start the installation process again. However, if one of these events occurs if the machine is in production, we want it to reboot.
		+
		+	;vfb
		+
		+	:I hope this will work. I honestly haven't tested this to see if there is a display available on this domU yet.
		+
		+	;disk
		+
		+	:This refers to a physical partition I created with Linux LVM2. In NetBSD, it is apparently not extremely important to make the device ID match a real major and minor number combo.
		+
		+	For installation, I mounted the NetBSD ISO image in my FTP directory and started vsftpd. I had to temporarily disable SELinux because ISO-9660 lacks the special labeling otherwise required. After installation was finished, I re-enabled SELinux.

Jeff at 06:37, 1 August 2009

Jeff — Sat, 01 Aug 2009 06:37:20 GMT

←Older revision		Revision as of 06:37, 1 August 2009
Line 31:		Line 31:
	:The Xen <code>xm</code> command creates a special Python object, which you can use to test the environment. The end result is that when you are installing the domU, invoke the following:		:The Xen <code>xm</code> command creates a special Python object, which you can use to test the environment. The end result is that when you are installing the domU, invoke the following:

-	:<pre>	+	:<pre> xm create -c netbsd install=1 </pre>
-	xm create -c netbsd install=1	+
-	</pre>	+

	:And when otherwise starting an installed domU, invoke:		:And when otherwise starting an installed domU, invoke:

-	:<pre>	+	:<pre> xm create -c netbsd </pre>
-	xm create -c netbsd	+
-	</pre>	+

Jeff at 06:36, 1 August 2009

Jeff — Sat, 01 Aug 2009 06:36:32 GMT

←Older revision		Revision as of 06:36, 1 August 2009
Line 31:		Line 31:
	:The Xen <code>xm</code> command creates a special Python object, which you can use to test the environment. The end result is that when you are installing the domU, invoke the following:		:The Xen <code>xm</code> command creates a special Python object, which you can use to test the environment. The end result is that when you are installing the domU, invoke the following:

-	<pre>	+	:<pre>
	xm create -c netbsd install=1		xm create -c netbsd install=1
	</pre>		</pre>

-	And when otherwise starting an installed domU, invoke:	+	:And when otherwise starting an installed domU, invoke:

-	<pre>	+	:<pre>
	xm create -c netbsd		xm create -c netbsd
	</pre>		</pre>

Jeff at 06:34, 1 August 2009

Jeff — Sat, 01 Aug 2009 06:34:55 GMT

←Older revision		Revision as of 06:34, 1 August 2009
Line 27:		Line 27:
	</pre>		</pre>

-	if ...	+	;if ...

-	The Xen <code>xm</code> command creates a special Python object, which you can use to test the environment. The end result is that when you are installing the domU, invoke the following:	+	:The Xen <code>xm</code> command creates a special Python object, which you can use to test the environment. The end result is that when you are installing the domU, invoke the following:

	<pre>		<pre>

Jeff at 06:32, 1 August 2009

Jeff — Sat, 01 Aug 2009 06:32:35 GMT

←Older revision		Revision as of 06:32, 1 August 2009
Line 27:		Line 27:
	</pre>		</pre>

-	if ... The Xen <code>xm</code> command creates a special Python object, which you can use to test the environment.	+	if ...
		+
		+	The Xen <code>xm</code> command creates a special Python object, which you can use to test the environment. The end result is that when you are installing the domU, invoke the following:
		+
		+	<pre>
		+	xm create -c netbsd install=1
		+	</pre>
		+
		+	And when otherwise starting an installed domU, invoke:
		+
		+	<pre>
		+	xm create -c netbsd
		+	</pre>