--- wikisrc/ports/xen/howto.mdwn	2014/12/30 18:25:46	1.67
+++ wikisrc/ports/xen/howto.mdwn	2014/12/31 00:33:48	1.69
@@ -173,6 +173,12 @@ support) is difficult to build.  The fol
         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.)
 
@@ -881,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
 ------