# Virtual Machine Manager Copyright (C) 2009 France Telecom |

Documentation Home Installation Resource Configuration About VMM MBeans Client programming Reference Javadocs Drivers Dummy driver VMware VI driver Xen driver Hyper-V driver Driver framework |
Hyper-V driver
The Hyper-V driver allows to manage a server pool made up of host machines running the Windows Server 2008 R2 including Microsoft Hyper-V Server.
Hyper-V driver installation instructions
The Hyper-V driver needs to establish WMI connections with host machines. The driver requires the activation of WMI remote connections on each hosts. And the user whose authentication credentials will be used to access the host machine must have the right permissions. On each hosts follow these instructions (from J-Interop documentation and J-Integra documentation ) : Configure the Firewall for DCOM protocol or turned it off Make sure that the Server Service and Remote Registry Service are running Give the user DCOM permissions : Go to Control Panel > Administrative Tools > Local Security Policy > Security Settings > Local Policies > Security Options : Double-click "DCOM: Machine Access Restrictions" policy, click Edit Security, add the user, allow "Remote Access" Double-click "DCOM: Machine Launch Restrictions" policy, click Edit Security, add the user, allow "Local Launch", "Remote Launch", "Local Activation", "Remote Activation" Go to Control Panel > Administrative Tools > Component Services > Computers > right-click My Computer > click Properties > click COM Security tab :- In Access Permissions section, click Edit Default > add the user, allow "Remote Access" In Launch and Activation Permissions section > click Edit Default > add the user, allow "Local Launch", "Remote Launch", "Local Activation", "Remote Activation" Configure DCOM using DCOMCnfg in Component Services : Click Start, click Programs, click Administrative Tools, click Component Services. Expand Component Services, expand Computers, and right-click My Computer. Select Properties. Click Default Properties. Select Enable Distributed COM on this computer. Set the Default Authentication Level to Connect (None also works). Set the Default Impersonation Level to Identify (Impersonate also works). Click Default COM Security. Under Default Access Permissions click Edit Default. Add SYSTEM, INTERACTIVE, and NETWORK. The user must also be included in this list. Under Default Launch Permissions click Edit Default. Make sure the Default Launch Permissions have the same values as the Default Access Permissions. Click Default Protocols. Make sure Connection-oriented TCP/IP is listed first. In regedit, you have to update or create these following keys (If you don't have the permission, open the "Permissions" window of the key and under Advanced > Owner add your account as owner) : Create an new String Value named AppID under the key HKCR\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6} which contains {76A64158-CB41-11D1-8B02-00600806D9B6}. HKCR\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6} AppID = {76A64158-CB41-11D1-8B02-00600806D9B6} Create a key under HKCR\AppID named {76A64158-CB41-11D1-8B02-00600806D9B6} then create the following values : HKCR\AppID\{76A64158-CB41-11D1-8B02-00600806D9B6} (Default) = "WBEM Scripting Locator" DllSurrogate = Make sure that your Windows machine is up to date with all the Service packs and updates from Microsoft. After configuring your DCOM settings, reboot your machine to allow the new settings to take effect.
Hyper-V Driver Properties
The following properties can be set on a per-server-pool basis:
Name | Default value | Description
--- | --- | ---
hypervUser | none | login of the user with sufficient administrator priviledges for every host of the server pool
hypervPassword | none | password of the user for every host of the server pool
vmFolderPath | none | Path of the Hyper-V VM folder where the JMX agent will create VMs for the server pool. The path must be made of double backslash(\\) as Windows path.
vmTemplateFolderPath | none | Path of the Hyper-V VM folder containing VM templates which will be made available through the virtual machine image store of the server pool. The path must be made of double backslash(\\) as Windows path.
Legacy_Network_Adapter | true | If the Hyper-V driver will add a "Legacy Network Adapter" or a "Synthetic Network Adapter" to the VMs. The value is "true" or "false"
Event_Collector_Period | 10 | Refresh time of the Event collector in second
Hyper-V Driver sample resource configuration
> The following resource file creates a single ServerPool driven by the Hyper-V driver and consisting of three hosts:
>     <?xml version="1.0" encoding="UTF-8"?>

>     <domain name="ProjectXYZ">
>        <serverPool name="ServerFarm-dev" driver="hyperv" properties="hyperv-farm.props">
>          <host name="i-server01.foobar.org" />
>          <host name="i-server02.foobar.org" />
>          <host name="i-server03.foobar.org"/>
>        </serverPool>
>     </domain>
The hyperv-farm.props file is as follows hypervUser=administrator hypervPassword=XXXX vmFolderPath=C:\\Users\\Public\\Documents\\Hyper-V\\VMFolder vmTemplateFolderPath=C:\\Users\\Public\\Documents\\Hyper-V\\VMTemplateFolder Legacy_Network_Adapter=true Event_Collector_Period=10