September 2014 Windows Updates Issue on Hyper-V hosts?

I performed some End of Month updates this weekend which froze the login screen on my Hyper-V hosts, no mouse movement, Ctrl+Alt+Del did nothing, non responsive. We were forced to perform a hard reset on the machines that is currently hosting around 100 VMs. I am glad we were able to recover from this malfunction but I am having issues trying to determine what exactly caused this issue.

Has anyone else seen this issue on Windows Server 2012 R2 platform and where should I start my investigation?

I have not noticed any issues on my physical servers, workstations, etc. except on the Hyper-V hosts.

Hi Team,

I am designing  Solution for 1700 VDi user's . I will use Microsoft Windows 2012 R2 Fileserver Cluster to host their Profile data by using Group Policy for Folder redirection.

I am looking best practice to define Storage disk size for User profile data . I am looking to have Single disk size of 30 TB to host user Profile data .Single disk which will spread across two Disk enclosure .

Please let me know if if single disk of 30 Tb can become any bottle neck to hold user active profile data .

I have SSD Writable disk in storage with FC connectivity.

Thanks

Ravi

Hello everyone,

I have come know that during migration of process of VM, consumer of IaaS cloud not gets the same VM. His VM is changed during the migration process. Components of VM like from bios, boot loader, operating system to applications are changed. I need to know that: 1. Will OS running on VM will be changed or remain same? 2. Will Core components of VM such as BIOS, Boot Loader and OS be changed during migration of VM.

Thanks in anticipation 

Hi

In my production hyper v Guest machines have IC version are

All my Windows 2012 R2 VM's (that run on a 3-node Windows 2008 R2 Fail-over cluster) are backed up by DPM 2012 R2 (also on Windows 2008 R2) using Saved State instead of Child Partition Snapshot. I've checked the list below, but didn't find anything applicable to these VM's. 

• Backup (Volume Snapshot) Integration Service is disabled or not installed.
• The virtual machine has one or more dynamic disks.
• The virtual machine has one or more non-NTFS based volumes.
• The virtual machine Cluster Resource Group in a cluster setup is offline.
• The virtual machine is not in a running state.
• A ShadowStorage assignment of a volume inside the virtual machine is explicitly set to a different volume other than itself.
• An App-V drive is installed on the virtual machine that creates a non-NTFS volume.

I've set the registry setting SystemRestore\ScopeSnapshots to 0 for each VM, and checked the current state with the diskshadow tool (to make sure it wasn't just an erronous datasource text in DPM). 

Can somebody point me in a direction on how to further investigate this problem? I'm running out of ideas for this one :-(

TIA!

Jeroen Brattinga

Hi!

I'm running Windows Hyper-V Server 2012 R2. In one beautiful day the server stopped responding partly. I mean all quest machines are still running and I can see event viewer and ping it, but server shares or remote desktop or Hyper-V manager are not accessible any more.

In system log I see following errors:

• 10010 - The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. - after every 30 seconds, in the end this is the only error!

• 7011 - A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Winmgmt service. - everything starts with this error.

After I restart the server it works for some hours or maybe a day and the problems start again.

Any ideas what can be wrong or how to troubleshoot?

Thanks in advance!

UV

Hello, 

We have a Hyper-V cluster servers on Windows Server 2012 R2. I use SAN and it connects with fiber channel. We use Windows MPIO.

If i try to open Hyper-V setting for any VM, I wait too much. It opens too late. Also, the disk management brings disk information too late on hosts.

Hello, all.

We are running an automated tests with Microsoft Test Manager and SCVMM virtual environments. Recently we started to mount ISO images with file collections on VMs (we used to copy them to VMs from a network share, but it was too slow and caused timeouts and network share access problems).

ISO images is being mounted via WMI Hyper-V Provider. The images are located in host's local folders (C:\ISO), which are also network shares being synced with "primary" share with DFS.

