Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.93 and 1.99

version 1.93, 2015/03/05 13:27:37 version 1.99, 2015/03/12 21:27:36
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.
   
   Except for an odd case with Xen 3.1, i386 dom0 and domU kernels must
   be PAE; 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 having to be amd64, or about the dom0 kernel
 having to be amd64.  having to 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 514  Ensure that the contents of /etc/rc.d/xe Line 524  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 761  i386 and amd64 provide the following ker Line 789  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 822  not really a Xen-specific issue, but bec Line 850  not really a Xen-specific issue, but bec
 obtained from the dom0, it is far more likely to be out of sync or  obtained from the dom0, it is far more likely to be out of sync or
 missing with Xen.)  missing with Xen.)
   
 Your domain should be now ready to work, enjoy.  
   
 Creating an unprivileged Linux domain (domU)  Creating an unprivileged Linux domain (domU)
 --------------------------------------------  --------------------------------------------
   
Line 1010  to update the special boot partiion. Line 1036  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 1018  Using npf Line 1044  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
 ===================================  ===================================

Removed from v.1.93  
changed lines
  Added in v.1.99


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