Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.83 and 1.88

version 1.83, 2015/01/17 13:14:32 version 1.88, 2015/02/10 17:38:14
Line 92  reasonable although trailing-edge choice Line 92  reasonable although trailing-edge choice
 xenkernel42 provides Xen 4.2.  This is maintained by Xen, but old as  xenkernel42 provides Xen 4.2.  This is maintained by Xen, but old as
 of 2014-12.  of 2014-12.
   
   xenkernel45 provides Xen 4.5.  This is new to pkgsrc as of 2015-01 and
   not yet recommended for other than experimental/testing use.
   
 Ideally newer versions of Xen will be added to pkgsrc.  Ideally newer versions of Xen will be added to pkgsrc.
   
 Note that NetBSD support is called XEN3.  It works with 3.1 through  Note that NetBSD support is called XEN3.  It works with Xen 3 and Xen
 4.2 because the hypercall interface has been stable.  4 because the hypercall interface has been stable.
   
 Xen command program  Xen command program
 -------------------  -------------------
Line 341  to configure the dom0 tools.  The daemon Line 344  to configure the dom0 tools.  The daemon
 with Xen version and with whether one is using xm or xl.  Note that  with Xen version and with whether one is using xm or xl.  Note that
 xend is for supporting "xm", and should only be used if you plan on  xend is for supporting "xm", and should only be used if you plan on
 using "xm".  Do NOT enable xend if you plan on using "xl" as it will  using "xm".  Do NOT enable xend if you plan on using "xl" as it will
 cause problems.  cause problems.  Running xl without xencommons=YES (and starting it)
   will result in a hang (so don't do that; follow the HOWTO!).
   
 The installation of NetBSD should already have created devices for xen  The installation of NetBSD should already have created devices for xen
 (xencons, xenevt), but if they are not present, create them:  (xencons, xenevt), but if they are not present, create them:
Line 374  For 4.2 with xl, add to rc.conf: Line 378  For 4.2 with xl, add to rc.conf:
         xencommons=YES          xencommons=YES
         TODO: explain if there is a xend replacement          TODO: explain if there is a xend replacement
   
   For 4.5 (and thus with xl), add to rc.conf:
   
           xencommons=YES
           TODO: explain if there is a xend replacement
   
 TODO: Recommend for/against xen-watchdog.  TODO: Recommend for/against xen-watchdog.
   
 After you have configured the daemons and either started them (in the  After you have configured the daemons and either started them (in the
Line 392  With xl, the commands are the same, and  Line 401  With xl, the commands are the same, and 
 different.  TODO: add example output for xl before the xm example,  different.  TODO: add example output for xl before the xm example,
 after confirming on 4.2 and resolving the TODO about rc.conf.  after confirming on 4.2 and resolving the TODO about rc.conf.
   
   ### Issues with xencommons
   
   xencommons starts xenstored, which stores data on behalf of dom0 and
   domUs.  It does not currently work to stop and start xenstored.
   Certainly all domUs should be shutdown first, following the sort order
   of the rc.d scripts.  However, the dom0 sets up state with xenstored,
   and is not notified when xenstored exits, leading to not recreating
   the state when the new xenstored starts.  Until there's a mechanism to
   make this work, one should not expect to be able to restart xenstored
   (and thus xencommons).  There is currently no reason to expect that
   this will get fixed any time soon.
   
 anita (for testing NetBSD)  anita (for testing NetBSD)
 --------------------------  --------------------------
   
Line 485  However, it can be useful to run Xen und Line 506  However, it can be useful to run Xen und
 version of NetBSD as a dom0 does not run on the hardware in use, or to  version of NetBSD as a dom0 does not run on the hardware in use, or to
 generate automated test cases involving Xen.  generate automated test cases involving Xen.
   
 In 2015-01, the following combination was reported to work:  In 2015-01, the following combination was reported to mostly work:
   
         host OS: NetBSD/amd64 6.1.4          host OS: NetBSD/amd64 6.1.4
         qemu: 2.2.0 from pkgsrc          qemu: 2.2.0 from pkgsrc
Line 493  In 2015-01, the following combination wa Line 514  In 2015-01, the following combination wa
         dom0 kernel: NetBSD/amd64 6.1.5          dom0 kernel: NetBSD/amd64 6.1.5
         Xen tools: xentools42-4.2.5 from pkgsrc          Xen tools: xentools42-4.2.5 from pkgsrc
   
   See http://gnats.netbsd.org/47720 for a problem with dom0 shutdown.
   
 Unprivileged domains (domU)  Unprivileged domains (domU)
 ===========================  ===========================
   
Line 690  shutdown, in rc.conf add: Line 713  shutdown, in rc.conf add:
   
         xendomains="foo bar"          xendomains="foo bar"
   
 TODO: Explain why 4.1 rc.d/xendomains has xl, when one should use xm  Note that earlier versions of the xentools41 xendomains rc.d scripth
 on 4.1.  Or fix the xentools41 package to have xm  usd xl, when one should use xm with 4.1.
   
 Creating specific unprivileged domains (domU)  Creating specific unprivileged domains (domU)
 =============================================  =============================================

Removed from v.1.83  
changed lines
  Added in v.1.88


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