libvirt/docs/drvvmware.html.in

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
    <body>
        <h1>VMware Workstation / Player / Fusion hypervisors driver</h1>
        <p>
        The libvirt VMware driver should be able to manage any Workstation,
        Player, Fusion version supported by the VMware VIX API. See the
        compatibility list
        <a href="https://www.vmware.com/support/developer/vix-api/vix110_reference/">here</a>.
    </p>
    <p>
    This driver uses the "vmrun" utility which is distributed with the VMware VIX API.
    You can download the VIX API
    from <a href="https://www.vmware.com/support/developer/vix-api/">here</a>.
    </p>

    <h2><a id="project">Project Links</a></h2>

    <ul>
      <li>
        The <a href="https://www.vmware.com/">VMware Workstation and
        Player</a> hypervisors
      </li>
      <li>
        The <a href="https://www.vmware.com/fusion">VMware Fusion</a>
        hypervisor
      </li>
    </ul>

    <h2>Connections to VMware driver</h2>

    <p>
    The libvirt VMware driver provides per-user drivers (the "session" instance).
    Three uris are available:
    </p>
    <ul>
      <li>"vmwareplayer" for VMware Player</li>
      <li>"vmwarews" for VMware Workstation</li>
      <li>"vmwarefusion" for VMware Fusion</li>
    </ul>
    <p>
    Some example connection URIs for the driver are:
    </p>

<pre>
vmwareplayer:///session                  (local access to VMware Player per-user instance)
vmwarews:///session                      (local access to VMware Workstation per-user instance)
vmwarefusion:///session                      (local access to VMware Fusion per-user instance)
vmwarews+tcp://user@example.com/session  (remote access to VMware Workstation, SASl/Kerberos)
vmwarews+ssh://user@example.com/session  (remote access to VMware Workstation, SSH tunnelled)
</pre>

    <h2><a id="xmlconfig">Example domain XML config</a></h2>

<pre>
&lt;domain type='vmware'&gt;
  &lt;name&gt;vmware&lt;/name&gt;
  &lt;uuid&gt;bea92244-8885-4562-828b-3b086731c5b1&lt;/uuid&gt;

  &lt;os&gt;
    &lt;type&gt;hvm&lt;/type&gt;
  &lt;/os&gt;

  &lt;memory&gt;524288&lt;/memory&gt;
  &lt;vcpu&gt;1&lt;/vcpu&gt;

  &lt;features&gt;
    &lt;pae/&gt;
    &lt;acpi/&gt;
  &lt;/features&gt;

  &lt;devices&gt;
    &lt;disk type='file' device='disk'&gt;
      &lt;source file='/home/user/tmp/disk.vmdk'/&gt;
      &lt;target bus='ide' dev='hda'/&gt;
    &lt;/disk&gt;

    &lt;interface type='bridge'&gt;
      &lt;target dev='/dev/vmnet1'/&gt;
      &lt;source bridge=''/&gt;
      &lt;mac address='00:16:3e:5d:c7:9e'/&gt;
    &lt;/interface&gt;
  &lt;/devices&gt;
&lt;/domain&gt;
</pre>

    </body>
</html>
Fix multiple formatting problems in HTML docs The rule generating the HTML docs passing the --html flag to xsltproc. This makes it use the legacy HTML parser, which either ignores or tries to fix all sorts of broken XML tags. There's no reason why we should be writing broken XML in the first place, so removing --html and adding the XHTML doctype to all files forces us to create good XML. This adds the XHTML doc type and fixes many, many XML tag problems it exposes. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2013-05-03 18:25:37 +04:00			`<?xml version="1.0" encoding="UTF-8"?>`
docs: switch to using HTML5 doctype declaration The HTML5 doctype is simply <!DOCTYPE html> no DTD is present because HTML5 is no longer defined as an extension of SGML. XSL has no way to natively output a doctype without a public or system identifier, so we have to use an <xsl:text> hack instead. See also https://dev.w3.org/html5/html-author/#doctype-declaration Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2017-07-26 20:01:25 +03:00			`<!DOCTYPE html>`
Fix multiple formatting problems in HTML docs The rule generating the HTML docs passing the --html flag to xsltproc. This makes it use the legacy HTML parser, which either ignores or tries to fix all sorts of broken XML tags. There's no reason why we should be writing broken XML in the first place, so removing --html and adding the XHTML doctype to all files forces us to create good XML. This adds the XHTML doc type and fixes many, many XML tag problems it exposes. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2013-05-03 18:25:37 +04:00			`<html xmlns="http://www.w3.org/1999/xhtml">`
Add info about VMware driver to the libvirt website 2010-12-23 11:35:51 +03:00			`<body>`
VMware: Initial VMware Fusion support Add support for VMware Fusion in the existing VMware driver. Connect via the URI vmwarefusion:///session 2013-09-24 20:24:31 +04:00			`<h1>VMware Workstation / Player / Fusion hypervisors driver</h1>`
Add info about VMware driver to the libvirt website 2010-12-23 11:35:51 +03:00			`<p>`
VMware: Initial VMware Fusion support Add support for VMware Fusion in the existing VMware driver. Connect via the URI vmwarefusion:///session 2013-09-24 20:24:31 +04:00			`The libvirt VMware driver should be able to manage any Workstation,`
			`Player, Fusion version supported by the VMware VIX API. See the`
			`compatibility list`
