Changes between Version 4 and Version 5 of Xen Zfs Handler Customization

Show
Ignore:
Timestamp:
12/04/08 21:56:10 (11 years ago)
Author:
aydan (IP: 69.134.122.47)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Xen Zfs Handler Customization

    v4 v5  
    1 Before you can use the Xen Zfs handler, it must be customized for your own installation. In particular, the handler must know which disk and kernel images to use when instantiating a virtual machine. The current version supports multiple disk images but requires that all of them share the same kernel image.  
     1Before you can use the Xen Zfs handler, it must be customized for your installation. In particular, the handler must know which disk and kernel images to use when instantiating a virtual machine. The current version supports multiple disk images but requires that all of them share the same kernel image.  
    22 
    33The kernel and disk images are controlled by a property file inside the xen zfs handler. You will need to check out the handler from the repository and make the following changes. 
     
    1414The last line creates an empty file called user.properties. This file overrides properties contained in build.properties (in the same directory). In particular, the properties that you need to override are: 
    1515 
    16  * unit.os.kernel - path to the kernel image to use.  The path is relative to the '''software'' sub-directory within the installation directory of the Xen driver on each Xen VMM. You can also add an absolute path, but it should refer to a valid location on each Xen VMM. See this page for instructions how to deploy your kernel image to each Xen VMM. 
     16 * unit.os.kernel - path to the kernel image to use.  The path is relative to the '''software''' sub-directory within the installation directory of the Xen driver on each Xen VMM. You can also add an absolute path, but it should refer to a valid location on each Xen VMM. See this page for instructions how to deploy your kernel image to each Xen VMM. 
    1717 
    1818 * image.guid - guid of the default vm image. See this page for information about preparing an image to be used with the system