Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.90 and 1.101

version 1.90, 2015/03/04 01:31:02 version 1.101, 2015/03/12 23:40:07
Line 95  of 2014-12. Line 95  of 2014-12.
 xenkernel45 provides Xen 4.5.  This is new to pkgsrc as of 2015-01 and  xenkernel45 provides Xen 4.5.  This is new to pkgsrc as of 2015-01 and
 not yet recommended for other than experimental/testing use.  not yet recommended for other than experimental/testing use.
   
   See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
   
 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 Xen 3 and Xen  Note that NetBSD support is called XEN3.  It works with Xen 3 and Xen
Line 128  Architecture Line 130  Architecture
 ------------  ------------
   
 Xen itself can run on i386 or amd64 machines.  (Practically, almost  Xen itself can run on i386 or amd64 machines.  (Practically, almost
 any computer where one would want to run Xen supports amd64.)  If  any computer where one would want to run Xen today supports amd64.)
 using an i386 NetBSD kernel for the dom0, PAE is required (PAE  
 versions are built by default).  While i386 dom0 works fine, amd64 is  Xen, the dom0 kernel, and each domU kernel can be either i386 or
 recommended as more normal.  amd64.  When building a xenkernel package, one obtains i386 on an i386
   host, and amd64 on an amd64 host.  If the xen kernel is i386, then the
   dom0 kernel and all domU kernels must be i386.  With an amd64 xen
   kernel, an amd64 dom0 kernel is known to work, and an i386 dom0 kernel
   should in theory work.  An amd64 xen/dom0 is known to support both
   i386 and amd64 domUs.
   
   i386 dom0 and domU kernels must be PAE (except for Xen 3.1); these are
   built by default.  (Note that emacs (at least) fails if run on i386
   with PAE when built without, and vice versa, presumably due to bugs in
   the undump code.)
   
   Because of the above, the standard approach is to use amd64 for the
   dom0.
   
 Xen 4.2 is the last version to support i386 as a host.  TODO: Clarify  Xen 4.2 is the last version to support i386 as a host.  TODO: Clarify
 if this is about the CPU having to be amd64, or about the dom0 kernel  if this is about the CPU, the xen kernel, or the dom0 kernel having to
 having to be amd64.  be amd64.
   
 One can then run i386 domUs and amd64 domUs, in any combination.  If  
 running an i386 NetBSD kernel as a domU, the PAE version is required.  
 (Note that emacs (at least) fails if run on i386 with PAE when built  
 without, and vice versa, presumably due to bugs in the undump code.)  
   
 Stability  Stability
 ---------  ---------
Line 148  Stability Line 159  Stability
 Mostly, NetBSD as a dom0 or domU is quite stable.  Mostly, NetBSD as a dom0 or domU is quite stable.
 However, there are some open PRs indicating problems.  However, there are some open PRs indicating problems.
   
  - http://gnats.netbsd.org/48125   - [PR 48125](http://gnats.netbsd.org/48125)
  - http://gnats.netbsd.org/47720   - [PR 47720](http://gnats.netbsd.org/47720)
   
 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.  these are not about Xen.
Line 226  dom0 is what the computer would have bee Line 237  dom0 is what the computer would have bee
 desktop or laptop.  Then, one can run domUs at will.  Purists will  desktop or laptop.  Then, one can run domUs at will.  Purists will
 deride this as less secure than the previous approach, and for a  deride this as less secure than the previous approach, and for a
 computer whose purpose is to run domUs, they are right.  But Xen and a  computer whose purpose is to run domUs, they are right.  But Xen and a
 dom0 (without domUs) is not meaingfully less secure than the same  dom0 (without domUs) is not meaningfully less secure than the same
 things running without Xen.  One can boot Xen or boot regular NetBSD  things running without Xen.  One can boot Xen or boot regular NetBSD
 alternately with little problems, simply refraining from starting the  alternately with little problems, simply refraining from starting the
 Xen daemons when not running Xen.  Xen daemons when not running Xen.
Line 251  over a RAID1 header to find /boot from a Line 262  over a RAID1 header to find /boot from a
 partition; this is no different when booting Xen.  partition; this is no different when booting Xen.
   
 There are 4 styles of providing backing storage for the virtual disks  There are 4 styles of providing backing storage for the virtual disks
 used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN,  used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN.
   
 With raw partitions, one has a disklabel (or gpt) partition sized for  With raw partitions, one has a disklabel (or gpt) partition sized for
 each virtual disk to be used by the domU.  (If you are able to predict  each virtual disk to be used by the domU.  (If you are able to predict
Line 324  starting at 0).  In an attempt to add pe Line 335  starting at 0).  In an attempt to add pe
 to force only one vcpu to be provided (since NetBSD dom0 can't use  to force only one vcpu to be provided (since NetBSD dom0 can't use
 more) and to pin that vcpu to a physical cpu.  TODO: benchmark this.  more) and to pin that vcpu to a physical cpu.  TODO: benchmark this.
   
   Xen has [many boot
   options](http://xenbits.xenproject.org/docs/4.5-testing/misc/xen-command-line.html),
   and other tham dom0 memory and max_vcpus, they are generally not
   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) and fallback versions of the non-Xen
 kernel, Xen, and the dom0 kernel.  kernel, Xen, and the dom0 kernel.
