Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.58 and 1.71

version 1.58, 2014/12/27 00:36:20 version 1.71, 2015/01/04 02:14:15
Line 151  Build problems Line 151  Build problems
 Ideally, all versions of Xen in pkgsrc would build on all versions of  Ideally, all versions of Xen in pkgsrc would build on all versions of
 NetBSD on both i386 and amd64.  However, that isn't the case.  Besides  NetBSD on both i386 and amd64.  However, that isn't the case.  Besides
 aging code and aging compilers, qemu (included in xentools for HVM  aging code and aging compilers, qemu (included in xentools for HVM
 support) is difficult to build.  The following are known to fail:  support) is difficult to build.  The following are known to work or FAIL:
   
         xenkernel3 netbsd-6 i386  
         xentools42 netbsd-6 i386   
   
 The following are known to work:  
   
           xenkernel3 netbsd-5 amd64
           xentools3 netbsd-5 amd64
           xentools3=hvm netbsd-5 amd64 ????
           xenkernel33 netbsd-5 amd64
           xentools33 netbsd-5 amd64
         xenkernel41 netbsd-5 amd64          xenkernel41 netbsd-5 amd64
         xentools41 netbsd-5 amd64          xentools41 netbsd-5 amd64
           xenkernel42 netbsd-5 amd64
           xentools42 netbsd-5 amd64
   
           xenkernel3 netbsd-6 i386 FAIL
           xentools3 netbsd-6 i386
           xentools3-hvm netbsd-6 i386 FAIL (dependencies fail)
           xenkernel33 netbsd-6 i386
           xentools33 netbsd-6 i386
         xenkernel41 netbsd-6 i386          xenkernel41 netbsd-6 i386
         xentools41 netbsd-6 i386          xentools41 netbsd-6 i386
           xenkernel42 netbsd-6 i386
           xentools42 netbsd-6 i386 *MIXED
   
           (all 3 and 33 seem to FAIL)
           xenkernel41 netbsd-7 i386
           xentools41 netbsd-7 i386
           xenkernel42 netbsd-7 i386
           xentools42 netbsd-7 i386 ??FAIL
   
   (*On netbsd-6 i386, there is a xentools42 in the 2014Q3 official builds,
   but it does not build for gdt.)
   
 NetBSD as a dom0  NetBSD as a dom0
 ================  ================
Line 457  Unprivileged domains (domU) Line 476  Unprivileged domains (domU)
 This section describes general concepts about domUs.  It does not  This section describes general concepts about domUs.  It does not
 address specific domU operating systems or how to install them.  The  address specific domU operating systems or how to install them.  The
 config files for domUs are typically in /usr/pkg/etc/xen, and are  config files for domUs are typically in /usr/pkg/etc/xen, and are
 typically named so that the file anme, domU name and the domU's host  typically named so that the file name, domU name and the domU's host
 name match.  name match.
   
 The domU is provided with cpu and memory by Xen, configured by the  The domU is provided with cpu and memory by Xen, configured by the
Line 531  anyplace, reasonable places to store dom Line 550  anyplace, reasonable places to store dom
 (so they are near the dom0 kernel), in /usr/pkg/etc/xen (near the  (so they are near the dom0 kernel), in /usr/pkg/etc/xen (near the
 config files), or in /u0/xen (where the vdisks are).  config files), or in /u0/xen (where the vdisks are).
   
   Note that loading the domU kernel from the dom0 implies that boot
   blocks, /boot, /boot.cfg, and so on are all ignored in the domU.
 See the VPS section near the end for discussion of alternate ways to  See the VPS section near the end for discussion of alternate ways to
 obtain domU kernels.  obtain domU kernels.
   
