diff options
Diffstat (limited to 'microkernel/mach')
| -rw-r--r-- | microkernel/mach/gnumach/ports/xen.mdwn | 12 |
1 files changed, 3 insertions, 9 deletions
diff --git a/microkernel/mach/gnumach/ports/xen.mdwn b/microkernel/mach/gnumach/ports/xen.mdwn index cdb4e2de..c492d9a0 100644 --- a/microkernel/mach/gnumach/ports/xen.mdwn +++ b/microkernel/mach/gnumach/ports/xen.mdwn @@ -10,15 +10,9 @@ is included in the section entitled [[toc ]] -## Xen dom0, PAE-disabled hypervisor +## Xen dom0, hypervisor -/!\ 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. - -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/>. +/!\ 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. @@ -63,7 +57,7 @@ and gnumach should get started. Proceed with native-install. ./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 you just need to install and boot non-PAE hypervisor and kernel. +- 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 |