Line 509  Ensure that the contents of /etc/rc.d/xe Line 525  Ensure that the contents of /etc/rc.d/xe
 correct set of daemons.  Ensure that the domU config files are valid  correct set of daemons.  Ensure that the domU config files are valid
 for the new version.  for the new version.
   
   Hardware known to work
   ----------------------
   
   Arguably, this section is misplaced, and there should be a page of
   hardware that runs NetBSD/amd64 well, with the mostly-well-founded
   assumption that NetBSD/xen runs fine on any modern hardware that
   NetBSD/amd64 runs well on.  Until then, we give motherboard/CPU/RAM
   triples to aid those choosing a motherboard.  Note that Xen systems
   usually do not run X, so a listing here does not imply that X works at
   all.
   
           Supermicro X9SRL-F, Xeon E5-1650 v2, 96 GiB ECC
           Supermicro ??, Atom C2758 (8 core), 32 GiB ECC
           ASUS M5A78L-M/USB3 AM3+ microATX, AMD Piledriver X8 4000MHz, 16 GiB ECC
   
   Older hardware:
   
           Intel D915GEV, Pentium4 CPU 3.40GHz, 4GB 533MHz Synchronous DDR2
   
 Running Xen under qemu  Running Xen under qemu
 ----------------------  ----------------------
Line 526  In 2015-01, the following combination wa Line 560  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.  See [PR 47720](http://gnats.netbsd.org/47720) for a problem with dom0
   shutdown.
   
 Unprivileged domains (domU)  Unprivileged domains (domU)
 ===========================  ===========================
Line 755  i386 and amd64 provide the following ker Line 790  i386 and amd64 provide the following ker
   
         i386 XEN3_DOMU          i386 XEN3_DOMU
         i386 XEN3PAE_DOMU          i386 XEN3PAE_DOMU
         amd64 XEN3_DOMU          amd64 XEN3_DOMU
   
 Unless using Xen 3.1 (and you shouldn't) with i386-mode Xen, you must  Unless using Xen 3.1 (and you shouldn't) with i386-mode Xen, you must
 use the PAE version of the i386 kernel.  use the PAE version of the i386 kernel.
Line 808  It is also desirable to add Line 843  It is also desirable to add
 in rc.conf. This way, the domain will be properly shut down if  in rc.conf. This way, the domain will be properly shut down if
 `xm shutdown -R` or `xm shutdown -H` is used on the dom0.  `xm shutdown -R` or `xm shutdown -H` is used on the dom0.
   
 Your domain should be now ready to work, enjoy.  It is not strictly necessary to have a kernel (as /netbsd) in the domU
   filesystem.  However, various programs (e.g. netstat) will use that
   kernel to look up symbols to read from kernel virtual memory.  If
   /netbsd is not the running kernel, those lookups will fail.  (This is
   not really a Xen-specific issue, but because the domU kernel is
   obtained from the dom0, it is far more likely to be out of sync or
   missing with Xen.)
   
 Creating an unprivileged Linux domain (domU)  Creating an unprivileged Linux domain (domU)
 --------------------------------------------  --------------------------------------------
Line 996  to update the special boot partiion. Line 1037  to update the special boot partiion.
 Amazon  Amazon
 ------  ------
   
 TODO: add link to NetBSD amazon howto.  See the [Amazon EC2 page](../amazon_ec2/).
   
 Using npf  Using npf
 ---------  ---------
Line 1004  Using npf Line 1045  Using npf
 In standard kernels, npf is a module, and thus cannot be loaded in a  In standard kernels, npf is a module, and thus cannot be loaded in a
 DOMU kernel.  DOMU kernel.
   
 TODO: explain how to compile npf into a custom kernel, answering (but  TODO: Explain how to compile npf into a custom kernel, answering (but
 note that the problem was caused by not booting the right kernel):  note that the problem was caused by not booting the right kernel)
 http://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html  [this email to
   netbsd-users](http://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html).
   
 TODO items for improving NetBSD/xen  TODO items for improving NetBSD/xen
 ===================================  ===================================
   
 * Package Xen 4.4.  * Make the NetBSD dom0 kernel work with SMP.
 * Get PCI passthrough working on Xen 4.2 (or 4.4).  * Test the Xen 4.5 packages adequately to be able to recommend them as
     the standard approach.
   * Get PCI passthrough working on Xen 4.5
 * Get pvgrub into pkgsrc, either via xentools or separately.  * Get pvgrub into pkgsrc, either via xentools or separately.
 * grub  * grub
   * Check/add support to pkgsrc grub2 for UFS2 and arbitrary    * Check/add support to pkgsrc grub2 for UFS2 and arbitrary
Line 1024  TODO items for improving NetBSD/xen Line 1068  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
   ===============
   
   TODO: This section contains links from elsewhere not yet integrated
   into the HOWTO.
   
   * http://www.lumbercartel.ca/library/xen/
   * http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html

Removed from v.1.90  
changed lines
  Added in v.1.101


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