The problem is: sometimes (I'd say in 1 case from 100) a virtual machine doesn't "see" mounted drive like it's ejected. But Hyper-V Manager shows correct "image file" in the VM's settings. Changing it to "None" and back to the same image file fixes the problem. 

Is it a bug in Hyper-V? We even inserted an additional check: after calling WMI we also run dir D:\ to ensure the image is mounted. And it's there. And then it doesn't...

Any suggestions other than re-mount an image every time it's needed :-) ?

Hello. I have two windows 2012 hyper-v servers as replication partners. One is the primary where the virtual machines are running and the secondary is the replica partner and runs a secondary domain controller.

Friday afternoon the primary hyper-v server failed (controller failure) so i had to wait for parts to arrive. I had to run with the secondary server, so i made a manual failover for the virtual machines i wanted. Eveything ok and it worked.

My question is what will happen when the primary server is online again. What are the steps i must follow? Do i bring the server online and synchronization will occur automatically?

Regards.

We are running Hyper-V on a 2012 server and for the 20nd time in as many months I've logged into a VM and restarted or migrated to another host it but it's stuck in the "stopping" state in Hyper-V 3.0 and doesn't give me any Turn Off, Shutdown, Save, Pause or Reset options.  The only thing I've been able to do is to schedule a time to reboot the Hyper-V server.  Has anyone else experienced this?  Is there any command I can run get the VM  top turn off  w/o having to reboot or restart the Hyper-V service?

Our host environment as below:

HP C7000 Blade Chasis

16x ProLiant BL460c Gen8 Server (Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz (8 Cores) - 256GB Ram)

Blades server have Hp FlexFabric 10Gb 2-port

2x HP VC Flex-10 Enet Module on Chassie

HP VC 8Gb 20-Port FC Module on Chassie

Also We turned off tcp checksum offloading but it didn't work.

We've opened case to HP support but they analyzing our system and didn't find any problem to themself.

Does anybody have any fixes for these problems?

Hi,

I have a eight node cluster which is all up running and working a treat but when I run the Cluster Validation I receive this warning for each host. I have also included the top few lines of the tests. This warning is repeated from each node to every other node in the cluster.

Warning:

Node HYP01N02.domain.uk is reachable from node HYP01N01.domain.uk by multiple communication paths, but one or more of these paths experienced more than 10% packet loss.

Each node has:

iSCSI1 VLAN101 is a 1x 10Gb port and iSCSI2 VLAN 116 is a 1x 10Gb port configured with MPIO

Trunk1 (4x 1Gb NIC) (Address Hash, LACP) on which sits a team with vEthernet (Management) VLAN 101 and vEthernet (Cluster) VLAN 104

Trunk10 (2x 10Gb NIC) (Hyper-V Port, LACP) on which sits a second team with VM traffic and vEthernet (Migration) VLAN 105

Trunk1 and Trunk10 are configured with LACP and locked down to the relevant VLANs on the switch as well as on the vNICs. (Don't know if its best practise to leave the trunk open to all VLANs if the NICs are configured in Hyper-V with VLANs or have both set like they currently are)

iSCSI1 is on VLAN 101 and ip range of 10.100.1.x

iSCSI2 is on VLAN 116 and ip range of 10.100.2.x

vEthernet (Management) is on VLAN 100 and on ip range 172.21.59.12

vEthernet (Cluster) and vEthernet (Migration) are also on there own VLANs and ip ranges.

iSCSI1 and iSCSI2 only has ip v4 and ip v6 left enabled and DNS registration and NETBIOS disabled.  They do have Jumbo frames enabled.

Each network can talk over the relevant NIC or vNIC to the other hosts on the same NIC or vNIC which is correct and not across networks which they shouldn't so (Migration) to (Cluster) etc which is also correct.

(Cluster) and (Migration) only allow cluster communications

(Management) accepts cluster and client communications.

iSCSI1 and iSCSI2 are set to NOT allow any cluster traffic.

Binding Order:

1.Management
2.iSCSI1
3.iSCSI2
4.Migration
5.Cluster

Cluster metric is 900 and Migration 1000.

I still receive the warning below and I assume its because some how when testing, there seems to be a tiny conection across VLANs and ip ranges from iSCSI1 or iSCSI2 to the vNIC (Management) which shouldn't be the case. I assume the error is because of the highlighted line of the table???

Can anyone suggest anything, it is driving me mad! Things seem to work properly but I need the test to complete correctly to be able to sign the clients environment off.

I'm surprised that there is (even if a little) any chat between iSCSI and vEthernet Management according to the test even though they are on different physicalNICs, IP range an even VLANs. Also, trying  to establish if the warning is just that a warning or something to be concerned about. Obviously with all networks broken up as they are, there will be multiple paths between each node of which many are locked down so they cant talk.

Concern is that although it all works fine and even the results read right, I have never seen the warning before in any implementation even when broken up by VLANs, IP ranges and virtual or physical NICs.

This issue was found because of this issue: "http://social.technet.microsoft.com/Forums/windowsserver/en-US/2aa0b53d-fb3d-4e63-ab76-58e72462fb1a/wmi-high-cpu-usage-on-hyperv-vms-related-to-data-exchange-integration-service?forum=winserverhyperv"

The fix didn't seem to work for me. Anyway here is my main issue.

Please see: http://i.imgur.com/w1poacd.png

Is anyone else experiencing this?

Is 5% CPU usage from the Data Exchange service just to tell the OS Type and IP address acceptable?

5% from a single VM might not seem like a lot but you do that over 50 VM's on a Host and it adds up quickly.

It seems rather aggressive.

Any feedback would be greatly appreciated.

Background info:

This is a Gen 2 2012 R2 U1 fully patched VM on a 2012 R2 U1 Fully Patched Hyper-V Host.

hi

i am getting a cluster validation warning below - 8 node cluster

NETWORK DESIGHN

1- WINDOWS NETWORK,2-HB NETWORK,3-LIVEMIGARTION, 4-MANAGEMNET NETWORK 5- VM NETWORK (TEAMED 3 NIC )

Node SHQSRV02.ZIME.BIZ is reachable from node SHQSRV01.ZIME.BIZ by multiple communication paths, but one or more of these paths experienced more than 10% packet loss.

Following are the connectivity checks made using UDP on port 3343 from network interfaces on node SHQSRV01.ZIME.BIZ to network interfaces on node SHQSRV02.ZIME.BIZ
Result    Source Interface Name    Source IP Address    Destination Interface Name    Destination IP Address    Same Cluster Network    Packet Loss (%)
Success    SHQSRV01.ZIME.BIZ - HB    192.168.198.10    SHQSRV02.ZIME.BIZ - HB    192.168.198.11    True    0
Success    SHQSRV01.ZIME.BIZ - HB    192.168.198.10    SHQSRV02.ZIME.BIZ - Production    10.10.65.11    False    97
Failure    SHQSRV01.ZIME.BIZ - HB    192.168.198.10    SHQSRV02.ZIME.BIZ - MGMT    10.250.250.58    False    100
Failure    SHQSRV01.ZIME.BIZ - HB    192.168.198.10    SHQSRV02.ZIME.BIZ - LiveMigration    192.168.199.11    False    100
Success    SHQSRV01.ZIME.BIZ - LiveMigration    192.168.199.10    SHQSRV02.ZIME.BIZ - LiveMigration    192.168.199.11    True    0
Success    SHQSRV01.ZIME.BIZ - LiveMigration    192.168.199.10    SHQSRV02.ZIME.BIZ - Production    10.10.65.11    False    97
Failure    SHQSRV01.ZIME.BIZ - LiveMigration    192.168.199.10    SHQSRV02.ZIME.BIZ - HB    192.168.198.11    False    100
Failure    SHQSRV01.ZIME.BIZ - LiveMigration    192.168.199.10    SHQSRV02.ZIME.BIZ - MGMT    10.250.250.58    False    100
Success    SHQSRV01.ZIME.BIZ - MGMT    10.250.250.45    SHQSRV02.ZIME.BIZ - MGMT    10.250.250.58    True    0
Success    SHQSRV01.ZIME.BIZ - MGMT    10.250.250.45    SHQSRV02.ZIME.BIZ - Production    10.10.65.11    False    97
Failure    SHQSRV01.ZIME.BIZ - MGMT    10.250.250.45    SHQSRV02.ZIME.BIZ - HB    192.168.198.11    False    100
Failure    SHQSRV01.ZIME.BIZ - MGMT    10.250.250.45    SHQSRV02.ZIME.BIZ - LiveMigration    192.168.199.11    False    100
Success    SHQSRV01.ZIME.BIZ - Production    10.10.65.10    SHQSRV02.ZIME.BIZ - Production    10.10.65.11    True    0
Failure    SHQSRV01.ZIME.BIZ - Production    10.10.65.10    SHQSRV02.ZIME.BIZ - LiveMigration    192.168.199.11    False    100
Failure    SHQSRV01.ZIME.BIZ - Production    10.10.65.10    SHQSRV02.ZIME.BIZ - HB    192.168.198.11    False    100
Failure    SHQSRV01.ZIME.BIZ - Production    10.10.65.10    SHQSRV02.ZIME.BIZ - MGMT    10.250.250.58    False    100

THIS WARNING ONLY BELONGS TO HEARTBEAT NETWORK AND LIVEMIGARTION NETWORK

WHERE SHOUL I CHECK , PLEASE HELP

Windows 2012 R2 VM with SQL 2014 on Hyper-v 2012 core is throwing SQL errors during VSS replica.  I have ran a test failover and the recovery point seems fine.  It almost looks like no database changes have occurred and the VSS engine is aborting the thread inappropriately.  If this is not an actual error is there any way to suppress these messages?

BACKUP failed to complete the command BACKUP DATABASE msdb. Check the backup application log for detailed messages.

BackupVirtualDeviceFile::SendFileInfoBegin:  failure on backup device '{F93039AB-B6A8-4944-93B2-6B2737228FEB}2'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1972. Thread=7360. Client. Instance=. VD=Global\{F93039AB-B6A8-4944-93B2-6B2737228FEB}3_SQLVDIMemoryName_0. 

Hi.

I have a Hyper-V 2012 cluster with 5 nodes. All HP Blade servers in the same enclosure, on 3PAR FC SAN storage. I wanted to run routine maintenance on the hosts, i.e., Windows Update. So I Live Migrated the VMs off one host at a time, paused it in Failover Cluster Manager, rebooted, unpaused, and failed the roles back manually.

After updating the second host, I decided to fail the roles back when unpausing. The instant one of the VMs moved back to this host, it failed to start, and got a red X in FCM.

The VM had 2 virtual disks. I removed one, leaving only the system disk. When I started it, it ran CHKDSK a couple of times and eventually came back, appearing to be healthy (a miracle!). But I cannot add the second VHDX to the VM. It throws an error:

Dan

I have been tasked with setting up a Hyper-V R2 3 node failover cluster. I have very limited clustering or Virtualization experience. So here I am asking for some Best Practices and if my implementation will work.

3 HP DL380 G8 with 1 4p onboard nic and 1 4p pci nic

1 HP D380 G8 with 14p onboard nic (used for VMM)

Dual HBA - SAN

My network team carved out several VLANs for me but they are NOT trunced.

SAN Team will setup all SAN connections

So here is my plan.

1 NIC - Management, 1 NIC - Backup, 1 NIC - Live Migration, 1 NIC - CSV/HB, 1 NIC - VM

Here is my confusion - I was given IP address ranges for the Management, Backup, VM, HB networks but none for the Live Migration. I was told by the networking team that internal non routable communication is setup as layer 2 and I could pick any IP range I wanted.

All the reading I have been doing on Hyper-V seems that every setup with LM has an IP range associated with it. So should I request an IP range from them or go ahead and pick an IP range (excluding the internal ranges like 192.168..etc).

This cluster will all be in the same datacenter and in the same site and will host currently planned 10 - 15 VM.

Thanks for any suggestions/Guideance

Nick

Nick

When enabling replication on several VM's, I receive Hyper-V failed to enable replication for virtual machine "virtualmachinename": Incorrect funciton. (0x8007001). However this error doesn't happen to all VM's and it isn't related to any particular host.

I've traced this down to a VSS error, however when running ">vssadmin list providers", I receive the following indicating there are no errors:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'Cluster Shared Volume VSS Writer'
   Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
   Writer Instance Id: {fab685fb-d333-4744-b46a-c63fc6360737}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {5583acc3-a218-4ce6-bce9-93ff551ad8aa}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {dd5f1635-d7ce-434b-84f7-9aaf216d5339}
   State: [1] Stable
   Last error: No error

Writer name: 'Cluster Database'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {0a0f16ab-b57a-4403-9059-1ea7aa3abc90}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {ce09aaff-1515-4240-b5a5-8c2710a4163a}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {faee5f76-086d-454c-afdb-4f8391c0ed7d}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {2b649ed6-9451-40d8-b45d-e11f171aca87}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {3cd0e01a-62a9-4ba4-b6dc-277a66719ae0}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {f10f17aa-c8e7-42ee-84df-ed2bbf3ac187}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {45e94e87-c253-45d5-942a-462f3fece288}
   State: [1] Stable
   Last error: No error

The providers I'm using are:

Provider name: 'Microsoft CSV Shadow Copy Helper Provider'
   Provider type: Software
   Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d}
   Version: 1.0.0.1

Provider name: 'Microsoft CSV Shadow Copy Provider'
   Provider type: Software
   Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}
   Version: 1.0.0.1

Provider name: 'Microsoft File Share Shadow Copy provider'
   Provider type: Fileshare
   Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Provider name: 'Dell EqualLogic VSS HW Provider'
   Provider type: Hardware
   Provider Id: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
   Version: 4.6.0

Has anyone run into this before?

-Jeremy Houp

I am currently contemplating a setup like in the drawing I made for  a lab environment. I have a few  questions regarding this setup. Do I need VLAN? Physical NIC 2 will probably be bridged between the subnet of the VM's and the subnet of the physical machine to be able to go on the internet?  

For security reasons I am assuming that VM 2 and VM 3 will have private network settings in Hyper-V so that all traffic to these 2 machines originate from VM 1. VM 1 on the other needs to be setup with External Network!?