Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.142 and 1.147

version 1.142, 2018/05/29 01:09:16 version 1.147, 2018/07/26 10:47:25
Line 1 Line 1
   [[!meta title="Xen HowTo"]]
   
 Introduction  Introduction
 ============  ============
   
Line 86  hardware architecture on which it runs.  Line 88  hardware architecture on which it runs. 
 both Intel and AMD, and in 2016 a normal PC has this CPU  both Intel and AMD, and in 2016 a normal PC has this CPU
 architecture.)  architecture.)
   
 Xen  Xen versions
 ---  ------------
   
 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,
 but note that both packages must be installed together and must have  but note that both packages must be installed together and must have
 matching versions.  matching versions.
   
 xenkernel3 provides Xen 3.1.  It is no longer maintained by Xen, and  Versions available in pkgsrc:
 the last applied security patch was in 2011. Thus, it should not be  
 used.  It supports PCI passthrough, which is why people use it anyway.  
 Xen 3.1 runs on i386 (both non-PAE and PAE) and amd64 hardware.  
   
 xenkernel33 provides Xen 3.3.  It is no longer maintained by Xen, and  
 the last applied security patch was in 2012.  Thus, it should not be  
 used.  Xen 3.3 runs on i386 PAE and amd64 hardware.  There are no good  
 reasons to run this version.  
   
 xenkernel41 provides Xen 4.1.  It is no longer maintained by Xen, but  
 as of 2016-12 received backported security patches.  Xen 4.1 runs on  
 i386 PAE and amd64 hardware.  There are no good reasons to run this  
 version.  
   
 Note that 3.1, 3.3 and 4.1 have been removed from pkgsrc-current, but  
 are in 2016Q4.  They will be removed from this HOWTO sometime after  
 2017Q1.  
   
 xenkernel42 provides Xen 4.2.  It is no longer maintained by Xen, but  
 as of 2016-12 received backported security patches.  Xen 4.2 runs on  
 i386 PAE and amd64 hardware.  The only reason to run this is if you  
 need to use xm instead of xl, or if you need to run on hardware that  
 supports i386 but not amd64.  (This might also be useful if you need  
 an i386 dom0, if it turns out that an amd64 Xen kernel and an i386  
 dom0 is problematic.)  
   
 xenkernel45 provides Xen 4.5.  Security advisories released in 2018-05  
 did not include support for 4.5.  Xen 4.5 and newer runs on amd64  
 hardware only.  While slightly old, 4.5 has been tested and run by  
 others, so it is a very conservative choice.  
   
 xenkernel46 provides Xen 4.6, and was added to pkgsrc as of 2016-05.  
 As of 2018-05, security patches were released by Xen and are expected  
 to be applied to pkgsrc.  Xen 4.6 runs on amd64 hardware only.  (If  
 using Ubuntu guests, be sure to have the xentools46 from December,  
 2016).  4.6 is perhaps an old choice, or perhaps the standard  
 approach.  
   
 Xen 4.7 was released in 2016-06 and is not in pkgsrc.  
   
 xenkernel48 provides Xen 4.8, and was added to pkgsrc in 2017-03.  As  
 of 2018-05, security patches were released by Xen and are expected to  
 be applied to pkgsrc.  4.8 is perhaps the standard choice, or perhaps  
 slightly new.  
   
 Xen 4.9 and 4.10 are not in pkgsrc.  [[!table data="""
   Xen Version     |Package Name   |Xen CPU Support        |EOL'ed By Upstream
   4.2             |xenkernel42    |32bit, 64bit           |Yes
   4.5             |xenkernel45    |64bit                  |Yes
   4.6             |xenkernel46    |64bit                  |Partially
   4.8             |xenkernel48    |64bit                  |No
   4.11            |xenkernel411   |64bit                  |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/).
   
 Note that NetBSD support is called XEN3.  It works with Xen 3 and Xen  Note: Xen 4.2 was the last version to support 32bit CPUs.
 4 because the hypercall interface has been stable.  
   
 Xen command program  Xen command program
 -------------------  -------------------
Line 158  xm and xl work fine.  4.4 is the last ve Line 122  xm and xl work fine.  4.4 is the last ve
 You must make a global choice to use xm or xl, because it affects not  You must make a global choice to use xm or xl, because it affects not
 only which command you use, but the command used by rc.d scripts  only which command you use, but the command used by rc.d scripts
 (specifically xendomains) and which daemons should be run.  The  (specifically xendomains) and which daemons should be run.  The
 xentools packages provide xm for 3.1, 3.3 and 4.1 and xl for 4.2 and up.  xentools packages provide xl for 4.2 and up.
   
 In 4.2, you can choose to use xm by simply changing the ctl_command  In 4.2, you can choose to use xm by simply changing the ctl_command
 variable and setting xend=YES in rc.conf.  variable and setting xend=YES in rc.conf.
Line 171  xbd, where a vnd must be allocated).  Bu Line 135  xbd, where a vnd must be allocated).  Bu
 been adequately tested for a complex custom setup with a large number  been adequately tested for a complex custom setup with a large number
 of interfaces.  of interfaces.
   
 NetBSD  NetBSD versions
 ------  ---------------
   
 The netbsd-7, netbsd-8, and -current branches are all reasonable  The netbsd-7, netbsd-8, and -current branches are all reasonable
 choices, with more or less the same considerations for non-Xen use.  choices, with more or less the same considerations for non-Xen use.
 Therefore, netbsd-7 is recommended as the stable version of the most  NetBSD 8 is recommended as the stable version of the most recent
 recent release for production use.  (Note that netbsd-7 (and therefore  release for production use.
 8/current) have a important scheduler fix (in November of 2015)  
 affecting contention between dom0 and domUs; see  For developing Xen, netbsd-current may be appropriate.
 https://releng.netbsd.org/cgi-bin/req-7.cgi?show=1040 for a  
 description.)  For production, netbsd-7 is appropriate.  For learning,  
 netbsd-8 is appropriate.  For developing Xen, netbsd-current may be  
 appropriate.  
   
 As of NetBSD 6, a NetBSD domU will support multiple vcpus.  There is  As of NetBSD 6, a NetBSD domU will support multiple vcpus.  There is
 no SMP support for NetBSD as dom0.  (The dom0 itself doesn't really  no SMP support for NetBSD as dom0.  (The dom0 itself doesn't really
 need SMP for dom0 functions; the lack of support is really a problem  need SMP for dom0 functions; the lack of support is really a problem
 when using a dom0 as a normal computer.)  when using a dom0 as a normal computer.)
   
   Note: NetBSD support is called XEN3. However, it does support Xen 4,
   because the hypercall interface has remained identical.
   
 Architecture  Architecture
 ------------  ------------
   
Line 234  NetBSD.  TODO: Include link to benchmark Line 197  NetBSD.  TODO: Include link to benchmark
 Stability  Stability
 ---------  ---------
   
 Mostly, NetBSD as a dom0 or domU is quite stable.  Mostly, NetBSD as a dom0 or domU is quite stable. However, just like every
 However, there are some open PRs indicating problems.  other architecture, there are some open PRs indicating problems.
   
  - [PR 48125](http://gnats.netbsd.org/48125)  
   
 Note also that there are issues with sparse vnd(4) instances, but  Note also that there are issues with sparse vnd(4) instances, but
 these are not about Xen -- they just are noticed with sparse vnd(4)  these are not about Xen -- they just are noticed with sparse vnd(4)
Line 261  pkgsrc), and with the Xen tools.  Specif Line 222  pkgsrc), and with the Xen tools.  Specif
 November, 2015, and xentools46 got a fix to enable Ubuntu guests to  November, 2015, and xentools46 got a fix to enable Ubuntu guests to
 boot in December, 2016.  boot in December, 2016.
   
 Status  
 ------  
   
 Ideally, all versions of Xen in pkgsrc would build on all supported  
 versions of NetBSD/amd64, to the point where this section would be  
 silly.  However, that has not always been the case.  Besides aging  
 code and aging compilers, qemu (included in xentools for HVM support)  
 is difficult to build.  Note that there is intentionally no data for  
 4.5+ up for i386, and often omits xentools info if the corresponding  
 kernel fails.  
   
 The following table gives status, with the date last checked  
 (generally on the most recent quarterly branch).  The first code is  
 "builds" if it builds ok, and "FAIL" for a failure to build.  The  
 second code/date only appears for xenkernel* and is "works" if it runs  
 ok as a dom0 and can support a domU, and "FAIL" if it won't boot or  
 run a domU.  
   
         xenkernel3 netbsd-6 i386 FAIL 201612  
         xenkernel33 netbsd-6 i386 FAIL 201612  
         xenkernel41 netbsd-6 i386 builds 201612  
         xenkernel42 netbsd-6 i386 builds 201612  
         xentools3 netbsd-6 i386 FAIL 201612  
         xentools33 netbsd-6 i386 FAIL 201612  
         xentools41 netbsd-6 i386 builds 201612  
         xentools42 netbsd-6 i386 FAIL 201612  
   
         xenkernel3 netbsd-7 i386 FAIL 201412  
         xenkernel33 netbsd-7 i386 FAIL 201412  
         xenkernel41 netbsd-7 i386 builds 201412  
         xenkernel42 netbsd-7 i386 builds 201412  
         xentools41 netbsd-7 i386 builds 201412  
         xentools42 netbsd-7 i386 ??FAIL 201412  
   
         xenkernel3 netbsd-6 amd64 FAIL 201612  
         xenkernel33 netbsd-6 amd64 FAIL 201612  
         xenkernel41 netbsd-6 amd64 builds 201612 works 201612  
         xenkernel42 netbsd-6 amd64 builds 201612 works 201612  
         xenkernel45 netbsd-6 amd64 builds 201612  
         xenkernel46 netbsd-6 amd64 builds 201612  
         xentools41 netbsd-6 amd64 builds 201612  
         xentools42 netbsd-6 amd64 builds 201612  
         xentools45 netbsd-6 amd64 builds 201612  
         xentools46 netbsd-6 amd64 FAIL 201612  
   
         xenkernel3 netbsd-7 amd64 builds 201612  
         xenkernel33 netbsd-7 amd64 builds 201612  
         xenkernel41 netbsd-7 amd64 builds 201612  
         xenkernel42 netbsd-7 amd64 builds 201612  
         xenkernel45 netbsd-7 amd64 builds 201612  
         xenkernel46 netbsd-7 amd64 builds 201612  
         xentools3 netbsd-7 amd64 builds 201612  
         xentools3-hvm netbsd-7 amd64 builds 201612  
         xentools33 netbsd-7 amd64 FAIL 201612  
         xentools41 netbsd-7 amd64 builds 201612  
         xentools42 netbsd-7 amd64 builds 201612  
         xentools45 netbsd-7 amd64 builds 201612  
         xentools46 netbsd-7 amd64 builds 201612  
   
 NetBSD as a dom0  NetBSD as a dom0
 ================  ================
   
Line 1170  to update the special boot partition. Line 1072  to update the special boot partition.
 Amazon  Amazon
 ------  ------
   
 See the [Amazon EC2 page](../amazon_ec2/).  See the [Amazon EC2 page](/amazon_ec2/).
   
 Using npf  
 ---------  
   
 In standard kernels, npf is a module, and thus cannot be loaded in a  
 DOMU kernel.  
   
 TODO: Explain how to compile npf into a custom kernel, answering (but  
 note that the problem was caused by not booting the right kernel)  
 [this email to  
 netbsd-users](https://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html).  
   
 TODO items for improving NetBSD/xen  TODO items for improving NetBSD/xen
 ===================================  ===================================
Line 1201  TODO items for improving NetBSD/xen Line 1092  TODO items for improving NetBSD/xen
   * Get UFS2 patches into pvgrub.    * Get UFS2 patches into pvgrub.
 * Add support for PV ops to a version of /boot, and make it usable as  * Add support for PV ops to a version of /boot, and make it usable as
   a kernel in Xen, similar to pvgrub.    a kernel in Xen, similar to pvgrub.
 * Solve somehow the issue with modules for GENERIC not being loadable  
   in a Xen dom0 or domU kernel.  
   
 Random pointers  Random pointers
 ===============  ===============

Removed from v.1.142  
changed lines
  Added in v.1.147


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