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

version 1.20, 2014/12/24 01:06:43 version 1.23, 2014/12/24 01:34:47
Line 31  Generally any amd64 machine will work wi Line 31  Generally any amd64 machine will work wi
 guests, the VT or VMX cpu feature (Intel) or SVM/HVM/VT (amd64) is  guests, the VT or VMX cpu feature (Intel) or SVM/HVM/VT (amd64) is
 needed; "cpuctl identify 0" will show this.  TODO: Clean up and check  needed; "cpuctl identify 0" will show this.  TODO: Clean up and check
 the above features.  TODO: Explain if i386 (non-amd64) machines can  the above features.  TODO: Explain if i386 (non-amd64) machines can
 still be used - I think that witthe requirement to use PAE kernels is  still be used --- I think that the requirement to use PAE kernels is
 about the hypervisor being amd64 only.  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.
Line 183  However, the partitioning approach is ve Line 183  However, the partitioning approach is ve
   
 If you want to use RAIDframe for the dom0, there are no special issues  If you want to use RAIDframe for the dom0, there are no special issues
 for Xen.  Typically one provides RAID storage for the dom0, and the  for Xen.  Typically one provides RAID storage for the dom0, and the
 domU systems are unaware of RAID.  domU systems are unaware of RAID.  The 2nd-stage loader bootxx_* skips
   over a RAID1 header to find /boot from a filesystem within a RAID
   partition; this is no different when booting Xen.
   
 There are 4 styles of providing backing storage for the virtual disks  There are 4 styles of providing backing storage for the virtual disks
 used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN,  used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN,
Line 246  As with non-Xen systems, you should have Line 248  As with non-Xen systems, you should have
 kernel that works without Xen) and fallback versions of the non-Xen  kernel that works without Xen) and fallback versions of the non-Xen
 kernel, Xen, and the dom0 kernel.  kernel, Xen, and the dom0 kernel.
   
   Configuring Xen
   ---------------
   
   Now, you have a system that will boot Xen and the dom0 kernel, and
   just run the dom0 kernel.  There will be no domUs, and none can be
   started because you still have to configure the dom0 tools.
   
   For 3.3 (and probably 3.1), add to rc.conf (but note that you should
   have installed 4.2):
     xend=YES
     xenbackendd=YES
   
   For 4.1 and 4.2, add to rc.conf:
     xend=YES
     xencommons=YES
   
 Updating NetBSD in a dom0  Updating NetBSD in a dom0
 -------------------------  -------------------------
   
Line 257  and adjusts /etc. Line 275  and adjusts /etc.
 Note that one must update both the non-Xen kernel typically used for  Note that one must update both the non-Xen kernel typically used for
 rescue purposes and the DOM0 kernel used with Xen.  rescue purposes and the DOM0 kernel used with Xen.
   
   To convert from grub to /boot, install an mbr bootblock with fdisk,
   bootxx_ with installboot, /boot and /boot.cfg.  This really should be
   no different than completely reinstalling boot blocks on a non-Xen
   system.
   
 Updating Xen versions  Updating Xen versions
 ---------------------  ---------------------
   
 TODO: write  Updating Xen is conceptually not difficult, but can run into all the
   issues found when installing Xen.  Assuming migration from 4.1 to 4.2,
   remove the xenkernel41 and xentools41 packages and install the
   xenkernel42 and xentools42 packages.  Copy the 4.2 xen.gz to /.
   
   Ensure that the contents of /etc/rc.d/xen* are correct.  Enable the
   correct set of daemons.  Ensure that the domU config files are valid
   for the new version.
   
 Creating unprivileged domains (domU)  Creating unprivileged domains (domU)
 ====================================  ====================================
Line 411  working vif-bridge is also provided with Line 441  working vif-bridge is also provided with
   
     #!/bin/sh      #!/bin/sh
     #============================================================================      #============================================================================
     # $NetBSD: howto.mdwn,v 1.19 2014/12/24 00:41:04 gdt Exp $      # $NetBSD: howto.mdwn,v 1.22 2014/12/24 01:27:36 gdt Exp $
     #      #
     # /usr/pkg/etc/xen/vif-bridge      # /usr/pkg/etc/xen/vif-bridge
     #      #

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


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