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

version 1.165, 2019/04/11 17:33:16 version 1.169, 2020/05/25 09:28:21
Line 45  matching versions. Line 45  matching versions.
 Versions available in pkgsrc:  Versions available in pkgsrc:
   
 [[!table data="""  [[!table data="""
 Xen Version     |Package Name   |Xen CPU Support        |EOL'ed By Upstream  Xen Version     |Package Name   |Xen CPU Support        |xm?    |EOL'ed By Upstream
 4.2             |xenkernel42    |32bit, 64bit           |Yes  4.2             |xenkernel42    |i386 x86_64            |yes    |Yes
 4.5             |xenkernel45    |64bit                  |Yes  4.5             |xenkernel45    |x86_64                 |       |Yes
 4.6             |xenkernel46    |64bit                  |Partially  4.6             |xenkernel46    |x86_64                 |       |Yes
 4.8             |xenkernel48    |64bit                  |No  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
   by xl.  xm is obsolete, but 4.2 remains in pkgsrc because migrating
   from xm to xl is not always trivial, and because 4.2 is the last
   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)
 than amd64.  than amd64.
   
 #Creating a dom0  # Creating a dom0
   
 In order to install a NetBSD as a dom0, one must first install a normal  In order to install a NetBSD as a dom0, one must first install a normal
 NetBSD system, and then pivot the install to a dom0 install by changing  NetBSD system, and then pivot the install to a dom0 install by changing
Line 330  will trigger controlled shutdowns of all Line 337  will trigger controlled shutdowns of all
 CPU and memory  CPU and memory
 --------------  --------------
   
 A domain is provided with some number of vcpus, less than the number  A domain is provided with some number of vcpus, up to the number
 of CPUs seen by the hypervisor. For a domU, it is controlled  of CPUs seen by the hypervisor. For a domU, it is controlled
 from the config file by the "vcpus = N" directive.  from the config file by the "vcpus = N" directive.
   
Line 650  A second issue is multiple CPUs.  With N Line 657  A second issue is multiple CPUs.  With N
 multiple vcpus, and it is typical for VPS providers to enable multiple  multiple vcpus, and it is typical for VPS providers to enable multiple
 CPUs for NetBSD domUs.  CPUs for NetBSD domUs.
   
 pygrub  
 -------  
   
 pygrub runs in the dom0 and looks into the domU file system.  This  
 implies that the domU must have a kernel in a file system in a format  
 known to pygrub.  As of 2014, pygrub seems to be of mostly historical  
 interest.  
   
 pvgrub  pvgrub
 ------  ------
   
Line 684  partition for the kernel with the intent Line 683  partition for the kernel with the intent
 which leads to /netbsd not being the actual kernel.  One must remember  which leads to /netbsd not being the actual kernel.  One must remember
 to update the special boot partition.  to update the special boot partition.
   
   pygrub
   -------
   
   pygrub runs in the dom0 and looks into the domU file system.  This
   implies that the domU must have a kernel in a file system in a format
   known to pygrub.
   
   pygrub doesn't seem to work to load Linux images under NetBSD dom0,
   and is inherently less secure than pvgrub due to running inside dom0. For both these
   reasons, pygrub should not be used, and is only still present so that
   historical DomU images using it still work.
   
   As of 2014, pygrub seems to be of mostly historical
   interest. New DomUs should use pvgrub.
   
 Amazon  Amazon
 ------  ------
   

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


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