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

version 1.145, 2018/07/26 10:36:26 version 1.147, 2018/07/26 10:47:25
Line 88  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,
Line 111  See also the [Xen Security Advisory page Line 111  See also the [Xen Security Advisory page
   
 Note: Xen 4.2 was the last version to support 32bit CPUs.  Note: Xen 4.2 was the last version to support 32bit CPUs.
   
 Note that NetBSD support is called XEN3.  It works with Xen 3 and Xen  
 4 because the hypercall interface has been stable.  
   
 Xen command program  Xen command program
 -------------------  -------------------
   
Line 125  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 138  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
 ------------  ------------
   

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


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