diff --git a/docs/drivers.html.in b/docs/drivers.html.in index 042887017c..75038fc17d 100644 --- a/docs/drivers.html.in +++ b/docs/drivers.html.in @@ -28,6 +28,7 @@
  • VMware ESX
  • VMware Workstation/Player
  • Xen
  • +
  • Microsoft Hyper-V
  • Storage drivers

    diff --git a/docs/drvhyperv.html.in b/docs/drvhyperv.html.in new file mode 100644 index 0000000000..7f0accd3e1 --- /dev/null +++ b/docs/drvhyperv.html.in @@ -0,0 +1,112 @@ + +

    Microsoft Hyper-V hypervisor driver

    + +

    + The libvirt Microsoft Hyper-V driver can manage Hyper-V 2008 R2. +

    + + +

    Project Links

    + + + +

    Connections to the Microsoft Hyper-V driver

    +

    + Some example remote connection URIs for the driver are: +

    +
    +hyperv://example-hyperv.com                  (over HTTPS)
    +hyperv://example-hyperv.com/?transport=http  (over HTTP)
    +
    +

    + Note: In contrast to other drivers, the Hyper-V driver + is a client-side-only driver. It connects to the Hyper-V server using + WS-Management over HTTP(S). Therefore, the + remote transport mechanism provided by the + remote driver and libvirtd will not work, and you cannot use URIs like + hyperv+ssh://example.com. +

    + + +

    URI Format

    +

    + URIs have this general form ([...] marks an optional part). +

    +
    +hyperv://[username@]hostname[:port]/[?extraparameters]
    +
    +

    + The default HTTPS ports is 5986. If the port parameter is given, it + overrides the default port. +

    + + +

    Extra parameters

    +

    + Extra parameters can be added to a URI as part of the query string + (the part following ?). A single parameter is formed by a + name=value pair. Multiple parameters are separated by + &. +

    +
    +?transport=http
    +
    +

    + The driver understands the extra parameters shown below. +

    + + + + + + + + + + + +
    NameValuesMeaning
    + transport + + http or https + + Overrides the default HTTPS transport. The default HTTP port + is 5985. +
    + + +

    Authentication

    +

    + In order to perform any useful operation the driver needs to log into + the Hyper-V server. Therefore, only virConnectOpenAuth can + be used to connect to an Hyper-V server, virConnectOpen and + virConnectOpenReadOnly don't work. + To log into an Hyper-V server the driver will request credentials using + the callback passed to the virConnectOpenAuth function. + The driver passes the hostname as challenge parameter to the callback. +

    +

    + Note: Currently only Basic authentication + is supported by libvirt. This method is disabled by default on the + Hyper-V server and can be enabled via the WinRM commandline tool. +

    +
    +winrm set winrm/config/service/auth @{Basic="true"}
    +
    +

    + To allow Basic authentication with HTTP transport WinRM + needs to allow unencrypted communication. This can be enabled via the + WinRM commandline tool. However, this is not the recommended + communication mode. +

    +
    +winrm set winrm/config/service @{AllowUnencrypted="true"}
    +
    + + + diff --git a/docs/index.html.in b/docs/index.html.in index 536e354962..c84eb1f314 100644 --- a/docs/index.html.in +++ b/docs/index.html.in @@ -59,6 +59,9 @@
  • The VMware Workstation and Player hypervisors
  • +
  • + The Microsoft Hyper-V hypervisor +
  • Virtual networks using bridging, NAT, VEPA and VN-LINK.
  • diff --git a/docs/sitemap.html.in b/docs/sitemap.html.in index f50a8d2737..505b599a14 100644 --- a/docs/sitemap.html.in +++ b/docs/sitemap.html.in @@ -202,6 +202,10 @@ VMware Workstation / Player Driver for VMware Workstation / Player +
  • + Microsoft Hyper-V + Driver for Microsoft Hyper-V +
  • diff --git a/src/README b/src/README index f95a8b7582..00d11d19a2 100644 --- a/src/README +++ b/src/README @@ -26,6 +26,7 @@ There are two core shared modules to be aware of: Then there are the hypervisor implementations: * esx/ - VMware ESX and GSX support using vSphere API over SOAP + * hyperv/ - Microsoft Hyper-V support using WinRM * lxc/ - Linux Native Containers * openvz/ - OpenVZ containers using cli tools * phyp/ - IBM Power Hypervisor using CLI tools over SSH @@ -41,7 +42,7 @@ Then there are the hypervisor implementations: Finally some secondary drivers that are shared for several HVs. Currently these are used by LXC, OpenVZ, QEMU, UML and Xen drivers. -The ESX, Power Hypervisor, Remote, Test & VirtualBox drivers all +The ESX, Hyper-V, Power Hypervisor, Remote, Test & VirtualBox drivers all implement the secondary drivers directly * cpu/ - CPU feature management