Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.169 and 1.170

version 1.169, 2020/05/25 09:28:21 version 1.170, 2020/10/31 15:29:23
Line 14  Xen supports different styles of guest: Line 14  Xen supports different styles of guest:
 Style of guest  |Supported by NetBSD  Style of guest  |Supported by NetBSD
 PV              |Yes (dom0, domU)  PV              |Yes (dom0, domU)
 HVM             |Yes (domU)  HVM             |Yes (domU)
 PVHVM           |No  PVHVM           |current-only (dom0, domU)
 PVH             |No  PVH             |current-only (dom0, domU)
 """]]  """]]
   
 In Para-Virtualized (PV) mode, the guest OS does not attempt to access  In Para-Virtualized (PV) mode, the guest OS does not attempt to access
 hardware directly, but instead makes hypercalls to the hypervisor; PV  hardware directly, but instead makes hypercalls to the hypervisor; PV
 guests must be specifically coded for Xen. In HVM mode, no guest  guests must be specifically coded for Xen.
 modification is required; however, hardware support is required, such  
 as VT-x on Intel CPUs and SVM on AMD CPUs.  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.   This is also called PVHv2; see https://wiki.xenproject.org/wiki/PVH_(v2)_Domu
   
 At boot, the dom0 kernel is loaded as a module with Xen as the kernel.  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  The dom0 can start one or more domUs.  (Booting is explained in detail

Removed from v.1.169  
changed lines
  Added in v.1.170


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb