--- wikisrc/ports/xen/howto.mdwn	2014/12/27 15:46:47	1.59
+++ wikisrc/ports/xen/howto.mdwn	2014/12/30 18:25:46	1.67
@@ -151,17 +151,30 @@ Build problems
 Ideally, all versions of Xen in pkgsrc would build on all versions of
 NetBSD on both i386 and amd64.  However, that isn't the case.  Besides
 aging code and aging compilers, qemu (included in xentools for HVM
-support) is difficult to build.  The following are known to fail:
-
-        xenkernel3 netbsd-6 i386
-        xentools42 netbsd-6 i386 
-
-The following are known to work:
+support) is difficult to build.  The following are known to work or FAIL:
 
+        xenkernel3 netbsd-5 amd64
+        xentools3 netbsd-5 amd64
+        xentools3=hvm netbsd-5 amd64 ????
+        xenkernel33 netbsd-5 amd64
+        xentools33 netbsd-5 amd64
         xenkernel41 netbsd-5 amd64
         xentools41 netbsd-5 amd64
+        xenkernel42 netbsd-5 amd64
+        xentools42 netbsd-5 amd64
+
+        xenkernel3 netbsd-6 i386 FAIL
+        xentools3 netbsd-6 i386
+        xentools3-hvm netbsd-6 i386 FAIL (dependencies fail)
+        xenkernel33 netbsd-6 i386
+        xentools33 netbsd-6 i386
         xenkernel41 netbsd-6 i386
         xentools41 netbsd-6 i386
+        xenkernel42 netbsd-6 i386
+        xentools42 netbsd-6 i386 *MIXED
+
+(*On netbsd-6 i386, there is a xentools42 in the 2014Q3 official builds,
+but it does not build for gdt.)
 
 NetBSD as a dom0
 ================
@@ -457,7 +470,7 @@ Unprivileged domains (domU)
 This section describes general concepts about domUs.  It does not
 address specific domU operating systems or how to install them.  The
 config files for domUs are typically in /usr/pkg/etc/xen, and are
-typically named so that the file anme, domU name and the domU's host
+typically named so that the file name, domU name and the domU's host
 name match.
 
 The domU is provided with cpu and memory by Xen, configured by the
@@ -891,7 +904,9 @@ calls.  It is booted from the dom0 as th
 their own operating system and kernel.  See then [prgmr.com NetBSD
 HOWTO](http://wiki.prgmr.com/mediawiki/index.php/NetBSD_as_a_DomU).
 
-Typically one has an ext2 or FAT partition for the kernel, so that
+Because [grub's FFS code](http://xenbits.xensource.com/hg/xen-unstable.hg/file/bca284f67702/tools/libfsimage/ufs/fsys_ufs.c)
+appears not to support all aspects of modern FFS,
+typically one has an ext2 or FAT partition for the kernel, so that
 grub can understand it, which leads to /netbsd not being the actual
 kernel.  One must remember to update the special boot partiion.
 
@@ -909,3 +924,19 @@ DOMU kernel.
 TODO: explain how to compile npf into a custom kernel, answering (but
 note that the problem was caused by not booting the right kernel):
 http://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html
+
+TODO items for improving NetBSD/xen
+===================================
+
+* Package Xen 4.4.
+* Get PCI passthrough working on Xen 4.2 (or 4.4).
+* Get pvgrub into pkgsrc, either via xentools or separately.
+* grub
+  * Add support to pkgsrc grub2 for UFS2 and arbitrary
+    fragsize/blocksize (UFS2 support may be present; the point is to
+    make it so that with any UFS1/UFS2 filesystem setup that works
+    with NetBSD grub will also work).
+  * Push patches upstream.
+  * Get UFS2 patches into pvgrub.
+* Add support for PV ops to a version of /boot, and make it usable as
+  a kernel in Xen, similar to pvgrub.