--- wikisrc/ports/xen/howto.mdwn	2015/03/04 01:36:07	1.92
+++ wikisrc/ports/xen/howto.mdwn	2015/03/05 13:27:37	1.93
@@ -226,7 +226,7 @@ dom0 is what the computer would have bee
 desktop or laptop.  Then, one can run domUs at will.  Purists will
 deride this as less secure than the previous approach, and for a
 computer whose purpose is to run domUs, they are right.  But Xen and a
-dom0 (without domUs) is not meaingfully less secure than the same
+dom0 (without domUs) is not meaningfully less secure than the same
 things running without Xen.  One can boot Xen or boot regular NetBSD
 alternately with little problems, simply refraining from starting the
 Xen daemons when not running Xen.
@@ -251,7 +251,7 @@ over a RAID1 header to find /boot from a
 partition; this is no different when booting Xen.
 
 There are 4 styles of providing backing storage for the virtual disks
-used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN,
+used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN.
 
 With raw partitions, one has a disklabel (or gpt) partition sized for
 each virtual disk to be used by the domU.  (If you are able to predict
@@ -324,6 +324,11 @@ starting at 0).  In an attempt to add pe
 to force only one vcpu to be provided (since NetBSD dom0 can't use
 more) and to pin that vcpu to a physical cpu.  TODO: benchmark this.
 
+Xen has [many boot
+options](http://xenbits.xenproject.org/docs/4.5-testing/misc/xen-command-line.html),
+and other tham dom0 memory and max_vcpus, they are generally not
+necessary.
+
 As with non-Xen systems, you should have a line to boot /netbsd (a
 kernel that works without Xen) and fallback versions of the non-Xen
 kernel, Xen, and the dom0 kernel.
@@ -1020,8 +1025,10 @@ http://mail-index.netbsd.org/netbsd-user
 TODO items for improving NetBSD/xen
 ===================================
 
-* Package Xen 4.4.
-* Get PCI passthrough working on Xen 4.2 (or 4.4).
+* Make the NetBSD dom0 kernel work with SMP.
+* Test the Xen 4.5 packages adequately to be able to recommend them as
+  the standard approach.
+* Get PCI passthrough working on Xen 4.5
 * Get pvgrub into pkgsrc, either via xentools or separately.
 * grub
   * Check/add support to pkgsrc grub2 for UFS2 and arbitrary
@@ -1033,3 +1040,14 @@ TODO items for improving NetBSD/xen
   * 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.
+* Solve somehow the issue with modules for GENERIC not being loadable
+  in a Xen dom0 or domU kernel.
+
+Random pointers
+===============
+
+TODO: This section contains links from elsewhere not yet integrated
+into the HOWTO.
+
+* http://www.lumbercartel.ca/library/xen/
+* http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html