--- wikisrc/ports/xen/howto.mdwn	2018/07/26 12:21:24	1.153
+++ wikisrc/ports/xen/howto.mdwn	2018/07/26 16:29:45	1.154
@@ -144,16 +144,14 @@ i386 dom0 and domU kernels must be PAE. 
 the NetBSD default build.
 
 Because of the above, the standard approach is to use an amd64 Xen
-kernel and NetBSD/amd64 for the dom0.  For domUs, NetBSD/i386 (with
-the PAE kernel) and NetBSD/amd64 are in widespread use, and there is
+kernel and NetBSD/amd64 for the dom0.  For domUs, NetBSD/i386 (PAE) and
+NetBSD/amd64 are in widespread use, and there is
 little to no Xen-specific reason to prefer one over the other.
 
 Note that to use an i386 dom0 with Xen 4.5 or higher, one must build
 (or obtain from pre-built packages) an amd64 Xen kernel and install
-that on the system.  (One must also use a PAE i386 kernel, but this is
-also required with an i386 Xen kernel.).  Almost no one in the
-NetBSD/Xen community does this, and the standard, well-tested,
-approach is to use an amd64 dom0.
+that on the system.  Almost no one in the NetBSD/Xen community does
+this, and the standard, well-tested, approach is to use an amd64 dom0.
 
 A [posting on
 xen-devel](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)
@@ -722,13 +720,9 @@ savecore(8) can work.   (This is helpful
 The kernel must be specifically for Xen and for use as a domU.  The
 i386 and amd64 provide the following kernels:
 
-        i386 XEN3_DOMU
         i386 XEN3PAE_DOMU
         amd64 XEN3_DOMU
 
-Unless using Xen 3.1 (and you shouldn't) with i386-mode Xen, you must
-use the PAE version of the i386 kernel.
-
 This will boot NetBSD, but this is not that useful if the disk is
 empty.  One approach is to unpack sets onto the disk outside of xen
 (by mounting it, just as you would prepare a physical disk for a