summaryrefslogtreecommitdiff
path: root/microkernel/mach/gnumach/ports/xen.mdwn
diff options
context:
space:
mode:
authorshakthimaan <shakthimaan@web>2008-09-23 05:42:19 +0000
committerGNU Hurd wiki engine <web-hurd@gnu.org>2008-09-23 05:42:19 +0000
commit071534c77850ea1f32987c3b908c047c40c225b4 (patch)
treed2aa20b07042f4ead21cc9a6fb87fb3e45984448 /microkernel/mach/gnumach/ports/xen.mdwn
parenta573fd8a9c868cdc2f886eed5458e6443a87efdb (diff)
.
Diffstat (limited to 'microkernel/mach/gnumach/ports/xen.mdwn')
-rw-r--r--microkernel/mach/gnumach/ports/xen.mdwn19
1 files changed, 18 insertions, 1 deletions
diff --git a/microkernel/mach/gnumach/ports/xen.mdwn b/microkernel/mach/gnumach/ports/xen.mdwn
index 1c1cc40..695be30 100644
--- a/microkernel/mach/gnumach/ports/xen.mdwn
+++ b/microkernel/mach/gnumach/ports/xen.mdwn
@@ -10,17 +10,34 @@ is included in the section entitled
/!\ Since GNU Mach doesn't handle PAE yet, you'll need a PAE-disabled hypervisor.
+On Debian Lenny, for example, you can install xen-hypervisor-3.2-1-i386-nonpae.
+
/!\ You need an already installed GNU/Hurd system.
+If you have a free partition, you can fdisk to type 0x83, create a filesystem using:
+
+ sudo mke2fs -b 4096 -I 128 -o hurd /dev/sda4
+
+Replace /dev/sda4 with your partition. Install and use crosshurd to setup a GNU/Hurd system on this partition.
+
This also means that you'll currently need a PAE-disabled `dom0`.
[[Stefan_Siegl|stesie]] is providing a PAE-disabled Linux kernel image at
<http://brokenpipe.de/GnuHurd/XEN/>.
-
You can either get binaries at <http://youpibouh.thefreecat.org/hurd-xen/> or build them yourself.
- Copy `gnumach-xen` and `hurd-modules` to your dom0 /boot.
- Copy `hurd` into `/etc/xen`, edit it for fixing access to your hurd / and swap
+
+Here is a sample /etc/xen/hurd configuration
+
+ kernel = "/boot/gnumach-xen"
+ memory = 256
+ disk = ['phy:sda4,hda,w']
+ extra = "root=device:hd0"
+ vif = [ '' ]
+ ramdisk = "/boot/hurd-modules"
+
- Run `xm create -c hurd`, gnumach should get started.
- If `xm` complains about networking (`vif could not be connected`), it's Xen scripts' fault, see Xen documentation for how to configure the network. The simplest way is network-bridge with fixed IPs (note that you need the bridge-utils package for this). You can also just disable networking by commenting the vif line in the config.
- If `xm` complains `Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n')`, you most probably have a PAE-enabled hypervisor, and you just need to install and boot non-PAE hypervisor and kernel.