--- wikisrc/ports/xen/howto.mdwn	2020/10/31 15:29:23	1.170
+++ wikisrc/ports/xen/howto.mdwn	2020/10/31 16:33:14	1.171
@@ -8,14 +8,14 @@ systems which operate in an unprivileged
 from the domU systems are forwarded by the Xen hypervisor to the dom0 to be
 fulfilled.
 
-Xen supports different styles of guest:
+Xen supports different styles of guests; see https://wiki.xen.org/wiki/PV_on_HVM and https://wiki.xenproject.org/wiki/PVH_(v2)_Domu for upstream documentation.
 
 [[!table data="""
 Style of guest	|Supported by NetBSD
 PV		|Yes (dom0, domU)
 HVM		|Yes (domU)
-PVHVM		|current-only (dom0, domU)
-PVH		|current-only (dom0, domU)
+PVH		|current-only (domU, dom0 not yet)
+PVHVM		|current-only (domU)
 """]]
 
 In Para-Virtualized (PV) mode, the guest OS does not attempt to access
@@ -25,9 +25,11 @@ guests must be specifically coded for Xe
 In HVM mode, no guest modification is required; however, hardware
 support is required, such as VT-x on Intel CPUs and SVM on AMD CPUs.
 
-In PVHVM mode, the guest mostly runs as HVM, but can use PV drivers for efficiency.  See https://wiki.xen.org/wiki/PV_on_HVM
+In PVH mode, the guest uses PV interfaces for IO and native interfaces for everything else.
 
-In PVH mode, the guest uses PV interfaces for IO and native interfaces for everything else.   This is also called PVHv2; see https://wiki.xenproject.org/wiki/PVH_(v2)_Domu
+In PVHVM mode, the guest mostly runs as HVM, but can use PV drivers for efficiency.
+
+\todo Explain about "HVM with PV drivers".
 
 At boot, the dom0 kernel is loaded as a module with Xen as the kernel.
 The dom0 can start one or more domUs.  (Booting is explained in detail