Prefer https: everywhere where possible Use https: links for websites that support them. The URIs which are used as namespace identifiers are left alone. Signed-off-by: Ján Tomko <jtomko@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Neal Gompa <ngompa13@gmail.com> 2020-08-26 01:44:00 +03:00			`<a href="https://www.vmware.com/support/developer/vix-api/vix110_reference/">here</a>.`
Add info about VMware driver to the libvirt website 2010-12-23 11:35:51 +03:00			`</p>`
			`<p>`
			`This driver uses the "vmrun" utility which is distributed with the VMware VIX API.`
docs: correct invalid xml * docs/internals.html.in: Fix xml errors. * docs/formatstorageencryption.html.in: Likewise. * docs/drvesx.html.in: Likewise. * docs/archnetwork.html.in: Likewise. * docs/logging.html.in: Likewise. * docs/drvvmware.html.in: Likewise. * docs/api.html.in: Likewise. * docs/formatnwfilter.html.in: Likewise. * docs/formatdomain.html.in: Likewise. * docs/windows.html.in: Likewise. 2011-04-02 02:02:10 +04:00			`You can download the VIX API`
Prefer https: everywhere where possible Use https: links for websites that support them. The URIs which are used as namespace identifiers are left alone. Signed-off-by: Ján Tomko <jtomko@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Neal Gompa <ngompa13@gmail.com> 2020-08-26 01:44:00 +03:00			`from <a href="https://www.vmware.com/support/developer/vix-api/">here</a>.`
docs: correct invalid xml * docs/internals.html.in: Fix xml errors. * docs/formatstorageencryption.html.in: Likewise. * docs/drvesx.html.in: Likewise. * docs/archnetwork.html.in: Likewise. * docs/logging.html.in: Likewise. * docs/drvvmware.html.in: Likewise. * docs/api.html.in: Likewise. * docs/formatnwfilter.html.in: Likewise. * docs/formatdomain.html.in: Likewise. * docs/windows.html.in: Likewise. 2011-04-02 02:02:10 +04:00			`</p>`
Add info about VMware driver to the libvirt website 2010-12-23 11:35:51 +03:00
docs: switch to using 'id' attribute instead of 'name' for links The 'name' attribute on <a...> elements is deprecated in favour of the 'id' attribute which is allowed on any element. HTML5 drops 'name' support entirely. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2017-07-26 17:52:42 +03:00			`<h2><a id="project">Project Links</a></h2>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-15 22:33:17 +04:00
			`<ul>`
			`<li>`
Prefer https: everywhere where possible Use https: links for websites that support them. The URIs which are used as namespace identifiers are left alone. Signed-off-by: Ján Tomko <jtomko@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Neal Gompa <ngompa13@gmail.com> 2020-08-26 01:44:00 +03:00			`The <a href="https://www.vmware.com/">VMware Workstation and`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-15 22:33:17 +04:00			`Player</a> hypervisors`
			`</li>`
VMware: Initial VMware Fusion support Add support for VMware Fusion in the existing VMware driver. Connect via the URI vmwarefusion:///session 2013-09-24 20:24:31 +04:00			`<li>`
Prefer https: everywhere where possible Use https: links for websites that support them. The URIs which are used as namespace identifiers are left alone. Signed-off-by: Ján Tomko <jtomko@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Neal Gompa <ngompa13@gmail.com> 2020-08-26 01:44:00 +03:00			`The <a href="https://www.vmware.com/fusion">VMware Fusion</a>`
VMware: Initial VMware Fusion support Add support for VMware Fusion in the existing VMware driver. Connect via the URI vmwarefusion:///session 2013-09-24 20:24:31 +04:00			`hypervisor`
			`</li>`
website: Point main page links to libvirt driver pages The "libvirt supports:" section on the main page of libvirt.org contains a list of hypervisors with links that point to the sites of the underlying virt technologies. The entry for KVM points to http://www.linux-kvm.org/, for example. People coming to libvirt.org for the first time are likely to know about those sites, and they're probably interested in how libvirt manages those technologies. This patch points those links to the libvirt driver pages instead. It also consolidates KVM and QEMU as there is only one libvirt driver page for them. Finally, it adds a line about networking support. v2: incorporate Eric's feedback adding project links to driver pages. website: Add project links to KVM/QEMU driver page website: Add project links to Xen driver page website: Add project links to LXC driver page website: Add project links to OpenVZ driver page website: Add project links to UML driver page website: Add project links to Virtualbox driver page website: Add project links to ESX driver page website: Add project links to VMware driver page 2011-07-15 22:33:17 +04:00			`</ul>`

Add info about VMware driver to the libvirt website 2010-12-23 11:35:51 +03:00			`<h2>Connections to VMware driver</h2>`

			`<p>`
			`The libvirt VMware driver provides per-user drivers (the "session" instance).`
VMware: Initial VMware Fusion support Add support for VMware Fusion in the existing VMware driver. Connect via the URI vmwarefusion:///session 2013-09-24 20:24:31 +04:00			`Three uris are available:`
docs: Make VMware Workstation / Player page appear in the menu By adding it to sitemap.html.in. Also <ul> can't be nested in <p>. 2010-12-23 18:56:11 +03:00			`</p>`
Add info about VMware driver to the libvirt website 2010-12-23 11:35:51 +03:00			`<ul>`
			`<li>"vmwareplayer" for VMware Player</li>`
			`<li>"vmwarews" for VMware Workstation</li>`
VMware: Initial VMware Fusion support Add support for VMware Fusion in the existing VMware driver. Connect via the URI vmwarefusion:///session 2013-09-24 20:24:31 +04:00			`<li>"vmwarefusion" for VMware Fusion</li>`
Add info about VMware driver to the libvirt website 2010-12-23 11:35:51 +03:00			`</ul>`
docs: Make VMware Workstation / Player page appear in the menu By adding it to sitemap.html.in. Also <ul> can't be nested in <p>. 2010-12-23 18:56:11 +03:00			`<p>`
Add info about VMware driver to the libvirt website 2010-12-23 11:35:51 +03:00			`Some example connection URIs for the driver are:`
			`</p>`

			`<pre>`
			`vmwareplayer:///session (local access to VMware Player per-user instance)`
			`vmwarews:///session (local access to VMware Workstation per-user instance)`
