Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.39 and 1.43

version 1.39, 2014/12/24 16:13:59 version 1.43, 2014/12/26 13:15:32
Line 301  is using xm or xl.  Note that xend is fo Line 301  is using xm or xl.  Note that xend is fo
 only be used if you plan on using "xm".  Do NOT enable xend if you  only be used if you plan on using "xm".  Do NOT enable xend if you
 plan on using "xl" as it will cause problems.  plan on using "xl" as it will cause problems.
   
   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: Give 3.1 advice (or remove it from pkgsrc).  TODO: Give 3.1 advice (or remove it from pkgsrc).
   
 For 3.3 (and thus xm), add to rc.conf (but note that you should have  For 3.3 (and thus xm), add to rc.conf (but note that you should have
Line 329  For 4.2 with xl (preferred), add to rc.c Line 334  For 4.2 with xl (preferred), add to rc.c
   
 TODO: Recommend for/against xen-watchdog.  TODO: Recommend for/against xen-watchdog.
   
 After you have configured the daemons and rebooted, run the following  After you have configured the daemons and either started them or
 (or use xl) to inspect Xen's boot messages, available resources, and  rebooted, run the following (or use xl) to inspect Xen's boot
 running domains:  messages, available resources, and running domains:
   
         xm dmesg          # xm dmesg
         xm info          [xen's boot info]
         xm list          # xm info
           [available memory, etc.]
           # xm list
           Name              Id  Mem(MB)  CPU  State  Time(s)  Console
           Domain-0           0       64    0  r----     58.1
   
   anita (for testing NetBSD)
   --------------------------
   
   With the setup so far, one should be able to run anita (see
   pkgsrc/sysutils/py-anita) to test NetBSD releases, by doing (as root,
   because anita must create a domU):
   
           anita --vmm=xm test file:///usr/obj/i386/
   
   Alternatively, one can use --vmm=xl to use xl-based domU creation instead.
   TODO: check this.
   
   Xen-specific NetBSD issues
   --------------------------
   
   There are (at least) two additional things different about NetBSD as a
   dom0 kernel compared to hardware.
   
   One is that modules are not usable in DOM0 kernels, so one must
   compile in what's needed.  It's not really that modules cannot work,
   but that modules must be built for XEN3_DOM0 because some of the
   defines change and the normal module builds don't do this.  Basically,
   enabling Xen changes the kernel ABI, and the module build system
   doesn't cope with this.
   
   The other difference is that XEN3_DOM0 does not have exactly the same
   options as GENERIC.  While it is debatable whether or not this is a
   bug, users should be aware of this and can simply add missing config
   items if desired.
   
 Updating NetBSD in a dom0  Updating NetBSD in a dom0
 -------------------------  -------------------------
Line 483  Creating specific unprivileged domains ( Line 522  Creating specific unprivileged domains (
   
 Creating domUs is almost entirely independent of operating system.  We  Creating domUs is almost entirely independent of operating system.  We
 first explain NetBSD, and then differences for Linux and Solaris.  first explain NetBSD, and then differences for Linux and Solaris.
   Note that you must have already completed the dom0 setup so that "xm
   list" (or "xl list") works.
   
 Creating an unprivileged NetBSD domain (domU)  Creating an unprivileged NetBSD domain (domU)
 ---------------------------------------------  ---------------------------------------------
   
 Once you have *domain0* running, you need to start the xen tool daemon  
 (`/usr/pkg/share/examples/rc.d/xend start`) and the xen backend daemon  
 (`/usr/pkg/share/examples/rc.d/xenbackendd start` for Xen3\*,  
 `/usr/pkg/share/examples/rc.d/xencommons start` for Xen4.\*). Make sure  
 that `/dev/xencons` and `/dev/xenevt` exist before starting `xend`. You  
 can create them with this command:  
   
     # cd /dev && sh MAKEDEV xen  
   
 xend will write logs to `/var/log/xend.log` and  
 `/var/log/xend-debug.log`. You can then control xen with the xm tool.  
 'xm list' will show something like:  
   
     # xm list  
     Name              Id  Mem(MB)  CPU  State  Time(s)  Console  
     Domain-0           0       64    0  r----     58.1  
   
 'xm create' allows you to create a new domain. It uses a config file in  'xm create' allows you to create a new domain. It uses a config file in
 PKG\_SYSCONFDIR for its parameters. By default, this file will be in  PKG\_SYSCONFDIR for its parameters. By default, this file will be in
 `/usr/pkg/etc/xen/`. On creation, a kernel has to be specified, which  `/usr/pkg/etc/xen/`. On creation, a kernel has to be specified, which
Line 627  working vif-bridge is also provided with Line 651  working vif-bridge is also provided with
   
     #!/bin/sh      #!/bin/sh
     #============================================================================      #============================================================================
     # $NetBSD: howto.mdwn,v 1.38 2014/12/24 16:07:32 gdt Exp $      # $NetBSD: howto.mdwn,v 1.42 2014/12/26 13:10:00 gdt Exp $
     #      #
     # /usr/pkg/etc/xen/vif-bridge      # /usr/pkg/etc/xen/vif-bridge
     #      #

Removed from v.1.39  
changed lines
  Added in v.1.43


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