docs/drvphyp.html.in

   1 <?xml version="1.0" encoding="UTF-8"?>
   2 <!DOCTYPE html>
   3 <html xmlns="http://www.w3.org/1999/xhtml">
   4   <body>
   5     <h1>IBM PowerVM hypervisor driver (phyp)</h1>
   6     <ul id="toc"></ul>
   7     <p>
   8         The IBM PowerVM driver can manage both HMC and IVM PowerVM
   9         guests.  VIOS connections are tunneled through HMC.
  10     </p>
  11
  12
  13     <h2><a id="project">Project Links</a></h2>
  14     <ul>
  15       <li>
  16         The <a href="http://www-03.ibm.com/systems/power/software/virtualization/index.html">IBM
  17         PowerVM</a> hypervisor
  18       </li>
  19     </ul>
  20
  21
  22     <h2><a id="uri">Connections to the PowerVM driver</a></h2>
  23     <p>
  24         Some example remote connection URIs for the driver are:
  25     </p>
  26 <pre>
  27 phyp://user@hmc/system (HMC connection)
  28 phyp://user@ivm/system (IVM connection)
  29 </pre>
  30     <p>
  31         <strong>Note</strong>: In contrast to other drivers, the
  32         PowerVM (or phyp) driver is a client-side-only driver,
  33         internally using ssh to connect to the specified hmc or ivm
  34         server. Therefore, the <a href="remote.html">remote transport
  35         mechanism</a> provided by the remote driver and libvirtd will
  36         not work, and you cannot use URIs like
  37         <code>phyp+ssh://example.com</code>.
  38     </p>
  39
  40
  41     <h3><a id="uriformat">URI Format</a></h3>
  42     <p>
  43         URIs have this general form (<code>[...]</code> marks an
  44         optional part, <code>{...|...}</code> marks a mandatory choice).
  45     </p>
  46 <pre>
  47 phyp://[username@]{hmc|ivm}/managed_system
  48 </pre>
  49
  50 </body></html>