File:  [NetBSD Developer Wiki] / wikisrc / ports / xen / howto.mdwn
Revision 1.72: download - view: text, annotated - select for diffs
Sun Jan 4 02:15:34 2015 UTC (4 years, 11 months ago) by gdt
Branches: MAIN
CVS tags: HEAD
Spell prgmr correctly.   (For some reason this is challenging.)

    1: Introduction
    2: ============
    3: 
    4: [![[Xen
    5: screenshot]](http://www.netbsd.org/gallery/in-Action/hubertf-xens.png)](http://www.netbsd.org/gallery/in-Action/hubertf-xen.png)
    6: 
    7: Xen is a hypervisor (or virtual machine monitor) for x86 hardware
    8: (i686-class or higher), which supports running multiple guest
    9: operating systems on a single physical machine.  Xen is a Type 1 or
   10: bare-metal hypervisor; one uses the Xen kernel to control the CPU,
   11: memory and console, a dom0 operating system which mediates access to
   12: other hardware (e.g., disks, network, USB), and one or more domU
   13: operating systems which operate in an unprivileged virtualized
   14: environment.  IO requests from the domU systems are forwarded by the
   15: hypervisor (Xen) to the dom0 to be fulfilled.
   16: 
   17: Xen supports two styles of guests.  The original is Para-Virtualized
   18: (PV) which means that the guest OS does not attempt to access hardware
   19: directly, but instead makes hypercalls to the hypervisor.  This is
   20: analogous to a user-space program making system calls.  (The dom0
   21: operating system uses PV calls for some functions, such as updating
   22: memory mapping page tables, but has direct hardware access for disk
   23: and network.)   PV guests must be specifically coded for Xen.
   24: 
   25: The more recent style is HVM, which means that the guest does not have
   26: code for Xen and need not be aware that it is running under Xen.
   27: Attempts to access hardware registers are trapped and emulated.  This
   28: style is less efficient but can run unmodified guests.
   29: 
   30: Generally any amd64 machine will work with Xen and PV guests.  In
   31: theory i386 computers without amd64 support can be used for Xen <=
   32: 4.2, but we have no recent reports of this working (this is a hint).
   33: For HVM guests, the VT or VMX cpu feature (Intel) or SVM/HVM/VT
   34: (amd64) is needed; "cpuctl identify 0" will show this.  TODO: Clean up
   35: and check the above features.
   36: 
   37: At boot, the dom0 kernel is loaded as a module with Xen as the kernel.
   38: The dom0 can start one or more domUs.  (Booting is explained in detail
   39: in the dom0 section.)
   40: 
   41: NetBSD supports Xen in that it can serve as dom0, be used as a domU,
   42: and that Xen kernels and tools are available in pkgsrc.  This HOWTO
   43: attempts to address both the case of running a NetBSD dom0 on hardware
   44: and running domUs under it (NetBSD and other), and also running NetBSD
   45: as a domU in a VPS.
   46: 
   47: Some versions of Xen support "PCI passthrough", which means that
   48: specific PCI devices can be made available to a specific domU instead
   49: of the dom0.  This can be useful to let a domU run X11, or access some
   50: network interface or other peripheral.
   51: 
   52: NetBSD used to support Xen2; this has been removed.
   53: 
   54: Prerequisites
   55: -------------
   56: 
   57: Installing NetBSD/Xen is not extremely difficult, but it is more
   58: complex than a normal installation of NetBSD.
   59: In general, this HOWTO is occasionally overly restrictive about how
   60: things must be done, guiding the reader to stay on the established
   61: path when there are no known good reasons to stray.
   62: 
   63: This HOWTO presumes a basic familiarity with the Xen system
   64: architecture.  This HOWTO presumes familiarity with installing NetBSD
   65: on i386/amd64 hardware and installing software from pkgsrc.
   66: See also the [Xen website](http://www.xenproject.org/).
   67: 
   68: Versions of Xen and NetBSD
   69: ==========================
   70: 
   71: Most of the installation concepts and instructions are independent
   72: of Xen version and NetBSD version.  This section gives advice on
   73: which version to choose.  Versions not in pkgsrc and older unsupported
   74: versions of NetBSD are intentionally ignored.
   75: 
   76: Xen
   77: ---
   78: 
   79: In NetBSD, xen is provided in pkgsrc, via matching pairs of packages
   80: xenkernel and xentools.  We will refer only to the kernel versions,
   81: but note that both packages must be installed together and must have
   82: matching versions.
   83: 
   84: xenkernel3 and xenkernel33 provide Xen 3.1 and 3.3.  These no longer
   85: receive security patches and should not be used.  Xen 3.1 supports PCI
   86: passthrough.  Xen 3.1 supports non-PAE on i386.
   87: 
   88: xenkernel41 provides Xen 4.1.  This is no longer maintained by Xen,
   89: but as of 2014-12 receives backported security patches.  It is a
   90: reasonable although trailing-edge choice.
   91: 
   92: xenkernel42 provides Xen 4.2.  This is maintained by Xen, but old as
   93: of 2014-12.
   94: 
   95: Ideally newer versions of Xen will be added to pkgsrc.
   96: 
   97: Note that NetBSD support is called XEN3.  It works with 3.1 through
   98: 4.2 because the hypercall interface has been stable.
   99: 
  100: Xen command program
  101: -------------------
  102: 
  103: Early Xen used a program called "xm" to manipulate the system from the
  104: dom0.  Starting in 4.1, a replacement program with similar behavior
  105: called "xl" is provided.  In 4.2 and later, "xl" is preferred.  4.4 is
  106: the last version that has "xm".
  107: 
  108: NetBSD
  109: ------
  110: 
  111: The netbsd-5, netbsd-6, netbsd-7, and -current branches are all
  112: reasonable choices, with more or less the same considerations for
  113: non-Xen use.  Therefore, netbsd-6 is recommended as the stable version
  114: of the most recent release for production use.  For those wanting to
  115: learn Xen or without production stability concerns, netbsd-7 is likely
  116: most appropriate.
  117: 
  118: As of NetBSD 6, a NetBSD domU will support multiple vcpus.  There is
  119: no SMP support for NetBSD as dom0.  (The dom0 itself doesn't really
  120: need SMP; the lack of support is really a problem when using a dom0 as
  121: a normal computer.)
  122: 
  123: Architecture
  124: ------------
  125: 
  126: Xen itself can run on i386 or amd64 machines.  (Practically, almost
  127: any computer where one would want to run Xen supports amd64.)  If
  128: using an i386 NetBSD kernel for the dom0, PAE is required (PAE
  129: versions are built by default).  While i386 dom0 works fine, amd64 is
  130: recommended as more normal.
  131: 
  132: Xen 4.2 is the last version to support i386 as a host.  TODO: Clarify
  133: if this is about the CPU having to be amd64, or about the dom0 kernel
  134: having to be amd64.
  135: 
  136: One can then run i386 domUs and amd64 domUs, in any combination.  If
  137: running an i386 NetBSD kernel as a domU, the PAE version is required.
  138: (Note that emacs (at least) fails if run on i386 with PAE when built
  139: without, and vice versa, presumably due to bugs in the undump code.)
  140: 
  141: Recommendation
  142: --------------
  143: 
  144: Therefore, this HOWTO recommends running xenkernel42 (and xentools42),
  145: xl, the NetBSD 6 stable branch, and to use an amd64 kernel as the
  146: dom0.  Either the i386 or amd64 of NetBSD may be used as domUs.
  147: 
  148: Build problems
  149: --------------
  150: 
  151: Ideally, all versions of Xen in pkgsrc would build on all versions of
  152: NetBSD on both i386 and amd64.  However, that isn't the case.  Besides
  153: aging code and aging compilers, qemu (included in xentools for HVM
  154: support) is difficult to build.  The following are known to work or FAIL:
  155: 
  156:         xenkernel3 netbsd-5 amd64
  157:         xentools3 netbsd-5 amd64
  158:         xentools3=hvm netbsd-5 amd64 ????
  159:         xenkernel33 netbsd-5 amd64
  160:         xentools33 netbsd-5 amd64
  161:         xenkernel41 netbsd-5 amd64
  162:         xentools41 netbsd-5 amd64
  163:         xenkernel42 netbsd-5 amd64
  164:         xentools42 netbsd-5 amd64
  165: 
  166:         xenkernel3 netbsd-6 i386 FAIL
  167:         xentools3 netbsd-6 i386
  168:         xentools3-hvm netbsd-6 i386 FAIL (dependencies fail)
  169:         xenkernel33 netbsd-6 i386
  170:         xentools33 netbsd-6 i386
  171:         xenkernel41 netbsd-6 i386
  172:         xentools41 netbsd-6 i386
  173:         xenkernel42 netbsd-6 i386
  174:         xentools42 netbsd-6 i386 *MIXED
  175: 
  176: 	(all 3 and 33 seem to FAIL)
  177:         xenkernel41 netbsd-7 i386
  178:         xentools41 netbsd-7 i386
  179:         xenkernel42 netbsd-7 i386
  180:         xentools42 netbsd-7 i386 ??FAIL
  181: 
  182: (*On netbsd-6 i386, there is a xentools42 in the 2014Q3 official builds,
  183: but it does not build for gdt.)
  184: 
  185: NetBSD as a dom0
  186: ================
  187: 
  188: NetBSD can be used as a dom0 and works very well.  The following
  189: sections address installation, updating NetBSD, and updating Xen.
  190: Note that it doesn't make sense to talk about installing a dom0 OS
  191: without also installing Xen itself.  We first address installing
  192: NetBSD, which is not yet a dom0, and then adding Xen, pivoting the
  193: NetBSD install to a dom0 install by just changing the kernel and boot
  194: configuration.
  195: 
  196: For experimenting with Xen, a machine with as little as 1G of RAM and
  197: 100G of disk can work.  For running many domUs in productions, far
  198: more will be needed.
  199: 
  200: Styles of dom0 operation
  201: ------------------------
  202: 
  203: There are two basic ways to use Xen.  The traditional method is for
  204: the dom0 to do absolutely nothing other than providing support to some
  205: number of domUs.  Such a system was probably installed for the sole
  206: purpose of hosting domUs, and sits in a server room on a UPS.
  207: 
  208: The other way is to put Xen under a normal-usage computer, so that the
  209: dom0 is what the computer would have been without Xen, perhaps a
  210: desktop or laptop.  Then, one can run domUs at will.  Purists will
  211: deride this as less secure than the previous approach, and for a
  212: computer whose purpose is to run domUs, they are right.  But Xen and a
  213: dom0 (without domUs) is not meaingfully less secure than the same
  214: things running without Xen.  One can boot Xen or boot regular NetBSD
  215: alternately with little problems, simply refraining from starting the
  216: Xen daemons when not running Xen.
  217: 
  218: Note that NetBSD as dom0 does not support multiple CPUs.  This will
  219: limit the performance of the Xen/dom0 workstation approach.  In theory
  220: the only issue is that the "backend drivers" are not yet MPSAFE:
  221:   http://mail-index.netbsd.org/netbsd-users/2014/08/29/msg015195.html
  222: 
  223: Installation of NetBSD
  224: ----------------------
  225: 
  226: First,
  227: [install NetBSD/amd64](/guide/inst/)
  228: just as you would if you were not using Xen.
  229: However, the partitioning approach is very important.
  230: 
  231: If you want to use RAIDframe for the dom0, there are no special issues
  232: for Xen.  Typically one provides RAID storage for the dom0, and the
  233: domU systems are unaware of RAID.  The 2nd-stage loader bootxx_* skips
  234: over a RAID1 header to find /boot from a filesystem within a RAID
  235: partition; this is no different when booting Xen.
  236: 
  237: There are 4 styles of providing backing storage for the virtual disks
  238: used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN,
  239: 
  240: With raw partitions, one has a disklabel (or gpt) partition sized for
  241: each virtual disk to be used by the domU.  (If you are able to predict
  242: how domU usage will evolve, please add an explanation to the HOWTO.
  243: Seriously, needs tend to change over time.)
  244: 
  245: One can use [lvm(8)](/guide/lvm/) to create logical devices to use
  246: for domU disks.  This is almost as efficient as raw disk partitions
  247: and more flexible.  Hence raw disk partitions should typically not
  248: be used.
  249: 
  250: One can use files in the dom0 filesystem, typically created by dd'ing
  251: /dev/zero to create a specific size.  This is somewhat less efficient,
  252: but very convenient, as one can cp the files for backup, or move them
  253: between dom0 hosts.
  254: 
  255: Finally, in theory one can place the files backing the domU disks in a
  256: SAN.  (This is an invitation for someone who has done this to add a
  257: HOWTO page.)
  258: 
  259: Installation of Xen
  260: -------------------
  261: 
  262: In the dom0, install sysutils/xenkernel42 and sysutils/xentools42 from
  263: pkgsrc (or another matching pair).
  264: See [the pkgsrc
  265: documentation](http://www.NetBSD.org/docs/pkgsrc/) for help with pkgsrc.
  266: 
  267: For Xen 3.1, support for HVM guests is in sysutils/xentool3-hvm.  More
  268: recent versions have HVM support integrated in the main xentools
  269: package.  It is entirely reasonable to run only PV guests.
  270: 
  271: Next you need to install the selected Xen kernel itself, which is
  272: installed by pkgsrc as "/usr/pkg/xen*-kernel/xen.gz".  Copy it to /.
  273: For debugging, one may copy xen-debug.gz; this is conceptually similar
  274: to DIAGNOSTIC and DEBUG in NetBSD.  xen-debug.gz is basically only
  275: useful with a serial console.  Then, place a NetBSD XEN3_DOM0 kernel
  276: in /, copied from releasedir/amd64/binary/kernel/netbsd-XEN3_DOM0.gz
  277: of a NetBSD build.  Both xen and NetBSD may be left compressed.  (If
  278: using i386, use releasedir/i386/binary/kernel/netbsd-XEN3PAE_DOM0.gz.)
  279: 
  280: With Xen as the kernel, you must provide a dom0 NetBSD kernel to be
  281: used as a module; place this in /.  Suitable kernels are provided in
  282: releasedir/binary/kernel:
  283: 
  284:         i386 XEN3_DOM0
  285:         i386 XEN3PAE_DOM0
  286: 	amd64 XEN3_DOM0
  287: 
  288: The first one is only for use with Xen 3.1 and i386-mode Xen (and you
  289: should not do this).  Current Xen always uses PAE on i386, but you
  290: should generally use amd64 for the dom0.  In a dom0 kernel, kernfs is
  291: mandatory for xend to comunicate with the kernel, so ensure that /kern
  292: is in fstab.  TODO: Say this is default, or file a PR and give a
  293: reference.
  294: 
  295: Because you already installed NetBSD, you have a working boot setup
  296: with an MBR bootblock, either bootxx_ffsv1 or bootxx_ffsv2 at the
  297: beginning of your root filesystem, /boot present, and likely
  298: /boot.cfg.  (If not, fix before continuing!)
  299: 
  300: See boot.cfg(5) for an example.  The basic line is
  301: 
  302:         menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=256M
  303: 
  304: which specifies that the dom0 should have 256M, leaving the rest to be
  305: allocated for domUs.  In an attempt to add performance, one can also
  306: add
  307: 
  308:         dom0_max_vcpus=1 dom0_vcpus_pin
  309: 
  310: to force only one vcpu to be provided (since NetBSD dom0 can't use
  311: more) and to pin that vcpu to a physical cpu.  TODO: benchmark this.
  312: 
  313: As with non-Xen systems, you should have a line to boot /netbsd (a
  314: kernel that works without Xen) and fallback versions of the non-Xen
  315: kernel, Xen, and the dom0 kernel.
  316: 
  317: Using grub (historic)
  318: ---------------------
  319: 
  320: Before NetBSD's native bootloader could support Xen, the use of
  321: grub was recommended.  If necessary, see the
  322: [old grub information](/ports/xen/howto-grub/).
  323: 
  324: The [HowTo on Installing into
  325: RAID-1](http://mail-index.NetBSD.org/port-xen/2006/03/01/0010.html)
  326: explains how to set up booting a dom0 with Xen using grub with
  327: NetBSD's RAIDframe.  (This is obsolete with the use of NetBSD's native
  328: boot.)
  329: 
  330: Configuring Xen
  331: ---------------
  332: 
  333: Xen logs will be in /var/log/xen.
  334: 
  335: Now, you have a system that will boot Xen and the dom0 kernel, and
  336: just run the dom0 kernel.  There will be no domUs, and none can be
  337: started because you still have to configure the dom0 tools.  The
  338: daemons which should be run vary with Xen version and with whether one
  339: is using xm or xl.  Note that xend is for supporting "xm", and should
  340: only be used if you plan on using "xm".  Do NOT enable xend if you
  341: plan on using "xl" as it will cause problems.
  342: 
  343: The installation of NetBSD should already have created devices for xen
  344: (xencons, xenevt), but if they are not present, create them:
  345: 
  346:         cd /dev && sh MAKEDEV xen
  347: 
  348: TODO: Give 3.1 advice (or remove it from pkgsrc).
  349: 
  350: For 3.3 (and thus xm), add to rc.conf (but note that you should have
  351: installed 4.1 or 4.2):
  352: 
  353:         xend=YES
  354:         xenbackendd=YES
  355: 
  356: For 4.1 (and thus xm; xl is believed not to work well), add to rc.conf:
  357: 
  358:         xencommons=YES
  359:         xend=YES
  360: 
  361: (If you are using xentools41 from before 2014-12-26, change
  362: rc.d/xendomains to use xm rather than xl.)
  363: 
  364: For 4.2 with xm, add to rc.conf
  365: 
  366:         xencommons=YES
  367:         xend=YES
  368: 
  369: For 4.2 with xl (preferred), add to rc.conf:
  370: 
  371:         xencommons=YES
  372:         TODO: explain if there is a xend replacement
  373: 
  374: TODO: Recommend for/against xen-watchdog.
  375: 
  376: After you have configured the daemons and either started them (in the
  377: order given) or rebooted, run the following (or use xl) to inspect
  378: Xen's boot messages, available resources, and running domains:
  379: 
  380:         # xm dmesg
  381: 	[xen's boot info]
  382:         # xm info
  383: 	[available memory, etc.]
  384:         # xm list
  385:         Name              Id  Mem(MB)  CPU  State  Time(s)  Console
  386:         Domain-0           0       64    0  r----     58.1
  387: 
  388: anita (for testing NetBSD)
  389: --------------------------
  390: 
  391: With the setup so far, one should be able to run anita (see
  392: pkgsrc/sysutils/py-anita) to test NetBSD releases, by doing (as root,
  393: because anita must create a domU):
  394: 
  395:         anita --vmm=xm test file:///usr/obj/i386/
  396: 
  397: Alternatively, one can use --vmm=xl to use xl-based domU creation instead.
  398: TODO: check this.
  399: 
  400: Xen-specific NetBSD issues
  401: --------------------------
  402: 
  403: There are (at least) two additional things different about NetBSD as a
  404: dom0 kernel compared to hardware.
  405: 
  406: One is that modules are not usable in DOM0 kernels, so one must
  407: compile in what's needed.  It's not really that modules cannot work,
  408: but that modules must be built for XEN3_DOM0 because some of the
  409: defines change and the normal module builds don't do this.  Basically,
  410: enabling Xen changes the kernel ABI, and the module build system
  411: doesn't cope with this.
  412: 
  413: The other difference is that XEN3_DOM0 does not have exactly the same
  414: options as GENERIC.  While it is debatable whether or not this is a
  415: bug, users should be aware of this and can simply add missing config
  416: items if desired.
  417: 
  418: Updating NetBSD in a dom0
  419: -------------------------
  420: 
  421: This is just like updating NetBSD on bare hardware, assuming the new
  422: version supports the version of Xen you are running.  Generally, one
  423: replaces the kernel and reboots, and then overlays userland binaries
  424: and adjusts /etc.
  425: 
  426: Note that one must update both the non-Xen kernel typically used for
  427: rescue purposes and the DOM0 kernel used with Xen.
  428: 
  429: Converting from grub to /boot
  430: -----------------------------
  431: 
  432: These instructions were [TODO: will be] used to convert a system from
  433: grub to /boot.  The system was originally installed in February of
  434: 2006 with a RAID1 setup and grub to boot Xen 2, and has been updated
  435: over time.  Before these commands, it was running NetBSD 6 i386, Xen
  436: 4.1 and grub, much like the message linked earlier in the grub
  437: section.
  438: 
  439:         # Install mbr bootblocks on both disks. 
  440:         fdisk -i /dev/rwd0d
  441:         fdisk -i /dev/rwd1d
  442:         # Install NetBSD primary boot loader (/ is FFSv1) into RAID1 components.
  443:         installboot -v /dev/rwd0d /usr/mdec/bootxx_ffsv1
  444:         installboot -v /dev/rwd1d /usr/mdec/bootxx_ffsv1
  445:         # Install secondary boot loader
  446:         cp -p /usr/mdec/boot /
  447:         # Create boog.cfg following earlier guidance:
  448:         menu=Xen:load /netbsd-XEN3PAE_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=256M
  449:         menu=Xen.ok:load /netbsd-XEN3PAE_DOM0.ok.gz console=pc;multiboot /xen.ok.gz dom0_mem=256M
  450:         menu=GENERIC:boot
  451:         menu=GENERIC single-user:boot -s
  452:         menu=GENERIC.ok:boot netbsd.ok
  453:         menu=GENERIC.ok single-user:boot netbsd.ok -s
  454:         menu=Drop to boot prompt:prompt
  455:         default=1
  456:         timeout=30
  457: 
  458: TODO: actually do this and fix it if necessary.
  459: 
  460: Updating Xen versions
  461: ---------------------
  462: 
  463: Updating Xen is conceptually not difficult, but can run into all the
  464: issues found when installing Xen.  Assuming migration from 4.1 to 4.2,
  465: remove the xenkernel41 and xentools41 packages and install the
  466: xenkernel42 and xentools42 packages.  Copy the 4.2 xen.gz to /.
  467: 
  468: Ensure that the contents of /etc/rc.d/xen* are correct.  Enable the
  469: correct set of daemons.  Ensure that the domU config files are valid
  470: for the new version.
  471: 
  472: 
  473: Unprivileged domains (domU)
  474: ===========================
  475: 
  476: This section describes general concepts about domUs.  It does not
  477: address specific domU operating systems or how to install them.  The
  478: config files for domUs are typically in /usr/pkg/etc/xen, and are
  479: typically named so that the file name, domU name and the domU's host
  480: name match.
  481: 
  482: The domU is provided with cpu and memory by Xen, configured by the
  483: dom0.  The domU is provided with disk and network by the dom0,
  484: mediated by Xen, and configured in the dom0.
  485: 
  486: Entropy in domUs can be an issue; physical disks and network are on
  487: the dom0.  NetBSD's /dev/random system works, but is often challenged.
  488: 
  489: Config files
  490: ------------
  491: 
  492: There is no good order to present config files and the concepts
  493: surrounding what is being configured.  We first show an example config
  494: file, and then in the various sections give details.
  495: 
  496: See (at least in xentools41) /usr/pkg/share/examples/xen/xmexample*,
  497: for a large number of well-commented examples, mostly for running
  498: GNU/Linux.
  499: 
  500: The following is an example minimal domain configuration file
  501: "/usr/pkg/etc/xen/foo".  It is (with only a name change) an actual
  502: known working config file on Xen 4.1 (NetBSD 5 amd64 dom0 and NetBSD 5
  503: i386 domU).  The domU serves as a network file server.
  504: 
  505:         # -*- mode: python; -*-
  506: 
  507:         kernel = "/netbsd-XEN3PAE_DOMU-i386-foo.gz"
  508:         memory = 1024
  509:         vif = [ 'mac=aa:00:00:d1:00:09,bridge=bridge0' ]
  510:         disk = [ 'file:/n0/xen/foo-wd0,0x0,w',
  511:                  'file:/n0/xen/foo-wd1,0x1,w' ]
  512: 
  513: The domain will have the same name as the file.  The kernel has the
  514: host/domU name in it, so that on the dom0 one can update the various
  515: domUs independently.  The vif line causes an interface to be provided,
  516: with a specific mac address (do not reuse MAC addresses!), in bridge
  517: mode.  Two disks are provided, and they are both writable; the bits
  518: are stored in files and Xen attaches them to a vnd(4) device in the
  519: dom0 on domain creation.  The system treates xbd0 as the boot device
  520: without needing explicit configuration.
  521: 
  522: By default xm looks for domain config files in /usr/pkg/etc/xen.  Note
  523: that "xm create" takes the name of a config file, while other commands
  524: take the name of a domain.  To create the domain, connect to the
  525: console, create the domain while attaching the console, shutdown the
  526: domain, and see if it has finished stopping, do (or xl with Xen >=
  527: 4.2):
  528: 
  529:         xm create foo
  530:         xm console foo
  531:         xm create -c foo
  532:         xm shutdown foo
  533: 	xm list
  534: 
  535: Typing ^] will exit the console session.  Shutting down a domain is
  536: equivalent to pushing the power button; a NetBSD domU will receive a
  537: power-press event and do a clean shutdown.  Shutting down the dom0
  538: will trigger controlled shutdowns of all configured domUs.
  539: 
  540: domU kernels
  541: ------------
  542: 
  543: On a physical computer, the BIOS reads sector 0, and a chain of boot
  544: loaders finds and loads a kernel.  Normally this comes from the root
  545: filesystem.  With Xen domUs, the process is totally different.  The
  546: normal path is for the domU kernel to be a file in the dom0's
  547: filesystem.  At the request of the dom0, Xen loads that kernel into a
  548: new domU instance and starts execution.  While domU kernels can be
  549: anyplace, reasonable places to store domU kernels on the dom0 are in /
  550: (so they are near the dom0 kernel), in /usr/pkg/etc/xen (near the
  551: config files), or in /u0/xen (where the vdisks are).
  552: 
  553: Note that loading the domU kernel from the dom0 implies that boot
  554: blocks, /boot, /boot.cfg, and so on are all ignored in the domU.
  555: See the VPS section near the end for discussion of alternate ways to
  556: obtain domU kernels.
  557: 
  558: CPU and memory
  559: --------------
  560: 
  561: A domain is provided with some number of vcpus, less than the number
  562: of cpus seen by the hypervisor.  (For a dom0, this is controlled by
  563: the boot argument "dom0_max_vcpus=1".)  For a domU, it is controlled
  564: from the config file by the "vcpus = N" directive.
  565: 
  566: A domain is provided with memory; this is controlled in the config
  567: file by "memory = N" (in megabytes).  In the straightforward case, the
  568: sum of the the memory allocated to the dom0 and all domUs must be less
  569: than the available memory.
  570: 
  571: Xen also provides a "balloon" driver, which can be used to let domains
  572: use more memory temporarily.  TODO: Explain better, and explain how
  573: well it works with NetBSD.
  574: 
  575: Virtual disks
  576: -------------
  577: 
  578: With the file/vnd style, typically one creates a directory,
  579: e.g. /u0/xen, on a disk large enough to hold virtual disks for all
  580: domUs.  Then, for each domU disk, one writes zeros to a file that then
  581: serves to hold the virtual disk's bits; a suggested name is foo-xbd0
  582: for the first virtual disk for the domU called foo.  Writing zeros to
  583: the file serves two purposes.  One is that preallocating the contents
  584: improves performance.  The other is that vnd on sparse files has
  585: failed to work.  TODO: give working/notworking NetBSD versions for
  586: sparse vnd.  Note that the use of file/vnd for Xen is not really
  587: different than creating a file-backed virtual disk for some other
  588: purpose, except that xentools handles the vnconfig commands.  To
  589: create an empty 4G virtual disk, simply do
  590: 
  591:         dd if=/dev/zero of=foo-xbd0 bs=1m count=4096
  592: 
  593: With the lvm style, one creates logical devices.  They are then used
  594: similarly to vnds.  TODO: Add an example with lvm.
  595: 
  596: In domU config files, the disks are defined as a sequence of 3-tuples.
  597: The first element is "method:/path/to/disk".  Common methods are
  598: "file:" for file-backed vnd. and "phy:" for something that is already
  599: a (TODO: character or block) device.
  600: 
  601: The second element is an artifact of how virtual disks are passed to
  602: Linux, and a source of confusion with NetBSD Xen usage.  Linux domUs
  603: are given a device name to associate with the disk, and values like
  604: "hda1" or "sda1" are common.  In a NetBSD domU, the first disk appears
  605: as xbd0, the second as xbd1, and so on.  However, xm/xl demand a
  606: second argument.  The name given is converted to a major/minor by
  607: calling stat(2) on the name in /dev and this is passed to the domU.
  608: In the general case, the dom0 and domU can be different operating
  609: systems, and it is an unwarranted assumption that they have consistent
  610: numbering in /dev, or even that the dom0 OS has a /dev.  With NetBSD
  611: as both dom0 and domU, using values of 0x0 for the first disk and 0x1
  612: for the second works fine and avoids this issue.  For a GNU/Linux
  613: guest, one can create /dev/hda1 in /dev, or to pass 0x301 for
  614: /dev/hda1.
  615: 
  616: The third element is "w" for writable disks, and "r" for read-only
  617: disks.
  618: 
  619: Virtual Networking
  620: ------------------
  621: 
  622: Xen provides virtual ethernets, each of which connects the dom0 and a
  623: domU.  For each virtual network, there is an interface "xvifN.M" in
  624: the dom0, and in domU index N, a matching interface xennetM (NetBSD
  625: name).  The interfaces behave as if there is an Ethernet with two
  626: adaptors connected.  From this primitive, one can construct various
  627: configurations.  We focus on two common and useful cases for which
  628: there are existing scripts: bridging and NAT.
  629: 
  630: With bridging (in the example above), the domU perceives itself to be
  631: on the same network as the dom0.  For server virtualization, this is
  632: usually best.  Bridging is accomplished by creating a bridge(4) device
  633: and adding the dom0's physical interface and the various xvifN.0
  634: interfaces to the bridge.  One specifies "bridge=bridge0" in the domU
  635: config file.  The bridge must be set up already in the dom0; an
  636: example /etc/ifconfig.bridge0 is:
  637: 
  638:         create
  639:         up
  640:         !brconfig bridge0 add wm0
  641: 
  642: With NAT, the domU perceives itself to be behind a NAT running on the
  643: dom0.  This is often appropriate when running Xen on a workstation.
  644: TODO: NAT appears to be configured by "vif = [ '' ]".
  645: 
  646: The MAC address specified is the one used for the interface in the new
  647: domain.  The interface in dom0 will use this address XOR'd with
  648: 00:00:00:01:00:00.  Random MAC addresses are assigned if not given.
  649: 
  650: Sizing domains
  651: --------------
  652: 
  653: Modern x86 hardware has vast amounts of resources.  However, many
  654: virtual servers can function just fine on far less.  A system with
  655: 256M of RAM and a 4G disk can be a reasonable choice.  Note that it is
  656: far easier to adjust virtual resources than physical ones.  For
  657: memory, it's just a config file edit and a reboot.  For disk, one can
  658: create a new file and vnconfig it (or lvm), and then dump/restore,
  659: just like updating physical disks, but without having to be there and
  660: without those pesky connectors.
  661: 
  662: Starting domains automatically
  663: ------------------------------
  664: 
  665: To start domains foo at bar at boot and shut them down cleanly on dom0
  666: shutdown, in rc.conf add:
  667: 
  668:         xendomains="foo bar"
  669: 
  670: TODO: Explain why 4.1 rc.d/xendomains has xl, when one should use xm
  671: on 4.1.  Or fix the xentools41 package to have xm
  672: 
  673: Creating specific unprivileged domains (domU)
  674: =============================================
  675: 
  676: Creating domUs is almost entirely independent of operating system.  We
  677: have already presented the basics of config files.  Note that you must
  678: have already completed the dom0 setup so that "xl list" (or "xm list")
  679: works.
  680: 
  681: Creating an unprivileged NetBSD domain (domU)
  682: ---------------------------------------------
  683: 
  684: See the earlier config file, and adjust memory.  Decide on how much
  685: storage you will provide, and prepare it (file or lvm).
  686: 
  687: While the kernel will be obtained from the dom0 filesystem, the same
  688: file should be present in the domU as /netbsd so that tools like
  689: savecore(8) can work.   (This is helpful but not necessary.)
  690: 
  691: The kernel must be specifically for Xen and for use as a domU.  The
  692: i386 and amd64 provide the following kernels:
  693: 
  694:         i386 XEN3_DOMU
  695:         i386 XEN3PAE_DOMU
  696: 	amd64 XEN3_DOMU
  697: 
  698: Unless using Xen 3.1 (and you shouldn't) with i386-mode Xen, you must
  699: use the PAE version of the i386 kernel.
  700: 
  701: This will boot NetBSD, but this is not that useful if the disk is
  702: empty.  One approach is to unpack sets onto the disk outside of xen
  703: (by mounting it, just as you would prepare a physical disk for a
  704: system you can't run the installer on).
  705: 
  706: A second approach is to run an INSTALL kernel, which has a miniroot
  707: and can load sets from the network.  To do this, copy the INSTALL
  708: kernel to / and change the kernel line in the config file to:
  709: 
  710:         kernel = "/home/bouyer/netbsd-INSTALL_XEN3_DOMU"
  711: 
  712: Then, start the domain as "xl create -c configname".
  713: 
  714: Alternatively, if you want to install NetBSD/Xen with a CDROM image, the following
  715: line should be used in the config file.
  716: 
  717:     disk = [ 'phy:/dev/wd0e,0x1,w', 'phy:/dev/cd0a,0x2,r' ]
  718: 
  719: After booting the domain, the option to install via CDROM may be
  720: selected.  The CDROM device should be changed to `xbd1d`.
  721: 
  722: Once done installing, "halt -p" the new domain (don't reboot or halt,
  723: it would reload the INSTALL_XEN3_DOMU kernel even if you changed the
  724: config file), switch the config file back to the XEN3_DOMU kernel,
  725: and start the new domain again. Now it should be able to use "root on
  726: xbd0a" and you should have a, functional NetBSD domU.
  727: 
  728: TODO: check if this is still accurate.
  729: When the new domain is booting you'll see some warnings about *wscons*
  730: and the pseudo-terminals. These can be fixed by editing the files
  731: `/etc/ttys` and `/etc/wscons.conf`. You must disable all terminals in
  732: `/etc/ttys`, except *console*, like this:
  733: 
  734:     console "/usr/libexec/getty Pc"         vt100   on secure
  735:     ttyE0   "/usr/libexec/getty Pc"         vt220   off secure
  736:     ttyE1   "/usr/libexec/getty Pc"         vt220   off secure
  737:     ttyE2   "/usr/libexec/getty Pc"         vt220   off secure
  738:     ttyE3   "/usr/libexec/getty Pc"         vt220   off secure
  739: 
  740: Finally, all screens must be commented out from `/etc/wscons.conf`.
  741: 
  742: It is also desirable to add
  743: 
  744:         powerd=YES
  745: 
  746: in rc.conf. This way, the domain will be properly shut down if
  747: `xm shutdown -R` or `xm shutdown -H` is used on the dom0.
  748: 
  749: Your domain should be now ready to work, enjoy.
  750: 
  751: Creating an unprivileged Linux domain (domU)
  752: --------------------------------------------
  753: 
  754: Creating unprivileged Linux domains isn't much different from
  755: unprivileged NetBSD domains, but there are some details to know.
  756: 
  757: First, the second parameter passed to the disk declaration (the '0x1' in
  758: the example below)
  759: 
  760:     disk = [ 'phy:/dev/wd0e,0x1,w' ]
  761: 
  762: does matter to Linux. It wants a Linux device number here (e.g. 0x300
  763: for hda).  Linux builds device numbers as: (major \<\< 8 + minor).
  764: So, hda1 which has major 3 and minor 1 on a Linux system will have
  765: device number 0x301.  Alternatively, devices names can be used (hda,
  766: hdb, ...)  as xentools has a table to map these names to devices
  767: numbers.  To export a partition to a Linux guest we can use:
  768: 
  769:         disk = [ 'phy:/dev/wd0e,0x300,w' ]
  770:         root = "/dev/hda1 ro"
  771: 
  772: and it will appear as /dev/hda on the Linux system, and be used as root
  773: partition.
  774: 
  775: To install the Linux system on the partition to be exported to the
  776: guest domain, the following method can be used: install
  777: sysutils/e2fsprogs from pkgsrc.  Use mke2fs to format the partition
  778: that will be the root partition of your Linux domain, and mount it.
  779: Then copy the files from a working Linux system, make adjustments in
  780: `/etc` (fstab, network config).  It should also be possible to extract
  781: binary packages such as .rpm or .deb directly to the mounted partition
  782: using the appropriate tool, possibly running under NetBSD's Linux
  783: emulation.  Once the filesystem has been populated, umount it.  If
  784: desirable, the filesystem can be converted to ext3 using tune2fs -j.
  785: It should now be possible to boot the Linux guest domain, using one of
  786: the vmlinuz-\*-xenU kernels available in the Xen binary distribution.
  787: 
  788: To get the linux console right, you need to add:
  789: 
  790:     extra = "xencons=tty1"
  791: 
  792: to your configuration since not all linux distributions auto-attach a
  793: tty to the xen console.
  794: 
  795: Creating an unprivileged Solaris domain (domU)
  796: ----------------------------------------------
  797: 
  798: See possibly outdated
  799: [Solaris domU instructions](/ports/xen/howto-solaris/).
  800: 
  801: 
  802: PCI passthrough: Using PCI devices in guest domains
  803: ---------------------------------------------------
  804: 
  805: The dom0 can give other domains access to selected PCI
  806: devices. This can allow, for example, a non-privileged domain to have
  807: access to a physical network interface or disk controller.  However,
  808: keep in mind that giving a domain access to a PCI device most likely
  809: will give the domain read/write access to the whole physical memory,
  810: as PCs don't have an IOMMU to restrict memory access to DMA-capable
  811: device.  Also, it's not possible to export ISA devices to non-dom0
  812: domains, which means that the primary VGA adapter can't be exported.
  813: A guest domain trying to access the VGA registers will panic.
  814: 
  815: If the dom0 is NetBSD, it has to be running Xen 3.1, as support has
  816: not been ported to later versions at this time.
  817: 
  818: For a PCI device to be exported to a domU, is has to be attached to
  819: the "pciback" driver in dom0.  Devices passed to the dom0 via the
  820: pciback.hide boot parameter will attach to "pciback" instead of the
  821: usual driver.  The list of devices is specified as "(bus:dev.func)",
  822: where bus and dev are 2-digit hexadecimal numbers, and func a
  823: single-digit number:
  824: 
  825:         pciback.hide=(00:0a.0)(00:06.0)
  826: 
  827: pciback devices should show up in the dom0's boot messages, and the
  828: devices should be listed in the `/kern/xen/pci` directory.
  829: 
  830: PCI devices to be exported to a domU are listed in the "pci" array of
  831: the domU's config file, with the format "0000:bus:dev.func".
  832: 
  833:         pci = [ '0000:00:06.0', '0000:00:0a.0' ]
  834: 
  835: In the domU an "xpci" device will show up, to which one or more pci
  836: busses will attach.  Then the PCI drivers will attach to PCI busses as
  837: usual.  Note that the default NetBSD DOMU kernels do not have "xpci"
  838: or any PCI drivers built in by default; you have to build your own
  839: kernel to use PCI devices in a domU.  Here's a kernel config example;
  840: note that only the "xpci" lines are unusual.
  841: 
  842:         include         "arch/i386/conf/XEN3_DOMU"
  843: 
  844:         # Add support for PCI busses to the XEN3_DOMU kernel
  845:         xpci* at xenbus ?
  846:         pci* at xpci ?
  847: 
  848:         # PCI USB controllers
  849:         uhci*   at pci? dev ? function ?        # Universal Host Controller (Intel)
  850: 
  851:         # USB bus support
  852:         usb*    at uhci?
  853: 
  854:         # USB Hubs
  855:         uhub*   at usb?
  856:         uhub*   at uhub? port ? configuration ? interface ?
  857: 
  858:         # USB Mass Storage
  859:         umass*  at uhub? port ? configuration ? interface ?
  860:         wd*     at umass?
  861:         # SCSI controllers
  862:         ahc*    at pci? dev ? function ?        # Adaptec [23]94x, aic78x0 SCSI
  863: 
  864:         # SCSI bus support (for both ahc and umass)
  865:         scsibus* at scsi?
  866: 
  867:         # SCSI devices
  868:         sd*     at scsibus? target ? lun ?      # SCSI disk drives
  869:         cd*     at scsibus? target ? lun ?      # SCSI CD-ROM drives
  870: 
  871: 
  872: NetBSD as a domU in a VPS
  873: =========================
  874: 
  875: The bulk of the HOWTO is about using NetBSD as a dom0 on your own
  876: hardware.  This section explains how to deal with Xen in a domU as a
  877: virtual private server where you do not control or have access to the
  878: dom0.  This is not intended to be an exhaustive list of VPS providers;
  879: only a few are mentioned that specifically support NetBSD.
  880: 
  881: VPS operators provide varying degrees of access and mechanisms for
  882: configuration.  The big issue is usually how one controls which kernel
  883: is booted, because the kernel is nominally in the dom0 filesystem (to
  884: which VPS users do not normally have acesss).  A second issue is how
  885: to install NetBSD.
  886: 
  887: A VPS user may want to compile a kernel for security updates, to run
  888: npf, run IPsec, or any other reason why someone would want to change
  889: their kernel.
  890: 
  891: One approach is to have an adminstrative interface to upload a kernel,
  892: or to select from a prepopulated list.  Other approaches are pygrub
  893: (deprecated) and pvgrub, which are ways to have a bootloader obtain a
  894: kernel from the domU filesystem.  This is closer to a regular physical
  895: computer, where someone who controls a machine can replace the kernel.
  896: 
  897: pygrub
  898: -------
  899: 
  900: pygrub runs in the dom0 and looks into the domU filesystem.  This
  901: implies that the domU must have a kernel in a filesystem in a format
  902: known to pygrub.  As of 2014, pygrub seems to be of mostly historical
  903: interest.
  904: 
  905: pvgrub
  906: ------
  907: 
  908: pvgrub is a version of grub that uses PV operations instead of BIOS
  909: calls.  It is booted from the dom0 as the domU kernel, and then reads
  910: /grub/menu.lst and loads a kernel from the domU filesystem.
  911: 
  912: [Panix](http://www.panix.com/) lets users use pvgrub.  Panix reports
  913: that pvgrub works with FFsv2 with 16K/2K and 32K/4K block/frag sizes
  914: (and hence with defaults from "newfs -O 2").  See [Panix's pvgrub
  915: page](http://www.panix.com/v-colo/grub.html), which describes only
  916: Linux but should be updated to cover NetBSD :-)
  917: 
  918: [prgmr.com](http://prgmr.com/) also lets users with pvgrub to boot
  919: their own kernel.  See then [prgmr.com NetBSD
  920: HOWTO](http://wiki.prgmr.com/mediawiki/index.php/NetBSD_as_a_DomU).
  921: 
  922: It appears that [grub's FFS
  923: code](http://xenbits.xensource.com/hg/xen-unstable.hg/file/bca284f67702/tools/libfsimage/ufs/fsys_ufs.c)
  924: does not support all aspects of modern FFS, but there are also reports
  925: that FFSv2 works fine.  At prgmr, typically one has an ext2 or FAT
  926: partition for the kernel with the intent that grub can understand it,
  927: which leads to /netbsd not being the actual kernel.  One must remember
  928: to update the special boot partiion.
  929: 
  930: Amazon
  931: ------
  932: 
  933: TODO: add link to NetBSD amazon howto.
  934: 
  935: Using npf
  936: ---------
  937: 
  938: In standard kernels, npf is a module, and thus cannot be loadeed in a
  939: DOMU kernel.
  940: 
  941: TODO: explain how to compile npf into a custom kernel, answering (but
  942: note that the problem was caused by not booting the right kernel):
  943: http://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html
  944: 
  945: TODO items for improving NetBSD/xen
  946: ===================================
  947: 
  948: * Package Xen 4.4.
  949: * Get PCI passthrough working on Xen 4.2 (or 4.4).
  950: * Get pvgrub into pkgsrc, either via xentools or separately.
  951: * grub
  952:   * Check/add support to pkgsrc grub2 for UFS2 and arbitrary
  953:     fragsize/blocksize (UFS2 support may be present; the point is to
  954:     make it so that with any UFS1/UFS2 filesystem setup that works
  955:     with NetBSD grub will also work).
  956:     See [pkg/40258](http://gnats.netbsd.org/40258).
  957:   * Push patches upstream.
  958:   * Get UFS2 patches into pvgrub.
  959: * Add support for PV ops to a version of /boot, and make it usable as
  960:   a kernel in Xen, similar to pvgrub.

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