2013-05-03 18:25:37 +04:00
<?xml version="1.0" encoding="UTF-8"?>
2017-07-26 20:01:25 +03:00
<!DOCTYPE html>
2013-05-03 18:25:37 +04:00
< html xmlns = "http://www.w3.org/1999/xhtml" >
< body >
2012-09-28 02:19:37 +04:00
< h1 > IBM PowerVM hypervisor driver (phyp)< / h1 >
< ul id = "toc" > < / ul >
< p >
The IBM PowerVM driver can manage both HMC and IVM PowerVM
guests. VIOS connections are tunneled through HMC.
< / p >
2017-07-26 17:52:42 +03:00
< h2 > < a id = "project" > Project Links< / a > < / h2 >
2012-09-28 02:19:37 +04:00
< ul >
< li >
The < a href = "http://www-03.ibm.com/systems/power/software/virtualization/index.html" > IBM
PowerVM< / a > hypervisor
< / li >
< / ul >
2017-07-26 17:52:42 +03:00
< h2 > < a id = "uri" > Connections to the PowerVM driver< / a > < / h2 >
2012-09-28 02:19:37 +04:00
< p >
Some example remote connection URIs for the driver are:
< / p >
< pre >
phyp://user@hmc/system (HMC connection)
phyp://user@ivm/system (IVM connection)
< / pre >
< p >
< strong > Note< / strong > : 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 < a href = "remote.html" > remote transport
mechanism< / a > provided by the remote driver and libvirtd will
not work, and you cannot use URIs like
< code > phyp+ssh://example.com< / code > .
< / p >
2017-07-26 17:52:42 +03:00
< h3 > < a id = "uriformat" > URI Format< / a > < / h3 >
2012-09-28 02:19:37 +04:00
< p >
URIs have this general form (< code > [...]< / code > marks an
optional part, < code > {...|...}< / code > marks a mandatory choice).
< / p >
< pre >
phyp://[username@]{hmc|ivm}/managed_system
< / pre >
< / body > < / html >
