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

version 1.38, 2014/12/24 16:07:32 version 1.39, 2014/12/24 16:13:59
Line 411  improves performance.  The other is that Line 411  improves performance.  The other is that
 failed to work.  TODO: give working/notworking NetBSD versions for  failed to work.  TODO: give working/notworking NetBSD versions for
 sparse vnd.  Note that the use of file/vnd for Xen is not really  sparse vnd.  Note that the use of file/vnd for Xen is not really
 different than creating a file-backed virtual disk for some other  different than creating a file-backed virtual disk for some other
 purpose, except that xentools handles the vnconfig commands.  purpose, except that xentools handles the vnconfig commands.  To
   create an empty 4G virtual disk, simply do
   
           dd if=/dev/zero of=foo-xbd0 bs=1m count=4096
   
 With the lvm style, one creates logical devices.  They are then used  With the lvm style, one creates logical devices.  They are then used
 similarly to vnds.  similarly to vnds.
Line 444  create a new file and vnconfig it (or lv Line 447  create a new file and vnconfig it (or lv
 just like updating physical disks, but without having to be there and  just like updating physical disks, but without having to be there and
 without those pesky connectors.  without those pesky connectors.
   
   domU kernels
   ------------
   
   On a physical computer, the BIOS reads sector 0, and a chain of boot
   loaders finds and loads a kernel.  Normally this comes from the root
   filesystem.  With Xen domUs, the process is totally different.  The
   normal path is for the domU kernel to be a file in the dom0's
   filesystem.  At the request of the dom0, Xen loads that kernel into a
   new domU instance and starts execution.  While domU kernels can be
   anyplace, reasonable places to store domU kernels on the dom0 are in /
   (so they are near the dom0 kernel), in /usr/pkg/etc/xen (near the
   config files), or in /u0/xen (where the vdisks are).
   
   See the VPS section near the end for discussion of alternate ways to
   obtain domU kernels.
   
 Config files  Config files
 ------------  ------------
   
Line 608  working vif-bridge is also provided with Line 627  working vif-bridge is also provided with
   
     #!/bin/sh      #!/bin/sh
     #============================================================================      #============================================================================
     # $NetBSD: howto.mdwn,v 1.37 2014/12/24 16:06:38 gdt Exp $      # $NetBSD: howto.mdwn,v 1.38 2014/12/24 16:07:32 gdt Exp $
     #      #
     # /usr/pkg/etc/xen/vif-bridge      # /usr/pkg/etc/xen/vif-bridge
     #      #

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


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