path: root/microkernel/mach/gnumach/ports/xen.mdwn
diff options
authorshakthimaan <shakthimaan@web>2008-09-24 12:44:44 +0000
committerGNU Hurd wiki engine <>2008-09-24 12:44:44 +0000
commit225c6a677f836ba1ceb015b63efc5b2321c58273 (patch)
tree6c6639b614adb829529e3cbea443d3c9a0a60408 /microkernel/mach/gnumach/ports/xen.mdwn
parent35306c9a868f53f48dec3b7b9a3429938264092e (diff)
Diffstat (limited to 'microkernel/mach/gnumach/ports/xen.mdwn')
1 files changed, 4 insertions, 1 deletions
diff --git a/microkernel/mach/gnumach/ports/xen.mdwn b/microkernel/mach/gnumach/ports/xen.mdwn
index 14a5c49..8919aa5 100644
--- a/microkernel/mach/gnumach/ports/xen.mdwn
+++ b/microkernel/mach/gnumach/ports/xen.mdwn
@@ -55,7 +55,10 @@ To run Hurd with Xen, use:
xm create -c hurd
-and gnumach should get started.
+and gnumach should get started. 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 you just need to install and boot non-PAE hypervisor and kernel.