Diff for /wikisrc/ports/xen/howto.mdwn between versions 1.19 and 1.20

version 1.19, 2014/12/24 00:41:04 version 1.20, 2014/12/24 01:06:43
Line 28  Attempts to access hardware registers ar Line 28  Attempts to access hardware registers ar
 style is less efficient but can run unmodified guests.  style is less efficient but can run unmodified guests.
   
 Generally any amd64 machine will work with Xen and PV guests.  For HVM  Generally any amd64 machine will work with Xen and PV guests.  For HVM
 guests, the VMX cpu feature (Intel) or VT?? (amd64) is needed.  TODO:  guests, the VT or VMX cpu feature (Intel) or SVM/HVM/VT (amd64) is
 Explain if i386 (non-amd64) machines can still be used - I think that  needed; "cpuctl identify 0" will show this.  TODO: Clean up and check
 witthe requirement to use PAE kernels is about the hypervisor being  the above features.  TODO: Explain if i386 (non-amd64) machines can
 amd64 only.  still be used - I think that witthe requirement to use PAE kernels is
   about the hypervisor being amd64 only.
   
 At boot, the dom0 kernel is loaded as module with Xen as the kernel.  At boot, the dom0 kernel is loaded as module with Xen as the kernel.
 The dom0 can start one or more domUs.  (Booting is explained in detail  The dom0 can start one or more domUs.  (Booting is explained in detail
Line 42  and that Xen kernels and tools are avail Line 43  and that Xen kernels and tools are avail
 attempts to address both the case of running a NetBSD dom0 on hardware  attempts to address both the case of running a NetBSD dom0 on hardware
 and running NetBSD as a domU in a VPS.  and running NetBSD as a domU in a VPS.
   
   Some versions of Xen support "PCI passthrough", which means that
   specific PCI devices can be made available to a specific domU instead
   of the dom0.  This can be useful to let a domU run X11, or access some
   network interface or other peripheral.
   
 Prerequisites  Prerequisites
 -------------  -------------
   
Line 82  but note that both packages must be inst Line 88  but note that both packages must be inst
 matching versions.  matching versions.
   
 xenkernel3 and xenkernel33 provide Xen 3.1 and 3.3.  These no longer  xenkernel3 and xenkernel33 provide Xen 3.1 and 3.3.  These no longer
 receive security patches and should not be used.  receive security patches and should not be used.  Xen 3.1 supports PCI
   passthrough.
   
 xenkernel41 provides Xen 4.1.  This is no longer maintained by Xen,  xenkernel41 provides Xen 4.1.  This is no longer maintained by Xen,
 but as of 2014-12 receives backported security patches.  It is a  but as of 2014-12 receives backported security patches.  It is a
Line 93  of 2014-12. Line 100  of 2014-12.
   
 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 3.1 through
   4.2, because the hypercall interface has been stable.
   
 Xen command program  Xen command program
 -------------------  -------------------
   
Line 199  HOWTO page.) Line 209  HOWTO page.)
 Installation of Xen  Installation of Xen
 -------------------  -------------------
   
 Next step is to install the Xen packages via pkgsrc or from binary  In the dom0, install sysutils/xenkernel42 and sysutils/xentools42 from
 packages. See [the pkgsrc  pkgsrc (or another matching pair).
 documentation](http://www.NetBSD.org/docs/pkgsrc/) if you are unfamiliar  See [the pkgsrc
 with pkgsrc and/or handling of binary packages. Xen 3.1, 3.3, 4.1 and  documentation](http://www.NetBSD.org/docs/pkgsrc/) for help with pkgsrc.
 4.2 are available. 3.1 supports PCI pass-through while other versions do  
 not. You'll need either `sysutils/xentools3` and `sysutils/xenkernel3`  For Xen 3.1, support for HVM guests is in sysutils/xentool3-hvm.  More
 for Xen 3.1, `sysutils/xentools33` and `sysutils/xenkernel33` for Xen  recent versions have HVM support integrated in the main xentools
 3.3, `sysutils/xentools41` and `sysutils/xenkernel41` for Xen 4.1. or  package.  It is entirely reasonable to run only PV guests.
 `sysutils/xentools42` and `sysutils/xenkernel42` for Xen 4.2. You'll  
 also need `sysutils/grub` if you plan do use the grub boot loader. If  Next you need to install the selected Xen kernel itself, which is
 using Xen 3.1, you may also want to install `sysutils/xentools3-hvm`  installed by pkgsrc as "/usr/pkg/xen*-kernel/xen.gz".  Copy it to /.
 which contains the utilities to run unmodified guests OSes using the  For debugging, one may copy xen-debug.gz; this is conceptually similar
 *HVM* support (for later versions this is included in  to DIAGNOSTIC and DEBUG in NetBSD.  xen-debug.gz is basically only
 `sysutils/xentools`). Note that your CPU needs to support this. Intel  useful with a serial console.  Then, place a NetBSD XEN3_DOM0 kernel
 CPUs must have the 'VT' instruction, AMD CPUs the 'SVM' instruction. You  in /, copied from releasedir/amd64/binary/kernel/netbsd-XEN3_DOM0.gz
 can easily find out if your CPU support HVM by using NetBSD's cpuctl  of a NetBSD build.  Both xen and NetBSD may be left compressed.  (If
 command:  using i386, use releasedir/i386/binary/kernel/netbsd-XEN3PAE_DOM0.gz.)
   
     # cpuctl identify 0  In a dom0 kernel, kernfs is mandatory for xend to comunicate with the
     cpu0: Intel Core 2 (Merom) (686-class), id 0x6f6  kernel, so ensure that /kern is in fstab.
     cpu0: features 0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>  
     cpu0: features 0xbfebfbff<PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX>  Because you already installed NetBSD, you have a working boot setup
     cpu0: features 0xbfebfbff<FXSR,SSE,SSE2,SS,HTT,TM,SBF>  with an MBR bootblock, either bootxx_ffsv1 or bootxx_ffsv2 at the
     cpu0: features2 0x4e33d<SSE3,DTES64,MONITOR,DS-CPL,,TM2,SSSE3,CX16,xTPR,PDCM,DCA>  beginning of your root filesystem, /boot present, and likely
     cpu0: features3 0x20100800<SYSCALL/SYSRET,XD,EM64T>  /boot.cfg.  (If not, fix before continuing!)
     cpu0: "Intel(R) Xeon(R) CPU            5130  @ 2.00GHz"  
     cpu0: I-cache 32KB 64B/line 8-way, D-cache 32KB 64B/line 8-way  See boot.cfg(5) for an example.  The basic line is
     cpu0: L2 cache 4MB 64B/line 16-way  
     cpu0: ITLB 128 4KB entries 4-way  "menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=256M"
     cpu0: DTLB 256 4KB entries 4-way, 32 4MB entries 4-way  
     cpu0: Initial APIC ID 0  which specifies that the dom0 should have 256M, leaving the rest to be
     cpu0: Cluster/Package ID 0  allocated for domUs.
     cpu0: Core ID 0  
     cpu0: family 06 model 0f extfamily 00 extmodel 00  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
 Depending on your CPU, the feature you are looking for is called HVM,  kernel, Xen, and the dom0 kernel.
 SVM or VMX.  
   
 Next you need to copy the selected Xen kernel itself. pkgsrc installed  
 them under `/usr/pkg/xen*-kernel/`. The file you're looking for is  
 `xen.gz`. Copy it to your root file system. `xen-debug.gz` is a kernel  
 with more consistency checks and more details printed on the serial  
 console. It is useful for debugging crashing guests if you use a serial  
 console. It is not useful with a VGA console.  
   
 You'll then need a NetBSD/Xen kernel for *domain0* on your root file  
 system. The XEN3PAE\_DOM0 kernel or XEN3\_DOM0 provided as part of the  
 i386 or amd64 binaries is suitable for this, but you may want to  
 customize it. Keep your native kernel around, as it can be useful for  
 recovery. *Note:* the *domain0* kernel must support KERNFS and `/kern`  
 must be mounted because *xend* needs access to `/kern/xen/privcmd`.  
   
 Next you need to get a bootloader to load the `xen.gz` kernel, and the  
 NetBSD *domain0* kernel as a module. This can be `grub` or NetBSD's boot  
 loader. Below is a detailled example for grub, see the boot.cfg(5)  
 manual page for an example using the latter.  
   
 This is also where you'll specify the memory allocated to *domain0*, the  
 console to use, etc ...  
   
 Here is a commented `/grub/menu.lst` file:  
   
     #Grub config file for NetBSD/xen. Copy as /grub/menu.lst and run  
     # grub-install /dev/rwd0d (assuming your boot device is wd0).  
     #  
     # The default entry to load will be the first one  
     default=0  
   
     # boot the default entry after 10s if the user didn't hit keyboard  
     timeout=10  
   
     # Configure serial port to use as console. Ignore if you'll use VGA only  
     serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1  
   
     # Let the user select which console to use (serial or VGA), default  
     # to serial after 10s  
     terminal --timeout=10 serial console  
   
     # An entry for NetBSD/xen, using /netbsd as the domain0 kernel, and serial  
     # console. Domain0 will have 64MB RAM allocated.  
     # Assume NetBSD is installed in the first MBR partition.  
     title Xen 3 / NetBSD (hda0, serial)  
       root(hd0,0)  
       kernel (hd0,a)/xen.gz dom0_mem=65536 com1=115200,8n1  
       module (hd0,a)/netbsd bootdev=wd0a ro console=ttyS0  
   
     # Same as above, but using VGA console  
     # We can use console=tty0 (Linux syntax) or console=pc (NetBSD syntax)  
     title Xen 3 / NetBSD (hda0, vga)  
       root(hd0,0)  
       kernel (hd0,a)/xen.gz dom0_mem=65536  
       module (hd0,a)/netbsd bootdev=wd0a ro console=tty0  
   
     # NetBSD/xen using a backup domain0 kernel (in case you installed a  
     # nonworking kernel as /netbsd  
     title Xen 3 / NetBSD (hda0, backup, serial)  
       root(hd0,0)  
       kernel (hd0,a)/xen.gz dom0_mem=65536 com1=115200,8n1  
       module (hd0,a)/netbsd.backup bootdev=wd0a ro console=ttyS0  
     title Xen 3 / NetBSD (hda0, backup, VGA)  
       root(hd0,0)  
       kernel (hd0,a)/xen.gz dom0_mem=65536  
       module (hd0,a)/netbsd.backup bootdev=wd0a ro console=tty0  
   
     #Load a regular NetBSD/i386 kernel. Can be useful if you end up with a  
     #nonworking /xen.gz  
     title NetBSD 5.1  
       root (hd0,a)  
       kernel --type=netbsd /netbsd-GENERIC  
   
     #Load the NetBSD bootloader, letting it load the NetBSD/i386 kernel.  
     #May be better than the above, as grub can't pass all required infos  
     #to the NetBSD/i386 kernel (e.g. console, root device, ...)  
     title NetBSD chain  
       root        (hd0,0)  
       chainloader +1  
   
     ## end of grub config file.  
             
   
 Install grub with the following command:  
   
     # grub --no-floppy  
   
     grub> root (hd0,a)  
      Filesystem type is ffs, partition type 0xa9  
   
     grub> setup (hd0)  
      Checking if "/boot/grub/stage1" exists... no  
      Checking if "/grub/stage1" exists... yes  
      Checking if "/grub/stage2" exists... yes  
      Checking if "/grub/ffs_stage1_5" exists... yes  
      Running "embed /grub/ffs_stage1_5 (hd0)"...  14 sectors are embedded.  
     succeeded  
      Running "install /grub/stage1 (hd0) (hd0)1+14 p (hd0,0,a)/grub/stage2 /grub/menu.lst"...  
      succeeded  
     Done.  
             
   
 Updating NetBSD in a dom0  Updating NetBSD in a dom0
 -------------------------  -------------------------
Line 503  working vif-bridge is also provided with Line 411  working vif-bridge is also provided with
   
     #!/bin/sh      #!/bin/sh
     #============================================================================      #============================================================================
     # $NetBSD: howto.mdwn,v 1.18 2014/12/24 00:11:15 gdt Exp $      # $NetBSD: howto.mdwn,v 1.19 2014/12/24 00:41:04 gdt Exp $
     #      #
     # /usr/pkg/etc/xen/vif-bridge      # /usr/pkg/etc/xen/vif-bridge
     #      #

Removed from v.1.19  
changed lines
  Added in v.1.20


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