2013-05-03 22:25:37 +08:00
|
|
|
<?xml version="1.0" encoding="UTF-8"?>
|
|
|
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
|
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
|
|
|
<body>
|
2012-09-28 06:19:37 +08: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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<h2><a name="project">Project Links</a></h2>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>
|
|
|
|
|
The <a href="http://www-03.ibm.com/systems/power/software/virtualization/index.html">IBM
|
|
|
|
|
PowerVM</a> hypervisor
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<h2><a name="uri">Connections to the PowerVM driver</a></h2>
|
|
|
|
|
<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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<h3><a name="uriformat">URI Format</a></h3>
|
|
|
|
|
<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>
|
