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

version 1.158, 2018/09/05 09:16:10 version 1.167, 2019/12/17 20:59:09
Line 33  architecture, with installing NetBSD on  Line 33  architecture, with installing NetBSD on 
 installing software from pkgsrc.  See also the [Xen  installing software from pkgsrc.  See also the [Xen
 website](http://www.xenproject.org/).  website](http://www.xenproject.org/).
   
 This HOWTO attempts to address both the case of running a NetBSD dom0  [[!toc]]
 on hardware and running domUs under it (NetBSD and other), and also  
 running NetBSD as a domU in a VPS.  
   
 Versions and Support  #Versions and Support
 ====================  
   
 In NetBSD, Xen is provided in pkgsrc, via matching pairs of packages  In NetBSD, Xen is provided in pkgsrc, via matching pairs of packages
 xenkernel and xentools.  We will refer only to the kernel versions,  xenkernel and xentools.  We will refer only to the kernel versions,
Line 48  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 66  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.
   
 NetBSD as 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 115  Once this is done, install the Xen kerne Line 118  Once this is done, install the Xen kerne
 # cp /usr/pkg/xen48-kernel/xen.gz /  # cp /usr/pkg/xen48-kernel/xen.gz /
 """]]  """]]
   
 Then, place a NetBSD XEN3_DOM0 kernel in the `/` directory, copied from  Then, place a NetBSD XEN3_DOM0 kernel in the `/` directory. Such kernel
 `releasedir/amd64/binary/kernel/netbsd-XEN3_DOM0.gz` of a NetBSD build.  can either be compiled manually, or downloaded from the NetBSD FTP, for
   example at:
   
   [[!template id=programlisting text="""
   ftp.netbsd.org/pub/NetBSD/NetBSD-8.0/amd64/binary/kernel/netbsd-XEN3_DOM0.gz
   """]]
   
 Add a line to /boot.cfg to boot Xen:  Add a line to /boot.cfg to boot Xen:
   
Line 124  Add a line to /boot.cfg to boot Xen: Line 132  Add a line to /boot.cfg to boot Xen:
 menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=512M  menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=512M
 """]]  """]]
   
 which specifies that the dom0 should have 512MB of ram, leaving the rest  This specifies that the dom0 should have 512MB of ram, leaving the rest
 to be allocated for domUs.  To use a serial console, use  to be allocated for domUs.  To use a serial console, use:
   
 [[!template id=filecontent name="/boot.cfg" text="""  [[!template id=filecontent name="/boot.cfg" text="""
 menu=Xen:load /netbsd-XEN3_DOM0.gz;multiboot /xen.gz dom0_mem=512M console=com1 com1=9600,8n1  menu=Xen:load /netbsd-XEN3_DOM0.gz;multiboot /xen.gz dom0_mem=512M console=com1 com1=9600,8n1
Line 145  more) and to pin that vcpu to a physical Line 153  more) and to pin that vcpu to a physical
 and other than dom0 memory and max_vcpus, they are generally not  and other than dom0 memory and max_vcpus, they are generally not
 necessary.  necessary.
   
   Copy the boot scripts into `/etc/rc.d`:
   
   [[!template id=programlisting text="""
   # cp /usr/pkg/share/examples/rc.d/xen* /etc/rc.d/
   """]]
   
 Enable `xencommons`:  Enable `xencommons`:
   
 [[!template id=filecontent name="/etc/rc.conf" text="""  [[!template id=filecontent name="/etc/rc.conf" text="""
Line 258  Minor version upgrades are trivial.  Jus Line 272  Minor version upgrades are trivial.  Jus
 xenkernel version and copy the new xen.gz to `/` (where `/boot.cfg`  xenkernel version and copy the new xen.gz to `/` (where `/boot.cfg`
 references it), and reboot.  references it), and reboot.
   
 Unprivileged domains (domU)  #Unprivileged domains (domU)
 ===========================  
   
 This section describes general concepts about domUs.  It does not  This section describes general concepts about domUs.  It does not
 address specific domU operating systems or how to install them.  The  address specific domU operating systems or how to install them.  The
Line 277  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 302  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 342  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 418  down cleanly on dom0 shutdown, add the f Line 431  down cleanly on dom0 shutdown, add the f
 xendomains="domU-netbsd domU-linux"  xendomains="domU-netbsd domU-linux"
 """]]  """]]
   
 Creating a domU  #Creating a domU
 ===============  
   
 Creating domUs is almost entirely independent of operating system.  We  Creating domUs is almost entirely independent of operating system.  We
 have already presented the basics of config files.  Note that you must  have already presented the basics of config files.  Note that you must
Line 429  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 452  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 618  note that only the "xpci" lines are unus Line 630  note that only the "xpci" lines are unus
         cd*     at scsibus? target ? lun ?      # SCSI CD-ROM drives          cd*     at scsibus? target ? lun ?      # SCSI CD-ROM drives
   
   
 NetBSD as a domU in a VPS  #NetBSD as a domU in a VPS
 =========================  
   
 The bulk of the HOWTO is about using NetBSD as a dom0 on your own  The bulk of the HOWTO is about using NetBSD as a dom0 on your own
 hardware.  This section explains how to deal with Xen in a domU as a  hardware.  This section explains how to deal with Xen in a domU as a
Line 684  Amazon Line 695  Amazon
 ------  ------
   
 See the [Amazon EC2 page](/amazon_ec2/).  See the [Amazon EC2 page](/amazon_ec2/).
   
 Random pointers  
 ===============  
   
 This section contains links from elsewhere not yet integrated into the  
 HOWTO, and other guides.  
   
 * http://www.lumbercartel.ca/library/xen/  
 * http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html  
 * https://gmplib.org/~tege/xen.html  

Removed from v.1.158  
changed lines
  Added in v.1.167


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