diff options
Diffstat (limited to 'microkernel/mach')
| -rw-r--r-- | microkernel/mach/gnumach/ports/xen.mdwn | 56 | ||||
| -rw-r--r-- | microkernel/mach/gnumach/ports/xen/discussion.mdwn | 14 |
2 files changed, 15 insertions, 55 deletions
diff --git a/microkernel/mach/gnumach/ports/xen.mdwn b/microkernel/mach/gnumach/ports/xen.mdwn index 1af19257..40b79a3f 100644 --- a/microkernel/mach/gnumach/ports/xen.mdwn +++ b/microkernel/mach/gnumach/ports/xen.mdwn @@ -16,78 +16,52 @@ License|/fdl]]."]]"""]] /!\ Now that GNU Mach handles PAE you can use a PAE-enabled hypervisor. -You can either get binaries at <http://youpibouh.thefreecat.org/hurd-xen/> or build them yourself. - -- 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 /!\ You need an already installed [[GNU/Hurd_system|hurd/running]]. 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 + sudo mke2fs -o hurd /dev/sda4 -Replace /dev/sda4 with your partition. Install and use crosshurd to setup a GNU/Hurd system on this partition. +Replace /dev/sda4 with your actual partition. Install and use crosshurd to setup a GNU/Hurd system on this partition. # /etc/xen/hurd configuration -There are two ways to boot a Hurd system: either directly boot gnumach, or boot it through PV-Grub. The former is a bit more complex. +The simpler way to boot a Hurd system is through PV-Grub. -## Directly booting gnumach +Use the following for instance: -Here is a sample /etc/xen/hurd configuration - - kernel = "/boot/gnumach-xen-pae" + kernel = "/usr/lib/grub-xen/grub-x86_64-xen.bin" memory = 512 disk = ['phy:sda4,hda,w'] - extra = "root=device:hd0" + extra = "(hd0)/boot/grub/grub.cfg" vif = [ '' ] - ramdisk = "/boot/hurd-modules" - -`hurd-modules` from http://youpibouh.thefreecat.org/hurd-xen/ was built from a specific libc version, -/!\ This means that when using this image, your GNU/Hurd system also needs to have the same version! -It is preferrable to rebuild your own hurd-modules, using your own libc version, by using the -http://youpibouh.thefreecat.org/hurd-xen/build_hurd-modules script. - -Suggestions about [[networking_configuration]] are available. +extra is the path to the grub config file, which must contain the usual grub command to boot a hurd system. If you need stable MAC addresses, use a syntax like `vif = [ 'mac=00:16:3e:XX:XX:XX, bridge=br0' ]`. -## Booting through pv-grub - -# `pv-grub` - -Starting from Xen 4.0, you can run the GNU Hurd using `pv-grub`. - -Download http://youpibouh.thefreecat.org/hurd-xen/pv-grub.gz into /boot, and use the following for instance: - - kernel = "/boot/pv-grub.gz" - memory = 512 - disk = ['phy:sda4,hda,w'] - extra = "(hd0)/boot/grub/menu.lst" - vif = [ '' ] - -extra is now the path to the grub config file, which must contain the usual grub -command to boot a hurd system. +If you are to run a 32b kernel, usr `/usr/lib/grub-xen/grub-i386-xen.bin` as kernel. # Running Hurd with Xen To run Hurd with Xen, use: - xm create -c hurd + xl create -c hurd + +and gnumach should get started. -and gnumach should get started. Proceed with native-install. +If you have installed with crosshurd, proceed with native-install. export TERM=mach ./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. + +- If `xl` 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 `xl` 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. # Partitions diff --git a/microkernel/mach/gnumach/ports/xen/discussion.mdwn b/microkernel/mach/gnumach/ports/xen/discussion.mdwn deleted file mode 100644 index 2980e3b2..00000000 --- a/microkernel/mach/gnumach/ports/xen/discussion.mdwn +++ /dev/null @@ -1,14 +0,0 @@ -[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -[[!tag open_issue_documentation]] - -Stuff from <http://youpibouh.thefreecat.org/hurd-xen> should be merged into -these pages here. |