Hyper-V host crashes and has bug checks when you perform a VM live migration in Windows 8.1 and Windows Server 2012 R2

Microsoft has released the most important KB for Hyper-V related with VMQ,LBFO and LM

—

Consider the following scenario:

  • You have a Windows Server 2012 R2-based computer that is configured for one or more NIC teams by using Windows NIC Teaming (LBFO).
  • You have implemented Windows NIC Teaming (LBFO) in Switch Independent teaming mode by using Hyper-V Port or Dynamic Load Balancing mode. Additionally, you have correctly configured the NICs to use non-overlapping processors. (For more information, see Knowledge Base article 2974384).
  • A Hyper-V virtual switch is bound to one of the LBFO teams.
  • You start a virtual machine on the Hyper-V server, or you live migrate a virtual machine from one server to another server.

In this scenario, you experience one or more of the following issues:

Log Name: System
Source: Microsoft-Windows-Hyper-V-VmSwitch
Date: <DateTime> 
Event ID: 113
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: Server1.contoso.com
Description:
Failed to allocate VMQ for NIC EDCED345-4C96-4C75-92A0-0C4FC5688F73--35BEB899-5BE9-4128-900A-6FE0BBFC7B22
(Friendly Name: Network Adapter) on switch DE4F3664-68D9-4781-825B-882A540FAB08 (Friendly Name: VM Switch).
Reason - The OID failed. Status = {Operation Failed} The requested operation was unsuccessful.

Additionally, the Hyper-V VmSwitch may fail to allocate VMQ queues for virtual machines.

+ This KB solves the problem described here

Download

SPLA and VDI

Microsoft VDI and VDA FAQ 3.0:

Currently, there is no SPLA model for Windows VDA. Hence, customers
who subscribe to desktops from a third-party hoster will need to
pay Microsoft for a Windows VDA license for each device accessing
Windows client virtual machines in the datacenter. Additionally, hosters
need to ensure they isolate the hardware and other resources for each
company. Any hardware running an instance of Microsoft software (OS
or application) must be dedicated to a single customer. For example, a
SAN device that is not running any Microsoft software may be shared
by more than one customer; whereas, a server or SAN device that runs
Microsoft software may only be used by one customer.

Services Provider Use Rights (April, 2015):

Desktops delivered as a service are supported under SPLA using Windows Server and Remote Desktop Services (RDS). The Windows Desktop Operating System cannot be used to provide a hosted client, hosted graphical user interface or desktop as a service.

Providing Microsoft Desktop as a Service licensing guide:

Offering a Desktop as a Service (DaaS) solution requires giving your customer an appropriately licensed solution for the entire software solution stack. The software solution stack depends on the software delivery model selected:

  • DaaS through the Microsoft Services Provider License Agreement (SPLA) via the Microsoft Windows Server Operating System or
  • DaaS through Dedicated Outsourcing using your customer’s Microsoft Volume Licensing agreement.

No option is available in the SPLA to provide a hosted virtual desktop using the Windows Desktop Operating System; however this is possible to do through Dedicated Outsourcing.

dedicated outsourcing vdi microsoft

…

DaaS through SPLA does not require dedicated hardware.  You can provide DaaS through a SPLA on servers accessed by more than one customer.

No words.No logic. Just one question. Why?