<?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">
<!--
This file is autogenerated from windows.html.in
Do not edit this file. Changes will be lost.
-->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<link rel="stylesheet" type="text/css" href="main.css" />
<link rel="SHORTCUT ICON" href="32favicon.png" />
<title>libvirt: Windows support</title>
<meta name="description" content="libvirt, virtualization, virtualization API" />
</head>
<body>
<div id="body">
<div id="content">
<h1>Windows support</h1>
<ul><li>
<a href="#installer">Installation packages</a>
</li><li>
<a href="#conntypes">Connection types</a>
</li><li>
<a href="#esx">Connecting to VMware ESX/vSphere</a>
</li><li>
<a href="#tlscerts">TLS Certificates</a>
</li><li>
<a href="#feedback">Feedback</a>
</li><li>
<a href="#compiling">Compiling yourself</a>
<ul><li>
<a href="#msys_setup">MSYS Build script</a>
</li><li>
<a href="#cross-compile">Cross compiling</a>
</li><li>
<a href="#configure">By hand</a>
</li></ul>
</li></ul>
<p>
Libvirt is known to work as a client (not server) on Windows XP
(32-bit), and Windows 7 (64-bit). Other Windows variants likely work
as well but we either haven't tested or received reports for them.
</p>
<h2>
<a name="installer" shape="rect" id="installer">Installation packages</a>
<a class="headerlink" href="#installer" title="Permalink to this headline">¶</a>
</h2>
<p>
Users who need pre-built Windows DLLs of libvirt are advised
to use the <a href="http://virt-manager.org" shape="rect">Virt Viewer</a>
pre-compiled <a href="http://virt-manager.org/download/" shape="rect">Windows MSI packages</a>
</p>
<p>
These installers include the libvirt, gtk-vnc and spice-gtk DLLs
along with any of their pre-requisite supporting DLLs, the virsh
command line tool and the virt-viewer & remote-viewer graphical
tools. The development headers are not currently provided in this
installer, so this cannot be used for compiling new applications
against libvirt.
</p>
<h2>
<a name="conntypes" shape="rect" id="conntypes">Connection types</a>
<a class="headerlink" href="#conntypes" title="Permalink to this headline">¶</a>
</h2>
<p>
These connection types are known to work:
</p>
<ul><li>QEMU with TLS (qemu+tls://)</li><li>QEMU with direct TCP (qemu+tcp://)</li><li>VMware ESX (esx://)</li><li>VMware VPX (vpx://)</li></ul>
<p>
These connection types are known not to work:
</p>
<ul><li>QEMU with SSH (qemu+ssh://)</li></ul>
<p>
All other connection types may or may not work, and haven't been
tested.
</p>
<p>
Please let us know either the results (either way) if you do.
</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>
<b>WARNING - The qemu+tcp:// connection type passes all traffic
without encryption. This is a security hazard, and should <i>not</i>
be used in security sensitive environments.</b>
</p>
<h2>
<a name="esx" shape="rect" id="esx">Connecting to VMware ESX/vSphere</a>
<a class="headerlink" href="#esx" title="Permalink to this headline">¶</a>
</h2>
<p>
Details on the capabilities, certificates, and connection string
syntax used for connecting to VMware ESX and vSphere can be found
online here:<br />
</p>
<a href="http://libvirt.org/drvesx.html" shape="rect">http://libvirt.org/drvesx.html</a>
<h2>
<a name="tlscerts" shape="rect" id="tlscerts">TLS Certificates</a>
<a class="headerlink" href="#tlscerts" title="Permalink to this headline">¶</a>
</h2>
<p>
TLS certificates need to have been created and placed in the correct
locations, before you will be able to connect to QEMU servers over
TLS.
</p>
<p>
Information on generating TLS certificates can be found here:
</p>
<a href="http://wiki.libvirt.org/page/TLSSetup" shape="rect">http://wiki.libvirt.org/page/TLSSetup</a>
<p>
These instructions are for *nix, and have not yet been adapted for
Windows. You'll need to figure out the Windows equivalents until
that's done (sorry). If you can help us out with this, that would be
really welcome.
</p>
<p>
The locations of the TLS certificates and key file on Windows are hard
coded, rather than being configurable.
</p>
<p>
The Certificate Authority (CA) certificate file must be placed in:
</p>
<ul><li>%APPDATA%\libvirt\pki\CA\cacert.pem</li></ul>
<p>
The Client certificate file must be placed in:
</p>
<ul><li>%APPDATA%\libvirt\pki\libvirt\clientcert.pem</li></ul>
<p>
The Client key file must be placed in:
</p>
<ul><li>%APPDATA%\libvirt\pki\libvirt\private\clientkey.pem</li></ul>
<p>
On an example Windows 7 x64 system here, this resolves to these paths:
</p>
<ul><li>C:\Users\someuser\AppData\Roaming\libvirt\pki\CA\cacert.pem</li><li>C:\Users\someuser\AppData\Roaming\libvirt\pki\libvirt\clientcert.pem</li><li>C:\Users\someuser\AppData\Roaming\libvirt\pki\libvirt\private\clientkey.pem</li></ul>
<h2>
<a name="feedback" shape="rect" id="feedback">Feedback</a>
<a class="headerlink" href="#feedback" title="Permalink to this headline">¶</a>
</h2>
<p>
Feedback and suggestions on changes to make and what else to include
<a href="contact.html" shape="rect">are desired</a>.
</p>
<h2>
<a name="compiling" shape="rect" id="compiling">Compiling yourself</a>
<a class="headerlink" href="#compiling" title="Permalink to this headline">¶</a>
</h2>
<p>
Libvirt can be compiled on Windows using the free
<a href="http://www.mingw.org/" shape="rect">MinGW compiler</a>.
</p>
<h3>
<a name="msys_setup" shape="rect" id="msys_setup">MSYS Build script</a>
<a class="headerlink" href="#msys_setup" title="Permalink to this headline">¶</a>
</h3>
<p>
The easiest way is to use the <b>msys_setup</b> script, developed by
Matthias Bolte. This is actively developed and kept current with
libvirt releases:
</p>
<a href="https://github.com/photron/msys_setup" shape="rect">https://github.com/photron/msys_setup</a>
<h3>
<a name="cross-compile" shape="rect" id="cross-compile">Cross compiling</a>
<a class="headerlink" href="#cross-compile" title="Permalink to this headline">¶</a>
</h3>
<p>
You can also cross-compile to a Windows target from a Fedora machine
using the packages available
<a href="http://hg.et.redhat.com/misc/fedora-mingw--devel/" shape="rect">from the Fedora MinGW project</a>
(which includes a working libvirt specfile).
</p>
<h3>
<a name="configure" shape="rect" id="configure">By hand</a>
<a class="headerlink" href="#configure" title="Permalink to this headline">¶</a>
</h3>
<p>
Use these options when following the instructions on the
<a href="compiling.html" shape="rect">Compiling</a> page.
</p>
<pre xml:space="preserve">
./configure \
--without-sasl \
--without-avahi \
--without-polkit \
--without-python \
--without-xen \
--without-qemu \
--without-lxc \
--without-openvz \
--without-libvirtd
</pre>
</div>
</div>
<div id="nav">
<div id="home">
<a href="index.html">Home</a>
</div>
<div id="jumplinks">
<ul><li>
<a href="downloads.html">Download</a>
</li><li>
<a href="contribute.html">Contribute</a>
</li><li>
<a href="docs.html">Learn</a>
</li></ul>
</div>
<div id="search">
<form action="search.php" enctype="application/x-www-form-urlencoded" method="get"><div>
<input name="query" type="text" size="12" value="" />
<input name="submit" type="submit" value="Go" />
</div></form>
</div>
</div>
<div id="footer">
<div id="contact">
<h3>Contact</h3>
<ul><li>
<a href="contact.html#email">email</a>
</li><li>
<a href="contact.html#irc">irc</a>
</li></ul>
</div>
<div id="community">
<h3>Community</h3>
<ul><li>
<a href="https://twitter.com/hashtag/libvirt">twitter</a>
</li><li>
<a href="https://plus.google.com/communities/109522598353007505282">google+</a>
</li><li>
<a href="http://stackoverflow.com/questions/tagged/libvirt">stackoverflow</a>
</li><li>
<a href="http://serverfault.com/questions/tagged/libvirt">serverfault</a>
</li></ul>
</div>
<div id="conduct">
Participants in the libvirt project agree to abide by <a href="governance.html#codeofconduct">the project code of conduct</a></div>
<br class="clear" />
</div>
</body>
</html>
