diff --git a/docs/drivers.html.in b/docs/drivers.html.in index 24387d03889236781803e8456b424dedfb813780..307d286e13d89a731cd05e8796c7ef72ed167ef8 100644 --- a/docs/drivers.html.in +++ b/docs/drivers.html.in @@ -29,6 +29,7 @@
  • VMware Workstation/Player
  • Xen
  • Microsoft Hyper-V
    • +
  • IBM PowerVM (phyp)

    • Storage drivers

    diff --git a/docs/drvphyp.html.in b/docs/drvphyp.html.in new file mode 100644 index 0000000000000000000000000000000000000000..0bd20dd489ff75f260915c9318f4840d7c7d163c --- /dev/null +++ b/docs/drvphyp.html.in @@ -0,0 +1,48 @@ + +

    IBM PowerVM hypervisor driver (phyp)

    + +

    + The IBM PowerVM driver can manage both HMC and IVM PowerVM + guests. VIOS connections are tunneled through HMC. +

    + + +

    Project Links

    + + + +

    Connections to the PowerVM driver

    +

    + Some example remote connection URIs for the driver are: +

    +
    +phyp://user@hmc/system (HMC connection)
+phyp://user@ivm/system (IVM connection)
+
    +

    + Note: In contrast to other drivers, the + PowerVM (or phyp) driver is a client-side-only driver, + internally using ssh to connect to the specified hmc or ivm + server. Therefore, the remote transport + mechanism provided by the remote driver and libvirtd will + not work, and you cannot use URIs like + phyp+ssh://example.com. +

    + + +

    URI Format

    +

    + URIs have this general form ([...] marks an + optional part, {...|...} marks a mandatory choice). +

    +
    +phyp://[username@]{hmc|ivm}/managed_system
+
    +

    + +