Hyper-V supports both emulated (“legacy”) and Hyper-V-specific (“synthetic”) devices for Linux virtual machines. When a Linux virtual machine is running with emulated devices, no additional software is required to be installed. However, emulated devices do not provide high performance and cannot leverage the rich virtual machine management infrastructure that the Hyper-V technology offers. To make full use of all benefits that Hyper-V provides, it is best to use Hyper-Vspecific devices for Linux. The collection of drivers that are required to run Hyper-V-specific devices is known as Linux Integration Services (LIS).
For certain older Linux distributions, Microsoft provides an ISO file containing installable LIS drivers for Linux virtual machines. For newer Linux distributions, LIS is built into the Linux operating system, and no separate download or installation is required. This guide discusses the installation and functionality of LIS drivers on older Linux distributions.
Blow are the main Points that comes with version 3.5
New OS with 3.5
Expands the list of supported distributions to include RHEL/CentOS 5.5-5.6.
Supported Virtualization Server Operating Systems
This version of Linux Integration Services (LIS) supports the following versions of Hyper-V:
Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, and Windows Server 2008 R2 Datacenter
Microsoft Hyper-V Server 2008 R2
Windows 8 Pro
Windows 8.1 Pro
Windows Server 2012
Windows Server 2012 R2
Microsoft Hyper-V Server 2012
Microsoft Hyper-V Server 2012 R2
When installed on a virtual machine that is running a supported Linux distribution, LIS 3.5 for Hyper-V provides the functionality listed in the table below. For comparative purposes, hereunder also list the features available in LIS 3.4. This allows users to decide if they want to upgrade from LIS 3.4 to LIS 3.5.
1. Static IP injection might not work if Network Manager has been configured for a given HyperV-specific network adapter on the virtual machine. To ensure smooth functioning of static IP injection, ensure that either Network Manager is turned off completely, or has been turned off for a specific network adapter through its Ifcfg-ethX file.
2. When you use Virtual Fibre Channel devices, ensure that logical unit number 0 (LUN 0) has been populated. If LUN 0 has not been populated, a Linux virtual machine might not be able to mount Virtual Fibre Channel devices natively.
3. If there are open file handles during a live virtual machine backup operation, the backed-up virtual hard disks (VHDs) might have to undergo a file system consistency check (fsck) when restored.
4. Live backup operations can fail silently if the virtual machine has an attached iSC SI device or a physical disk that is directly attached to a virtual machine (“pass-through disk”).
5. LIS 3.5 only provides Dynamic Memory ballooning support—it does not provide hot-add support. In such a scenario, the Dynamic Memory feature can be used by setting the Startup memory parameter to a value which is equal to the Maximum memory parameter. This results in all the requisite memory being allocated to the virtual machine at boot time—and then later, depending upon the memory requirements of the host, Hyper-V can freely reclaim any memory from the guest. Also, ensure that Startup Memory and Minimum Memory are not configured below distribution recommended values.
We are working on new private cloud implementation with high restrictive security boundaries, while adding new Hyper-v cluster “ Windows 2008 R2 Sp1 Core edition” we got error
We make sure that we are using administrator account, No firewall problems.
We have Parent Domain (xxx.local) where all Management servers are running "VMM, SCOM and DPM" and we have child domain "YYY.xxx.local" where all Hyper-v servers are running "10 Servers in One Hyper-v cluster using Windows 2008 R2 SP1 Server Core"
the Hyper-v hosts are from HV01 to HV10 and using IPs from XX.XXX.XX.51 to XX.XXX.XX.60 and Hyper-v cluster IP is XX.XXX.XX.61
When I am trying to ping any node of the Hyper-v hosts it is working fine, Able to resolve the Hosts names using NSLOOKUP
When I am trying to add any host to Hyper-v cluster I got this error
 084C.06D4::06/03-09:25:30.427#18:ServerConnection.cs(1229): Microsoft.VirtualManager.Utils.CarmineException: HV01 cannot resolve with DNS.
