Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.128 and 1.132

version 1.128, 2016/12/20 19:31:46 version 1.132, 2016/12/20 19:59:38
Line 113  need to use xm instead of xl, or if you  Line 113  need to use xm instead of xl, or if you 
 xenkernel45 provides Xen 4.5.  As of 2016-12, security patches were  xenkernel45 provides Xen 4.5.  As of 2016-12, security patches were
 released by Xen and applied to pkgsrc.  Xen 4.5 requires using a dom0  released by Xen and applied to pkgsrc.  Xen 4.5 requires using a dom0
 running NetBSD's amd64 port (Intel or AMD hardware is fine), but domUs  running NetBSD's amd64 port (Intel or AMD hardware is fine), but domUs
 can be amd64 or i386 PAE.  TODO: It is either a conservative choice or  can be amd64 or i386 PAE.  While slightly old, n4.5 has been tested and
 somewhat old.  run by others, so it is the conservative choice.
   
 xenkernel46 provides Xen 4.6.  It is new to pkgsrc as of 2016-05.  As  xenkernel46 provides Xen 4.6.  It is new to pkgsrc as of 2016-05.  As
 of 2016-12, security patches were released by Xen and applied to  of 2016-12, security patches were released by Xen and applied to
 pkgsrc.  Xen 4.6 similarly requires a NetBSD/amd64 dom0, but domUs can  pkgsrc.  Xen 4.6 similarly requires a NetBSD/amd64 dom0, but domUs can
 be amd64 or i386 PAE.  TODO: It is either a somewhat aggressive choice  be amd64 or i386 PAE.  For new installations, 4.6 is probably the
 or the standard choice.  appropriate choice and it will likely soon be the standard approach.
   
 Xen 4.7 (released 2016-06) and 4.8 (released 2016-12) are not yet in  Xen 4.7 (released 2016-06) and 4.8 (released 2016-12) are not yet in
 pkgsrc.  pkgsrc.
Line 148  variable. Line 148  variable.
   
 With xl, virtual devices are configured in parallel, which can cause  With xl, virtual devices are configured in parallel, which can cause
 problems if they are written assuming serial operation (e.g., updating  problems if they are written assuming serial operation (e.g., updating
 firewall rules without explicit locking).  firewall rules without explicit locking).  There is now locking for
   the provided scripts, which works for normal casses (e.g, file-backed
 There is now locking for xl startup, but as of 201612 it has not been  xbd, where a vnd must be allocated).  But, as of 201612, it has not
 adequately tested.  been adequately tested for a complex custom setup with a large number
   of interfaces.
   
 NetBSD  NetBSD
 ------  ------
Line 455  one is using xm or xl.  The Xen 3.1, 3.3 Line 456  one is using xm or xl.  The Xen 3.1, 3.3
 4.2 and up packages use xl.  To use xm with 4.2, edit xendomains to  4.2 and up packages use xl.  To use xm with 4.2, edit xendomains to
 use xm instead.  use xm instead.
   
 For "xm", you should enable xend and xenbackendd:  For 3.1 and 3.3, you should enable xend and xenbackendd:
   
         xend=YES          xend=YES
         xenbackendd=YES          xenbackendd=YES
   
 For "xl", you should enable xend and xencommons (xenstored).  Trying  For 4.1 and up, you should enable xencommons.  Not enabling xencommons
 to use xl without xencommons=YES will result in a hang; it is  will result in a hang; it is necessary to hit ^C on the console to let
 necessary to hit ^C on the console to let the machine finish booting.  the machine finish booting.  If you are using xm (default in 4.1, or
 TODO: Check if xend really should be used, and if not why it is  if you changed xendomains in 4.2), you should also enable xend:
 installed.  
   
         xend=YES          xend=YES # only if using xm, and only installed <= 4.2
         xencommons=YES          xencommons=YES
   
 TODO: Recommend for/against xen-watchdog.  TODO: Recommend for/against xen-watchdog.
Line 604  Hardware known to work Line 604  Hardware known to work
 Arguably, this section is misplaced, and there should be a page of  Arguably, this section is misplaced, and there should be a page of
 hardware that runs NetBSD/amd64 well, with the mostly-well-founded  hardware that runs NetBSD/amd64 well, with the mostly-well-founded
 assumption that NetBSD/xen runs fine on any modern hardware that  assumption that NetBSD/xen runs fine on any modern hardware that
 NetBSD/amd64 runs well on.  Until then, we give motherboard/CPU/RAM  NetBSD/amd64 runs well on.  Until then, we give motherboard/CPU (and
 triples to aid those choosing a motherboard.  Note that Xen systems  sometimes RAM) pairs/triples to aid those choosing a motherboard.
 usually do not run X, so a listing here does not imply that X works at  Note that Xen systems usually do not run X, so a listing here does not
 all.  imply that X works at all.
   
         Supermicro X9SRL-F, Xeon E5-1650 v2, 96 GiB ECC          Supermicro X9SRL-F, Xeon E5-1650 v2, 96 GiB ECC
         Supermicro ??, Atom C2758 (8 core), 32 GiB ECC          Supermicro ??, Atom C2758 (8 core), 32 GiB ECC
Line 616  all. Line 616  all.
 Older hardware:  Older hardware:
   
         Intel D915GEV, Pentium4 CPU 3.40GHz, 4GB 533MHz Synchronous DDR2          Intel D915GEV, Pentium4 CPU 3.40GHz, 4GB 533MHz Synchronous DDR2
           INTEL DG33FB, "Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz"
           INTEL DG33FB, "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
   
 Running Xen under qemu  Running Xen under qemu
 ----------------------  ----------------------

Removed from v.1.128  
changed lines
  Added in v.1.132


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