Line 854  NetBSD as a domU in a VPS Line 875  NetBSD as a domU in a VPS
 The bulk of the HOWTO is about using NetBSD as a dom0 on your own  The bulk of the HOWTO is about using NetBSD as a dom0 on your own
 hardware.  This section explains how to deal with Xen in a domU as a  hardware.  This section explains how to deal with Xen in a domU as a
 virtual private server where you do not control or have access to the  virtual private server where you do not control or have access to the
 dom0.  dom0.  This is not intended to be an exhaustive list of VPS providers;
   only a few are mentioned that specifically support NetBSD.
   
 VPS operators provide varying degrees of access and mechanisms for  VPS operators provide varying degrees of access and mechanisms for
 configuration.  The big issue is usually how one controls which kernel  configuration.  The big issue is usually how one controls which kernel
 is booted, because the kernel is nominally in the dom0 filesystem (to  is booted, because the kernel is nominally in the dom0 filesystem (to
 which VPS users do not normally have acesss).  which VPS users do not normally have acesss).  A second issue is how
   to install NetBSD.
   
 A VPS user may want to compile a kernel for security updates, to run  A VPS user may want to compile a kernel for security updates, to run
 npf, run IPsec, or any other reason why someone would want to change  npf, run IPsec, or any other reason why someone would want to change
 their kernel.  their kernel.
   
 One approach is to have an adminstrative interface to upload a kernel,  One approach is to have an adminstrative interface to upload a kernel,
 or to select from a prepopulated list.  or to select from a prepopulated list.  Other approaches are pygrub
   (deprecated) and pvgrub, which are ways to have a bootloader obtain a
 Otehr approaches are pvgrub and py-grub, which are ways to start a  kernel from the domU filesystem.  This is closer to a regular physical
 bootloader from the dom0 instead of the actual domU kernel, and for  computer, where someone who controls a machine can replace the kernel.
 that loader to then load a kernel from the domU filesystem.  This is  
 closer to a regular physical computer, where someone who controls a  pygrub
 machine can replace the kernel.  -------
   
   pygrub runs in the dom0 and looks into the domU filesystem.  This
   implies that the domU must have a kernel in a filesystem in a format
   known to pygrub.  As of 2014, pygrub seems to be of mostly historical
   interest.
   
   pvgrub
   ------
   
   pvgrub is a version of grub that uses PV operations instead of BIOS
   calls.  It is booted from the dom0 as the domU kernel, and then reads
   /grub/menu.lst and loads a kernel from the domU filesystem.
   
   [Panix](http://www.panix.com/) lets users use pvgrub.  Panix reports
   that pvgrub works with FFsv2 with 16K/2K and 32K/4K block/frag sizes
   (and hence with defaults from "newfs -O 2").  See [Panix's pvgrub
   page](http://www.panix.com/v-colo/grub.html), which describes only
   Linux but should be updated to cover NetBSD :-)
   
   [prgmr.com](http://prgmr.com/) also lets users with pvgrub to boot
   their own kernel.  See then [prgmr.com NetBSD
   HOWTO](http://wiki.prgmr.com/mediawiki/index.php/NetBSD_as_a_DomU).
   
   It appears that [grub's FFS
   code](http://xenbits.xensource.com/hg/xen-unstable.hg/file/bca284f67702/tools/libfsimage/ufs/fsys_ufs.c)
   does not support all aspects of modern FFS, but there are also reports
   that FFSv2 works fine.  At prmgr, typically one has an ext2 or FAT
   partition for the kernel with the intent that grub can understand it,
   which leads to /netbsd not being the actual kernel.  One must remember
   to update the special boot partiion.
   
 prmgr and pvgrub  Amazon
 ----------------  ------
   
 TODO: Perhaps reference panix, prmgr, amazon as interesting examples.  TODO: add link to NetBSD amazon howto.
 Explain what prmgr does.  
   
 Using npf  Using npf
 ---------  ---------
Line 886  Using npf Line 938  Using npf
 In standard kernels, npf is a module, and thus cannot be loadeed in a  In standard kernels, npf is a module, and thus cannot be loadeed in a
 DOMU kernel.  DOMU kernel.
   
 TODO: explain how to compile npf into a custom kernel, answering:  TODO: explain how to compile npf into a custom kernel, answering (but
   note that the problem was caused by not booting the right kernel):
 http://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html  http://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html
   
   TODO items for improving NetBSD/xen
   ===================================
   
   * Package Xen 4.4.
   * Get PCI passthrough working on Xen 4.2 (or 4.4).
   * Get pvgrub into pkgsrc, either via xentools or separately.
   * grub
     * Check/add support to pkgsrc grub2 for UFS2 and arbitrary
       fragsize/blocksize (UFS2 support may be present; the point is to
       make it so that with any UFS1/UFS2 filesystem setup that works
       with NetBSD grub will also work).
       See [pkg/40258](http://gnats.netbsd.org/40258).
     * Push patches upstream.
     * Get UFS2 patches into pvgrub.
   * Add support for PV ops to a version of /boot, and make it usable as
     a kernel in Xen, similar to pvgrub.

Removed from v.1.58  
changed lines
  Added in v.1.71


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