[BACK]Return to howto.mdwn CVS log [TXT] [DIR] Up to [NetBSD Developer Wiki] / wikisrc / ports / xen

Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.166 and 1.167

version 1.166, 2019/12/17 20:36:16 version 1.167, 2019/12/17 20:59:09
Line 46  Versions available in pkgsrc: Line 46  Versions available in pkgsrc:
   
 [[!table data="""  [[!table data="""
 Xen Version     |Package Name   |Xen CPU Support        |xm?    |EOL'ed By Upstream  Xen Version     |Package Name   |Xen CPU Support        |xm?    |EOL'ed By Upstream
 4.2             |xenkernel42    |32bit, 64bit           |yes    |Yes  4.2             |xenkernel42    |i386 x86_64            |yes    |Yes
 4.5             |xenkernel45    |64bit                  |       |Yes  4.5             |xenkernel45    |x86_64                 |       |Yes
 4.6             |xenkernel46    |64bit                  |       |Yes  4.6             |xenkernel46    |x86_64                 |       |Yes
 4.8             |xenkernel48    |64bit                  |       |Yes  4.8             |xenkernel48    |x86_64                 |       |Yes
 4.11            |xenkernel411   |64bit                  |       |No  4.11            |xenkernel411   |x86_64                 |       |No
 """]]  """]]
   
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).  See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
Line 63  dom0  |No Line 63  dom0  |No
 domU            |Yes  domU            |Yes
 """]]  """]]
   
 Note: NetBSD support is called XEN3. However, it does support Xen 4,  Note: NetBSD support is called XEN3.  However, it does support Xen 4,
 because the hypercall interface has remained identical.  because the hypercall interface has remained identical.
   
 Older Xen had a python-based management tool called xm, now replaced  Older Xen had a python-based management tool called xm, now replaced
Line 74  version to run on an i386 dom0. Line 74  version to run on an i386 dom0.
 Architecture  Architecture
 ------------  ------------
   
 Xen itself runs on x86_64 hardware.  Xen 4.5 and later runs on x86_64 hardware (the NetBSD amd64 port).
   Xen 4.2 can in theory use i386 hardware, but we do not have
   recent reports of success.
   
 The dom0 system, plus each domU, can be either i386PAE or amd64.  The dom0 system, plus each domU, can be either i386PAE or amd64.
 i386 without PAE is not supported.  i386 without PAE is not supported.
   
 The standard approach is to use NetBSD/amd64 for the dom0.  The standard approach is to use NetBSD/amd64 for the dom0.
   
 To use an i386PAE dom0, one must build or obtain a 64bit Xen kernel and  To use an i386PAE dom0 (other than on 4.2), one must build or obtain a
 install it on the system.  64bit Xen kernel and install it on the system.
   
 For domUs, i386PAE is considered as  For domUs, i386PAE is considered as
 [faster](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)  [faster](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)
Removed from v.1.166  
changed lines
  Added in v.1.167

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