mirror of
https://github.com/libvirt/libvirt.git
synced 2025-02-25 18:55:26 -06:00
docs: updated windows page for new 0.8.7 installer
This commit is contained in:
@@ -18,7 +18,7 @@
|
|||||||
version is available here:
|
version is available here:
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<a href="http://libvirt.org/sources/win32_experimental/Libvirt-0.8.6-2.exe">http://libvirt.org/sources/win32_experimental/Libvirt-0.8.6-2.exe</a>
|
<a href="http://libvirt.org/sources/win32_experimental/Libvirt-0.8.7-2.exe">http://libvirt.org/sources/win32_experimental/Libvirt-0.8.7-2.exe</a>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<b>It is not production ready.</b>
|
<b>It is not production ready.</b>
|
||||||
@@ -77,15 +77,6 @@
|
|||||||
<br /><br />
|
<br /><br />
|
||||||
</li>
|
</li>
|
||||||
|
|
||||||
<li>
|
|
||||||
Libvirt dll files should be added to path
|
|
||||||
<br /><br />
|
|
||||||
At the moment, anything that needs to use the libvirt dll files
|
|
||||||
(i.e. the C# bindings) won't automatically find them. This can be
|
|
||||||
worked around by copying the dll files into the same directory as
|
|
||||||
whatever needs them, but is probably not an optimal approach.
|
|
||||||
There might be a better way and needs to be investigated.
|
|
||||||
</li>
|
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<h2><a name="conntypes">Connection types</h2>
|
<h2><a name="conntypes">Connection types</h2>
|
||||||
@@ -118,6 +109,12 @@
|
|||||||
Please let us know either the results (either way) if you do.
|
Please let us know either the results (either way) if you do.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<b>Special note</b> - Support for VirtualBox *on windows* was added in
|
||||||
|
libvirt 0.8.7, so reports on success and failure if you're using that
|
||||||
|
would be really helpful and appreciated.
|
||||||
|
</p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<b>WARNING - The qemu+tcp:// connection type passes all traffic
|
<b>WARNING - The qemu+tcp:// connection type passes all traffic
|
||||||
without encryption. This is a security hazard, and should <i>not</i>
|
without encryption. This is a security hazard, and should <i>not</i>
|
||||||
@@ -127,8 +124,9 @@
|
|||||||
<h2><a name="esx">Connecting to VMware ESX/vSphere</h2>
|
<h2><a name="esx">Connecting to VMware ESX/vSphere</h2>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
Details on the capabilities and connection string syntax used for
|
Details on the capabilities, certificates, and connection string
|
||||||
connecting to VMware ESX and vSphere can be found online here:<br />
|
syntax used for connecting to VMware ESX and vSphere can be found
|
||||||
|
online here:<br />
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<a href="http://libvirt.org/drvesx.html">http://libvirt.org/drvesx.html</a>
|
<a href="http://libvirt.org/drvesx.html">http://libvirt.org/drvesx.html</a>
|
||||||
@@ -136,8 +134,9 @@
|
|||||||
<h2><a name="tlscerts">TLS Certificates</h2>
|
<h2><a name="tlscerts">TLS Certificates</h2>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
TLS certificates are needed prior to connecting to either QEMU
|
TLS certificates need to have been created and placed in the correct
|
||||||
instances with TLS, or connecting to VMware ESX/vSphere.
|
locations, before you will be able to connect to QEMU servers over
|
||||||
|
TLS.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
@@ -154,8 +153,8 @@
|
|||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
The locations of the TLS certificates and key file are hard coded,
|
The locations of the TLS certificates and key file on Windows are hard
|
||||||
rather than being configurable.
|
coded, rather than being configurable.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|||||||
Reference in New Issue
Block a user