I tried to add the host name "netbios and FQDN" to hosts file and got the same error. the funny thing that when I am trying for example HV04 I got the same error that the servers HV01 cannot resolve with DNS. !!!!!!!!!!
VMM is trying to resolve HV01 not Hv04, I tried IPs and got the same error.
After some troubleshooting it turn to be something wrong in the VMM Server
Using Network Monitor and Wirshark here what i found
When adding the cluster IP or FQDN , VMM Service check with Parent DC to resolve and it manage to get the IP "it does not matter wherever I provide IP or FQDN"
Then the VMM checks with the Child DC for the cluster "Since The cluster and Hyper-v hosts exist in the child domain" and it resolve the cluster name.
VMM start to query the cluster nodes and resolve all nodes and suddenly it start searching for any random host NetBIOS name and consider Host.Parent.domain not hots.child.parent.domain without any reasons and return error that it can not resolve the name
So for the seek of troubleshooting we added all the hosts NetBIOS and FQDN to hosts file and got the same error. Analyzing the capture I found that all Cluster name and all hosts were resolved but suddenly the VMM did the same again with Cluster name "Since it is not added to hosts file"
Adding all Hosts and Cluster names to Hosts file solved the problem.
At a high level, here’s a list of the changes since v3.1:
- Synthetic Mouse Support: The virtualized mouse device is no longer bound to the VMConnect window, and can now be used with a RDP session.
- Merged Device Drivers: We now present a single device driver for both IDE and SCSI devices (hv_storvsc).
- Windows 8 Fix: The synthetic network device (hv_netvsc) can now be used with a Windows 8 host, eliminating the hang on boot that was previously seen.
- SCVMM Fix: This release fixes the issue as described in KB2586286.
- Improved Setup Experience: Users now only need to run install.sh (as root) to automatically detect the correct architecture and install the appropriate drivers.
In addition, I would like to mention a number of requirements and limitations on the use of this package of integration:
- The driver applied to guest virtual machines running Red Hat Enterprise Linux Server 6.1 (architecture x 86 and x 64) and CentOS 6.0 (architecture x 86 and x 64). For earlier version should be used components integration version 2.1
- In fact, it’s modified drivers in the Linux kernel 3.2, but can work with the Linux kernel 2.6.32, shipped with Red Hat and CentOS
This week I got a call from one of my team mates (Nashaat Sorial) telling me that he is facing a problem with his Hyper-V cluster..
He is running 3 Hyper-V hosts with Windows 2008 R2 SP1 running multiple applications. One of the hosts keep failing and He can not Live migrate any VM to the other hosts until restart.
We went through all well known workarounds for such cases like
1- if you have AV please disable
3- Please if you have teaming..Break it and check again
4- Please check http://support.microsoft.com/kb/981618
5- Make sure that you enable the "file and printer sharing" as well as the "client for MS networks" on the heartbeat networks cards on all nodes. http://support.microsoft.com/kb/2008795
So we have to start reading more in the cluster logs. You can generate the cluster logs as per
We got some interesting data and errors in the logs just like:
In Win2008 the Physical Disk resource type private property that stores the disk signature change from "Signature" and it is now "DiskSignature" in Win2008. The lack of the DiskSignature property not being populated was resulting in the resource failing to come online
ERROR_CLUSTER_GROUP_MOVING(5908)’ because of ”Virtual Machine Configuration R-Web2003′ is owned by node 2, not 1.’
mm.. So it looks like something from the Hardware level. Searching HP blades errors come with more useful information
he HP Integrated Management Log shows ‘ASR Detected by System ROM‘ along with the following events in the System event log on an affected machine:
Event Type: Warning
Event Source: hpqilo2
Event Category: None
Event ID: 57
Failed GET SENSOR READING, sensor 16
Event Type: Warning
Event Source: hpqilo2
Event Category: None
Event ID: 57
NetFN 0x4, command 0x2D timed out
The solution for this was to perform the following:
- Install the latest ILO Firmware Update v. 1.81
- Install the HP iLO Management Channel Interface Driver v. 220.127.116.11
- Install the HP ProLiant iLO2 Management Controller Driver v. 18.104.22.168
All of these drivers can be downloaded form the following location, selecting your operating system:
okay..I know that most people already knows that running DAG servers on Hyper-V cluster and UM on Hyper-V now is supported… Really Good news.
Microsoft already has a techNet resources covering that but also now we have a white paper for that.
The purpose of this paper is to provide guidance and best practices for deploying Microsoft® Exchange Server 2010 in a virtualized environment with Windows Server® 2008 R2 Hyper V™ technology. This paper has been carefully composed to be relevant to organizations of any size.
Virtualizationmatrix.com did a good effort listing vSphere vs Hyper-V vs XenServer features.. You can compare and even change versions
Q7: Is Hyper-V Dynamic Memory supported for SQL Server?
A7: Hyper-V Dynamic Memory is fully supported with SQL Server. Only SQL Server versions and editions (Enterprise and Datacenter) that support Hot Add Memory can see memory that is added by using Hyper-V Dynamic Memory. SQL Server versions that do not support Hot Add Memory are still supported. But these versions will detect only the memory that is present in the operating system when SQL Server starts. Before you deploy Hyper-V Dynamic Memory, please read the following resources when you use Hyper-V Dynamic Memory with SQL Server:
SQLOS Team Blog – Hyper-V Dynamic Memory (http://blogs.msdn.com/b/sqlosteam/archive/tags/hyper_2d00_v+dynamic+memory/)
Windows Virtualization Team Blog – Dynamic Memory (http://blogs.technet.com/b/virtualization/archive/tags/dynamic+memory/)