--- wikisrc/ports/xen/howto.mdwn	2014/12/29 00:13:15	1.62
+++ wikisrc/ports/xen/howto.mdwn	2014/12/31 00:33:48	1.69
@@ -154,20 +154,33 @@ aging code and aging compilers, qemu (in
 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
+        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 FAIL
+        xenkernel42 netbsd-6 i386
+        xentools42 netbsd-6 i386 *MIXED
+
+	(all 3 and 33 seem to FAIL)
+        xenkernel41 netbsd-7 i386
+        xentools41 netbsd-7 i386
+        xenkernel42 netbsd-7 i386
+        xentools42 netbsd-7 i386 ??FAIL
+
+(*On netbsd-6 i386, there is a xentools42 in the 2014Q3 official builds,
+but it does not build for gdt.)
 
 NetBSD as a dom0
 ================
@@ -874,17 +887,18 @@ npf, run IPsec, or any other reason why 
 their kernel.
 
 One approach is to have an adminstrative interface to upload a kernel,
-or to select from a prepopulated list.  Other approaches are py-grub
+or to select from a prepopulated list.  Other approaches are pygrub
 (deprecated) and pvgrub, which are ways to have a bootloader obtain a
 kernel from the domU filesystem.  This is closer to a regular physical
 computer, where someone who controls a machine can replace the kernel.
 
-py-grub
+pygrub
 -------
 
-py-grub runs in the dom0 and looks into the domU filesystem.  This
+pygrub runs in the dom0 and looks into the domU filesystem.  This
 implies that the domU must have a kernel in a filesystem in a format
-known to py-grub.  As of 2014, py-grub seems to be of mostly historical interest.
+known to pygrub.  As of 2014, pygrub seems to be of mostly historical
+interest.
 
 pvgrub
 ------
@@ -917,3 +931,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.