diff options
author | GNU Hurd wiki engine <web-hurd@gnu.org> | 2008-03-01 17:49:54 +0000 |
---|---|---|
committer | GNU Hurd wiki engine <web-hurd@gnu.org> | 2008-03-01 17:49:54 +0000 |
commit | af6424f861e93e3e03a05c97e07f110db592ac08 (patch) | |
tree | 6869bcaf707ed539d6bdbd582521e07945bf423b | |
parent | 479793d24ba023f0a01990b52e87d017cb849f76 (diff) |
web commit by SamuelThibault
-rw-r--r-- | microkernel/mach/gnumach/ports/xen.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/microkernel/mach/gnumach/ports/xen.mdwn b/microkernel/mach/gnumach/ports/xen.mdwn index 19c5653e..d995c42d 100644 --- a/microkernel/mach/gnumach/ports/xen.mdwn +++ b/microkernel/mach/gnumach/ports/xen.mdwn @@ -10,7 +10,7 @@ You can either get binaries at <http://dept-info.labri.fr/~thibault/hurd-xen/> o - 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 - Run `xm create -c hurd`, gnumach should get started. -- If `xm` complains about networking (`vif could not be connected`), it's Xen fault, see Xen documentation for how to configure the network. The simplest way is network-bridge with fixed IPs. You can also just disable networking by commenting the vif line in the config. +- 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 a non-PAE hypervisor. If you want to generate these images, first get the `gnumach-1-branch-Xen-branch` branch from gnumach CVS. |