summaryrefslogtreecommitdiff
path: root/microkernel/mach/gnumach/ports/xen.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2009-12-31 14:47:37 +0100
committerThomas Schwinge <thomas@schwinge.name>2009-12-31 14:47:37 +0100
commit331d4b2fdb828de6d1b50ec866fa1839a429ca5c (patch)
treeb455899c8ce616aa79411405b6f5ed0b5e2727f9 /microkernel/mach/gnumach/ports/xen.mdwn
parent824dc46c2f7f43a25e22451d4d06521e85036e87 (diff)
news/2009-12-31: tschwinge's changes.
Diffstat (limited to 'microkernel/mach/gnumach/ports/xen.mdwn')
-rw-r--r--microkernel/mach/gnumach/ports/xen.mdwn21
1 files changed, 16 insertions, 5 deletions
diff --git a/microkernel/mach/gnumach/ports/xen.mdwn b/microkernel/mach/gnumach/ports/xen.mdwn
index c544fd5..bf26410 100644
--- a/microkernel/mach/gnumach/ports/xen.mdwn
+++ b/microkernel/mach/gnumach/ports/xen.mdwn
@@ -11,7 +11,7 @@ is included in the section entitled
[[!toc]]
-## Xen dom0, hypervisor
+# Xen dom0, hypervisor
/!\ Now that GNU Mach handles PAE you can use a PAE-enabled hypervisor.
@@ -20,7 +20,7 @@ You can either get binaries at <http://youpibouh.thefreecat.org/hurd-xen/> or bu
- Copy `gnumach-xen-pae` and `hurd-modules` to your dom0 /boot. If you still have a non-PAE hypervisor, use `gnumach-xen-nonpae` instead.
- Copy `hurd` into `/etc/xen`, edit it for fixing access to your hurd / and swap
-## GNU/Hurd system
+# GNU/Hurd system
/!\ You need an already installed [[GNU/Hurd_system|hurd/running]].
@@ -30,7 +30,7 @@ If you have a free partition, you can fdisk to type 0x83, create a filesystem us
Replace /dev/sda4 with your partition. Install and use crosshurd to setup a GNU/Hurd system on this partition.
-## /etc/xen/hurd configuration
+# /etc/xen/hurd configuration
Here is a sample /etc/xen/hurd configuration
@@ -49,7 +49,7 @@ Suggestions about [[networking_configuration]] are available.
If you need stable MAC addresses, use a syntax like `vif = [
'mac=00:16:3e:XX:XX:XX, bridge=br0' ]`.
-## Running Hurd with Xen
+# Running Hurd with Xen
To run Hurd with Xen, use:
@@ -63,7 +63,7 @@ and gnumach should get started. Proceed with native-install.
- 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 a non-PAE gnumach. Either install and boot non-PAE hypervisor and kernel, or rebuilt gnumach in PAE mode.
-## Building from sources
+# Building from sources
If you want to generate these images, first get the `gnumach-1-branch-Xen-branch` branch from gnumach CVS.
Then look for "Ugly" in `kern/bootstrap.c`, how to generate `hurd-modules` is explained there, and you'll have to fix `EXT2FS_SIZE` and `LD_SO_SIZE` by hand.
@@ -77,6 +77,17 @@ The current `hurd-modules` was built from the debian packages `hurd 20070606-2`
---
+# Miscellaneous
+
[[Internals]].
[[!GNU_Savannah_task 5468]], [[!GNU_Savannah_task 6584]].
+
+---
+
+# `pv-grub`
+
+From Xen 4.0 on you'll be able to run the GNU Hurd directly using `pv-grub`,
+without the need to [prepare a special bootstrap
+image](http://youpibouh.thefreecat.org/hurd-xen/build_hurd-modules) (like an
+initrd).