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

version 1.126, 2016/12/20 18:53:23 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 136  Xen command program Line 136  Xen command program
 Early Xen used a program called xm to manipulate the system from the  Early Xen used a program called xm to manipulate the system from the
 dom0.  Starting in 4.1, a replacement program with similar behavior  dom0.  Starting in 4.1, a replacement program with similar behavior
 called xl is provided, but it does not work well in 4.1.  In 4.2, both  called xl is provided, but it does not work well in 4.1.  In 4.2, both
 xm and xl work fine.  4.4 is the last version that has xm.  You must  xm and xl work fine.  4.4 is the last version that has xm.
 choose one or the other, because it affects which daemons you run.  
 However, the rc.d scripts provided by xentools packages expect a  You must make a global choice to use xm or xl, because it affects not
 particular version, and you should use the version used by the  only which command you use, but the command used by rc.d scripts
 scripts.  (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.
   
   In 4.2, you can choose to use xm by simply changing the ctl_command
   variable.
   
   With xl, virtual devices are configured in parallel, which can cause
   problems if they are written assuming serial operation (e.g., updating
   firewall rules without explicit locking).  There is now locking for
   the provided scripts, which works for normal casses (e.g, file-backed
   xbd, where a vnd must be allocated).  But, as of 201612, it has not
   been adequately tested for a complex custom setup with a large number
   of interfaces.
   
 NetBSD  NetBSD
 ------  ------
Line 234  ok as a dom0, and "FAIL" if it won't boo Line 246  ok as a dom0, and "FAIL" if it won't boo
         xenkernel41 netbsd-6 i386 builds 201612          xenkernel41 netbsd-6 i386 builds 201612
         xenkernel42 netbsd-6 i386 builds 201612          xenkernel42 netbsd-6 i386 builds 201612
         xentools3 netbsd-6 i386 FAIL 201612          xentools3 netbsd-6 i386 FAIL 201612
         xentools3-hvm netbsd-6 i386 FAIL 201412          xentools33 netbsd-6 i386 FAIL 201612
         xentools33 netbsd-6 i386 builds 201412  
         xentools41 netbsd-6 i386 builds 201612          xentools41 netbsd-6 i386 builds 201612
         xentools42 netbsd-6 i386 FAIL 201612          xentools42 netbsd-6 i386 FAIL 201612
   
Line 349  Installation of Xen Line 360  Installation of Xen
 -------------------  -------------------
   
 In the dom0, install sysutils/xenkernel42 and sysutils/xentools42 from  In the dom0, install sysutils/xenkernel42 and sysutils/xentools42 from
 pkgsrc (or another matching pair).  pkgsrc (or another matching pair).  See [the pkgsrc
 See [the pkgsrc  documentation](http://www.NetBSD.org/docs/pkgsrc/) for help with
 documentation](http://www.NetBSD.org/docs/pkgsrc/) for help with pkgsrc.  pkgsrc.  Ensure that your packages are recent; the HOWTO does not
   contemplate old builds.
   
   
 For Xen 3.1, support for HVM guests is in sysutils/xentool3-hvm.  More  For Xen 3.1, support for HVM guests is in sysutils/xentool3-hvm.  More
 recent versions have HVM support integrated in the main xentools  recent versions have HVM support integrated in the main xentools
Line 403  and other than dom0 memory and max_vcpus Line 416  and other than dom0 memory and max_vcpus
 necessary.  necessary.
   
 As with non-Xen systems, you should have a line to boot /netbsd (a  As with non-Xen systems, you should have a line to boot /netbsd (a
 kernel that works without Xen) and fallback versions of the non-Xen  kernel that works without Xen).  Consider a line to boot /netbsd.ok (a
 kernel, Xen, and the dom0 kernel.  fallback version of the non-Xen kernel, updated manually when you are
   sure /netbsd is ok).  Consider also a line to boot fallback versions
   of Xen and the dom0 kernel, but note that non-Xen NetBSD can be used
   to resolve Xen booting issues.
   
   Probably you want a default=N line to choose Xen in the absence of
   intervention.
   
 Now, reboot so that you are running a DOM0 kernel under Xen, rather  Now, reboot so that you are running a DOM0 kernel under Xen, rather
 than GENERIC without Xen.  than GENERIC without Xen.
Line 433  There will be no domUs, and none can be  Line 452  There will be no domUs, and none can be 
 to configure the dom0 daemons.  to configure the dom0 daemons.
   
 The daemons which should be run vary with Xen version and with whether  The daemons which should be run vary with Xen version and with whether
 one is using xm or xl.  The Xen 3.1 and 3.3 packages use xm.  Xen 4.1  one is using xm or xl.  The Xen 3.1, 3.3 and 4.1 packages use xm.  Xen
 and higher packages use xl.  While is is possible to use xm with some  4.2 and up packages use xl.  To use xm with 4.2, edit xendomains to
 4.x versions (TODO: 4.1 and 4.2?), the pkgsrc-provided rc.d scripts do  use xm instead.
 not support this as of 2014-12-26, and thus the HOWTO does not support  
 it either.  (Make sure your packages are reasonably recent.)  
   
 For "xm" (3.1 and 3.3), you should enable xend and xenbackendd (but  For 3.1 and 3.3, you should enable xend and xenbackendd:
 note that you should be using 4.x):  
   
         xend=YES          xend=YES
         xenbackendd=YES          xenbackendd=YES
   
 For "xl" (4.x), you should enabled xend and xencommons (xenstored).  For 4.1 and up, you should enable xencommons.  Not enabling xencommons
 Trying to boot 4.x 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: explain why xend is installed by the package.  if you changed xendomains in 4.2), you should also enable xend:
   
           xend=YES # only if using xm, and only installed <= 4.2
         xencommons=YES          xencommons=YES
   
 The installation of NetBSD should already have created devices for xen  
 (xencons, xenevt), but if they are not present, create them:  
   
         cd /dev && sh MAKEDEV xen  
   
 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 483  make this work, one should not expect to Line 495  make this work, one should not expect to
 (and thus xencommons).  There is currently no reason to expect that  (and thus xencommons).  There is currently no reason to expect that
 this will get fixed any time soon.  this will get fixed any time soon.
   
   ### No-longer needed advice about devices
   
   The installation of NetBSD should already have created devices for xen
   (xencons, xenevt, xsd_kva), but if they are not present, create them:
   
           cd /dev && sh MAKEDEV xen
   
 anita (for testing NetBSD)  anita (for testing NetBSD)
 --------------------------  --------------------------
   
Line 585  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 597  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
 ----------------------  ----------------------
Line 730  for the first virtual disk for the domU  Line 751  for the first virtual disk for the domU 
 the file serves two purposes.  One is that preallocating the contents  the file serves two purposes.  One is that preallocating the contents
 improves performance.  The other is that vnd on sparse files has  improves performance.  The other is that vnd on sparse files has
 failed to work.  TODO: give working/notworking NetBSD versions for  failed to work.  TODO: give working/notworking NetBSD versions for
 sparse vnd.  Note that the use of file/vnd for Xen is not really  sparse vnd and gnats reference.  Note that the use of file/vnd for Xen
 different than creating a file-backed virtual disk for some other  is not really different than creating a file-backed virtual disk for
 purpose, except that xentools handles the vnconfig commands.  To  some other purpose, except that xentools handles the vnconfig
 create an empty 4G virtual disk, simply do  commands.  To create an empty 4G virtual disk, simply do
   
         dd if=/dev/zero of=foo-xbd0 bs=1m count=4096          dd if=/dev/zero of=foo-xbd0 bs=1m count=4096
   
Line 767  guest, one can create /dev/hda1 in /dev, Line 788  guest, one can create /dev/hda1 in /dev,
 The third element is "w" for writable disks, and "r" for read-only  The third element is "w" for writable disks, and "r" for read-only
 disks.  disks.
   
   Note that NetBSD by default creates only vnd[0123].  If you need more
   than 4 total virtual disks at a time, run e.g. "./MAKEDEV vnd4" in the
   dom0.
   
   Note that NetBSD by default creates only xbd[0123].  If you need more
   virtual disks in a domU, run e.g. "./MAKEDEV xbd4" in the domU.
   
 Virtual Networking  Virtual Networking
 ------------------  ------------------
   

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


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