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

version 1.161, 2018/09/05 09:39:39 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 283  the dom0.  NetBSD's /dev/random system w Line 290  the dom0.  NetBSD's /dev/random system w
 Config files  Config files
 ------------  ------------
   
 See /usr/pkg/share/examples/xen/xlexample*,  See /usr/pkg/share/examples/xen/xlexample*
 for a large number of well-commented examples, mostly for running  for a small number of well-commented examples, mostly for running
 GNU/Linux.  GNU/Linux.
   
 The following is an example minimal domain configuration file. The domU  The following is an example minimal domain configuration file. The domU
Line 308  are stored in files and Xen attaches the Line 315  are stored in files and Xen attaches the
 dom0 on domain creation.  The system treats xbd0 as the boot device  dom0 on domain creation.  The system treats xbd0 as the boot device
 without needing explicit configuration.  without needing explicit configuration.
   
 By default, `xl` looks for domain config files in `/usr/pkg/etc/xen`.  Note  By convention, domain config files are kept in `/usr/pkg/etc/xen`.  Note
 that "xl create" takes the name of a config file, while other commands  that "xl create" takes the name of a config file, while other commands
 take the name of a domain.  take the name of a domain.
   
 Examples of commands:  Examples of commands:
   
 [[!template id=programlisting text="""  [[!template id=programlisting text="""
 xl create foo  xl create /usr/pkg/etc/xen/foo
 xl console foo  xl console domU-id
 xl create -c foo  xl create -c /usr/pkg/etc/xen/foo
 xl shutdown foo  xl shutdown domU-id
 xl list  xl list
 """]]  """]]
   
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 348  Virtual disks Line 355  Virtual disks
 In domU config files, the disks are defined as a sequence of 3-tuples:  In domU config files, the disks are defined as a sequence of 3-tuples:
   
  * The first element is "method:/path/to/disk". Common methods are   * The first element is "method:/path/to/disk". Common methods are
    "file:" for file-backed vnd, and "phy:" for something that is already     "file:" for a file-backed vnd, and "phy:" for something that is already
    a device.     a device, such as an LVM logical volume.
   
  * The second element is an artifact of how virtual disks are passed to   * The second element is an artifact of how virtual disks are passed to
    Linux, and a source of confusion with NetBSD Xen usage.  Linux domUs     Linux, and a source of confusion with NetBSD Xen usage.  Linux domUs
Line 434  Creating a NetBSD domU Line 441  Creating a NetBSD domU
 ----------------------  ----------------------
   
 See the earlier config file, and adjust memory.  Decide on how much  See the earlier config file, and adjust memory.  Decide on how much
 storage you will provide, and prepare it (file or lvm).  storage you will provide, and prepare it (file or LVM).
   
 While the kernel will be obtained from the dom0 file system, the same  While the kernel will be obtained from the dom0 file system, the same
 file should be present in the domU as /netbsd so that tools like  file should be present in the domU as /netbsd so that tools like
Line 457  kernel to / and change the kernel line i Line 464  kernel to / and change the kernel line i
   
         kernel = "/home/bouyer/netbsd-INSTALL_XEN3_DOMU"          kernel = "/home/bouyer/netbsd-INSTALL_XEN3_DOMU"
   
 Then, start the domain as "xl create -c configname".  Then, start the domain as "xl create -c configfile".
   
 Alternatively, if you want to install NetBSD/Xen with a CDROM image, the following  Alternatively, if you want to install NetBSD/Xen with a CDROM image, the following
 line should be used in the config file.  line should be used in the config file.
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.161  
changed lines
  Added in v.1.169


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