VMware: Initial VMware Fusion support Add support for VMware Fusion in the existing VMware driver. Connect via the URI vmwarefusion:///session 2013-09-24 20:24:31 +04:00			`vmwarefusion:///session (local access to VMware Fusion per-user instance)`
Add info about VMware driver to the libvirt website 2010-12-23 11:35:51 +03:00			`vmwarews+tcp://user@example.com/session (remote access to VMware Workstation, SASl/Kerberos)`
			`vmwarews+ssh://user@example.com/session (remote access to VMware Workstation, SSH tunnelled)`
			`</pre>`

docs: switch to using 'id' attribute instead of 'name' for links The 'name' attribute on <a...> elements is deprecated in favour of the 'id' attribute which is allowed on any element. HTML5 drops 'name' support entirely. Signed-off-by: Daniel P. Berrange <berrange@redhat.com> 2017-07-26 17:52:42 +03:00			`<h2><a id="xmlconfig">Example domain XML config</a></h2>`
Add info about VMware driver to the libvirt website 2010-12-23 11:35:51 +03:00
			`<pre>`
			`<domain type='vmware'>`
			`<name>vmware</name>`
			`<uuid>bea92244-8885-4562-828b-3b086731c5b1</uuid>`

			`<os>`
			`<type>hvm</type>`
			`</os>`

			`<memory>524288</memory>`
			`<vcpu>1</vcpu>`

			`<features>`
			`<pae/>`
			`<acpi/>`
			`</features>`

			`<devices>`
			`<disk type='file' device='disk'>`
			`<source file='/home/user/tmp/disk.vmdk'/>`
			`<target bus='ide' dev='hda'/>`
			`</disk>`

			`<interface type='bridge'>`
			`<target dev='/dev/vmnet1'/>`
			`<source bridge=''/>`
			`<mac address='00:16:3e:5d:c7:9e'/>`
			`</interface>`
			`</devices>`
			`</domain>`
			`</pre>`

			`</body>`
			`</html>`