Hi

We are using HV 2012 R2 failover cluster with CSV. We found some articles saying pass through disks outperforms CSV. Is this correct?

Regards

LMS

Hi,

I am looking for some advice on what the best way to configure my disk system is for performance when using Hyper-V. Currently I have two midline 7.2k SATA disks used for the hyper-V OS in RAID 1, and then 14 x 10k 600GB SAS enterprise disks in RAID 10. The RAID 10 is where all my VM’s exist on, but not directly on the physical disk, I use a product called StarWind which consumes almost all of the physical disk space, this is a virtual SAN and I use this for my CSV in the cluster, the VM’s all exist on this starwind disk, there is a tiny amount of overhead but I don’t think that’s really where my problem lies. We have 12 Virtual machines, so there is 1 spindle per VM, however it’s in RAID 10 so does this actually mean I have 7 spindles for 12 VMs?

The entire system almost grinds to a halt whenever I am copying new VM’s onto this host. I can’t use any other RAID type except for RAID 1 or 10. I know RAID 0 would give me better performance but we are not willing to take the risk. Now, it is my understanding that RAID 1 and 10 are essentially the same with the same performance and capacity, because of this I chose RAID 10 so I can take advantage of the combined capacity, but I am wondering if this is the best configuration.

I can think of a few other variations:

• A single RAID 10 with one large partition but multiple CSV’s instead of one large one
• A single RAID 10 with multiple partitions and a CSV on each partition
• Multiple RAID 1, each having a single partition and a single CSV

Reading this site, there are a few pointers I have taken away regarding disk performance, a couple below I have questions about.

http://www.altaro.com/hyper-v/23-best-practices-improve-hyper-v-vm-performance/

Point 6 says “Use separate volumes for each VM. Since the administrative tasks of a virtual machine are controlled by its own process (VMWP.exe), keeping several virtual machines on a single volume will cause more Disk I/O operations from each worker process. Hence, it is recommended to use separate volumes for storing virtual machine files (VHD, VHDx, checkpoints, and XML).”

Does this mean the arrangement I propose in my second point above – multiple partitions and a CSV on each partition? The term “Volume” seems to be a bit ambiguous depending on where you read

I believe point 14 to be incorrect though. “De-fragment Hyper-V Server regularly or before creating a virtual hard disk. It is advisable to defrag Hyper-V Server disks where the VHD and virtual machine configuration files are stored regularly or before creating a large virtual hard disk file.”

It is my understanding that defrag only tends to work well if there are many files on the disk, on the physical disk in my case there is one massive starwind file so I don’t think defrag on the physical will do anything, defrag in the starwind disk might help but it is mostly large VHDX files – will defrag really make much difference?

Additionally, I don’t have any generation 2 VM’s and there’s nothing I can do about this right now, all data disks use SCSI channels on the VMs, all VHDX are fixed size.

Also, a slight side question but kind of related – I have both an exchange server and SQL server running as VM’s (the log files already exist on separate VHDs, but on the same physical RAID 10 disk), does my physical disks used for log files need to match those used for the DB, or can they be slower lower class disks… for example, if I place a 7.2K disk in with a RAID made up of 10K disks, it is my understanding that the entire RAID will lower its performance of the slowest member – is this true with log files and databases, if the log files are on slow disks will the database also go slower to match the pace of log files being written?

many thanks

Steve

Hello. I have a hyper-v server with 3 terminal servers (in fact there are two hyper-v with a totall of 6 terminal servers).

Hyper-V server is W2K8R2 and so are the terminal servers.

Users connect to the terminal servers using RDP and are unable to play sounds locally on their thin and fat clients.

I installed Desktop Experience and offcourse done the steps below.

1. Start -> Run -> services.msc
2. Change the Windows Audio service from 'Disabled' to 'Automatic' - and start it.  
3. Lauch the Remote Desktop Session Host Configuration utility by going to START -> RUN/SEARCH -> and typing entering the following command: tsconfig.msc <ENTER>
   
4. On the right-hand pane, double click on 'RDP-TCP'
5. Select the 'Client Settings' tab
6. Clear/Uncheck the Audio and video playback check box
7. Log off the system and launch your RDP client.
8. Before you connect to the system, click the Options button/arrow to expand the RDP session options.
9. Click the ‘Local Resources Tab’ and under ‘Remote audio’ click the ‘Settings’ button.
10. On the window that pops-up, under ‘Remote audio playback’ click ‘Play on this computer’ and click OK.
11. Connect to the virtual machine and you now have sound!
12. (quick test, you can use START -> RUN -> c:\windows\media\tada.wav  (it may prompt you to configure Media Player for first usage).

After this, the users are still unable to play audio in their terminal session.

They have boxes or headphones connected to their devices and are able to play audio local on their fat clients. (Windows pc's)

Does anyone has more idea's?

Hello

I have a test server with Windows 2012 R2 installed, which acts as a standalone Hyper-V Server (not joined to a domain). Among others there are two VM's (Windows 7 and Windows Vista) that I had transferred from a Windows 2008 R2 server. Both can be started and stopped without any problems, I can add and delete snapshots etc.

When I export the Windows Vista machine, all is ok. However, when I try to export the Windows 7 machine to a local SDD (drive E), I get the following error:

An error occurred while attempting to export the virtual machine "CL1" (E1FF00DC-B841-4D80-8FCE-4D6D39BA2370). Error: General access denied error (0x80070005).

What can I do to solve that? The suggestions I found so far, either didn't apply to my case or didn't solve the problem. I tried adding "Everyone" with full access to the VM source folder, but the error message keeps popping up at the very end of the export process.

Please note: Drive E is NOT a connected network share, it's really attached locally to the computer and in fact is the same drive, where all the active VM's are stored.

I need to mentioned a few additional points, which might be important.

1. Both VMs have differential hard disks connected to base disks.
2. The Windows Vista VM could be imported to Windows Server 2012 R2 without problems. - I first exported it in Windows Server 2008 R2, imported it in Windows Server 2012, exported it again, and finally imported it in Windows Server 2012 R2. For the Windows 7 VM, that didn't work. I had to restore the data from a backup to the new folders and manually add them to Hyper-V.
3. One of the base VHDs of the Windows 7 VM is on drive C instead of E and when I move it to the folder, where the other VHDs are and try to repair the connection, I get an error message stating that the superior element can't be set for the virtual drive. I do suppose if I could repair that connection successfully, the problem with the export would be solved as well.

Does anyone have a suggestion what I could try to do to solve the problem?

Hi,

I am currently trying to restore a 2008 r2 image which is .VHD extension to Hyper V.

I have created a VM (501GB) and added it as a disk into disk management. The file of the back up is 146GB which is on a external HDD (500GB). So based on that the destination disk is larger.

I am restoring from a shared location and have attached physical drive as IDE Controller. Physcial drive is offline.

I have run diskpart > clean also.

I keep getting this error " 

No disk that can be used for recovering the system disk can be found" 

On searching this error it came down to the physical size of the drive which in my case is fine.

Can anyone help with what may be causing this error? Am i missing something? Driver that may need to be installed?

This is the first time i am installing image on Hyper V so could be missing something crucial

Hello,

I am trying to create Hyper V Replica Between Two Hyper V Clusters having Three Nodes at Production Site and Two Node Hyper V Cluster at DR Site. I am trying to replicate only three VMs (not the complete cluster) to the DR Site. I am following MS Article where as I create Broker resource , however not sure if I can limit the replication to only three VMs. 

I am looking for a Document which can guide me on Step by Step configuration of the same. 

Note: I don't have SCVMM as if now (planned for Next Year).

Raj

3 hosts in the Hyper-V 2012 cluster and few CSV volumes.

The slow backup performance (around 1xxx MB/min in backup exec) will occure when it meets the following scenario :

1. VM on Node 1 and CSV 1

2. CSV 1 owner is Node 2

When i change the owner of CSV 1 to Node 1, the backup performance will return to normal (over 6000MB/min in Backup exec).

Hi 

I have one problem in my Windows 2012R2 server with Hyper-V Cluster . In this server i have Four Port NIC, and i configured Teaming with two NIC ports, one for Heartbeat and one is free. Server was works fine all theway. suddenly this server is not reachable over the network. but server was running and all my Guest VM's are moved to other Host machine. i can able to connect this server by using hearbeat IP not through Production (Team) IP. what i saw there is yellow exclamation (Seems to be warning) after i disabled and enabled Teaming, Network comes up and i was able to access the server over production network.

Do you have any idea about this issue.

i found some hotfix which is almost same not exactly same.(http://support.microsoft.com/kb/2953202). for me server got disconnected during the server operation.

How ever i found one for Windows 2012 not for R2 http://support.microsoft.com/kb/2908243 

Kris

I am failing to install Hyper-V update for release version of the Hyper-v technology for Windows server Std SP 1 2008 (KB950050)

Error says " current drivers are not supported" i have also tried to install KB948465 and this also comes back with an error.

I think this has to do with the Pre-release version of Hyper-v which i seem to be hitting dead ends with regards to updating from Pre-release to Release version, however this is purely my estimation.

All help will be appreciated

I wish I could have a setup as the following:

1. I have Windows Server 2012 R2
2. I have Two NICs: First one is connected to the LAN and the second one connected to the Internet
3. I have Created two external virtual switches: First one for the LAN NIC and the second one for the Interne NIC
4. I have create one virtual machine and promoted it to domain controller with DHCP working properly. This virtual machine has the LAN external switch.

When I create another Virtual Machine using the second external switch I got connected to the internet inside this second virtual machine.

When I add one more adapter to the second virtual machine from the LAN switch. I can not access the internet from that machine.

My question is:

How to access the internet in a virtual machine that has two adapters one from external switch to the LAN and the other with external switch to the Internet?

I want to be able to connect with a Windows Mobile Device through Windows Mobile Device Center, within a Virtual Machine.  When connecting through the Hyper-V Manager and through Remote Desktop, under "Other supported RemoteFX USB devices", I can see the Symbol USB Sync Cradle.  In the VM, in Device Manager, I don't see a USB connection.  In the VM, I don't see any meaningful errors in the Event Viewer.

Host:  Windows 8.1 Enterprise Hyper-V on a Domain.  Upgraded from Windows 8.1 Pro.  When this computer was originally installed with Windows 8 Pro, Hyper-V was enabled.  I removed Hyper-V, and installed VMWare Player, because I wanted USB Pass-through.  I then uninstalled VMWare and installed VirtualBox.  Recently, I uninstalled VirtualBox, upgraded to Windows 8.1 Enterprise, and enabled Hyper-V.

Virtual Machine OS: Windows Server 2012 R2 on a Workgroup.  Started out with being a VMWare VM, using VMWare Player.  Moved to VirtualBox.  USB Pass-through was working in both those virtual environments.  Used Disk2VHD to convert the VM to a VHDX file.

On the Host:

1. Windows Mobile Device Center is connected to a Motorola Windows Mobile Device (MC959X) sitting in a Symbol USB Cradle.  The OS on the scanner is Windows Embedded Handheld 6.5 Classic CE OS 5.2.29217 (Build 29217.5.3.12.26).  Advanced Networking (USB to PC) is not enabled.
2. Enabled RemoteFX. 
3. In the RDP file, and in the Registry, added the GUID's for:

• WPD "{eec5ad98-8080-425f-922a-dabf3de3f69a}";
• Windows Mobile "{6AC27878-A6FA-4155-BA85-F98F491D4F33}";
• USB Device "{88BAE032-5A81-49f0-BC3D-A4FF138216D6}";
• Windows CE USB Device "{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}";
• GUID_DEVINTERFACE_USB_DEVICE "{A5DCBF10-6530-11D2-901F-00C04FB951ED}"

Ran "sfc /scannow"

All Microsoft Updates are current.

What am I missing?

I need some help.

I installed the November 2014 MS updates last night. I installed them on my lab Hyper-V box. The Hyper-V box is joined to a domain but is not a domain controller. It is Server 2012R2 with Hyper-V with all previous patches applied. I had two VMs configured on the box. The VMs were a 2012R2 server and a Windows 8.1 box. Both were running fine. In fact I shut them down before I did the Microsoft Updates on the server.

The issue I describe below was not present until I did the updates and rebooted. The server and the associated VMs had been running fine for months. These updates are the ones that my SUS server provided to this server.

After I rebooted the server I could not restart either VM. I kept getting the same error that is listed below. I tried DELETING the VM from Hyper-V manager and then building a new VM and using the old vhdx. Again NO LUCK. I even tried CREATING a new VM and I got the same problem.

(Additional Note: I appeared as though I was able to delete the VM from Hyper-V Manager. Hyper-V Manager displayed 'Destroying....' for some period of time and then the VM was removed from Hyper-V Manager. However, recreating the VM did not solve the problem.) 

Each time I get the following error displayed on screen.

'Unnamed VM' could not intiialize.

An attempt to read or update virtual machine configuration failed

'Unnamed VM' could not initialize (Virtual Machine ID)

'Unnamed VM' could not read or update virtual machine configuration: Ran out of memory (0x8007000E) Virtual machine ID B9xxxxxxxxxxxx 

=======================

I adjusted permissions on the C:\ProgramData\Microsoft\Windows\Hyper-V folder. Opened it up to "Authenticated Users" based on a couple of TechNet articles that I found. NO luck

In the Hyper-V Config log I get the following entry,

The configuration store at'' is not accessible Unspecified error(0x80004005)

==========================

I also had these errors in the Windows Application log.

ID=1000 Source=Application Error Type=1 Message=Faulting application name: vmwp.exe, version: 6.3.9600.17334, time stamp: 0x5407c751

Faulting module name: vsconfig.dll, version: 6.3.9600.16384, time stamp: 0x5215db66Exception code: 0xc0000194

Fault offset: 0x000000000001966c

Faulting process id: 0xb84

Faulting application start time: 0x01cffe274d55ea6b

Faulting application path: C:\Windows\System32\vmwp.exe

Faulting module path: C:\Windows\System32\vsconfig.dll

Report Id: d4210450-6a1a-11e4-80d6-0019b9eed814

Faulting package full name:

Faulting package-relative application ID:

I have a Hyper-V 2012 R2 lab environment. I need 2 allocate resources to different groups. For example, how can I allocate 60% of hyper-v resources (compute and storage) to group A and 40% to group B. How do I accomplish this? 

Hi,

in case the  online P2V Migration scvmm 2012 take about 1 hour to complete

do we lose any changes on the live server during this hour ??

Ramy

Hi,

our Microsoft Windows Server 2012 R2 with Hyper-V crashed today.

According to the dumpfile it seems to be something with vhdmp.sys

Any idea what could have been causing this?

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {b500190637, ffffd001577c63b8, ffffd001577c5bc0, fffff801ccc12154}

Probably caused by : vhdmp.sys ( vhdmp!ExFreeToNPagedLookasideList+3c )

Followup: MachineOwner
---------

18: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 000000b500190637
Arg2: ffffd001577c63b8
Arg3: ffffd001577c5bc0
Arg4: fffff801ccc12154

Debugging Details:
------------------


EXCEPTION_RECORD:  ffffd001577c63b8 -- (.exr 0xffffd001577c63b8)
ExceptionAddress: fffff801ccc12154 (vhdmp!ExFreeToNPagedLookasideList+0x000000000000003c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffd001577c5bc0 -- (.cxr 0xffffd001577c5bc0;r)
rax=000000000840542f rbx=ffffe8005b4df080 rcx=ffffe8005a81d220
rdx=ffffe8005a81d220 rsi=ffffe8005b4de000 rdi=ffffe8005a81d220
rip=fffff801ccc12154 rsp=ffffd001577c65f0 rbp=ffffd001577c6670
 r8=0000000000000001  r9=000000000000002f r10=fffff80284a065b0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000001
r14=ffffe8005c2d2440 r15=ffffe8005c2b94f0
iopl=0         nv up ei ng nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010292
vhdmp!ExFreeToNPagedLookasideList+0x3c:
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h] ds:002b:ffffe800`5b4df0b8=????????????????
Last set context:
rax=000000000840542f rbx=ffffe8005b4df080 rcx=ffffe8005a81d220
rdx=ffffe8005a81d220 rsi=ffffe8005b4de000 rdi=ffffe8005a81d220
rip=fffff801ccc12154 rsp=ffffd001577c65f0 rbp=ffffd001577c6670
 r8=0000000000000001  r9=000000000000002f r10=fffff80284a065b0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000001
r14=ffffe8005c2d2440 r15=ffffe8005c2b94f0
iopl=0         nv up ei ng nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010292
vhdmp!ExFreeToNPagedLookasideList+0x3c:
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h] ds:002b:ffffe800`5b4df0b8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80284dc4138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffffffffffffff

FOLLOWUP_IP:
vhdmp!ExFreeToNPagedLookasideList+3c
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h]

FAULTING_IP:
vhdmp!ExFreeToNPagedLookasideList+3c
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h]

BUGCHECK_STR:  0x24

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffff801ccc3bd98 to fffff801ccc12154

STACK_TEXT:
ffffd001`577c65f0 fffff801`ccc3bd98 : ffffd001`577c6660 ffffe800`5b4de000 00000000`00000010 ffffc001`f9c91d00 : vhdmp!ExFreeToNPagedLookasideList+0x3c
ffffd001`577c6620 fffff802`84b0f378 : ffffe000`5d429810 ffffe000`5d429800 ffffe000`5d429adb ffffc001`f9c91da0 : vhdmp!VhdmpiCTFlushBuffersIOCompletion+0x18c
ffffd001`577c6690 fffff801`cb670130 : ffffe800`5eb64b00 00000000`00000001 ffffe800`5eb64bc8 ffffe000`5d429810 : nt!IopfCompleteRequest+0x588
ffffd001`577c67a0 fffff801`cb66ca58 : 00000000`00000000 ffffd001`577c6a40 ffffc002`01b57c30 00000000`00000048 : Ntfs!NtfsExtendedCompleteRequestInternal+0x150
ffffd001`577c67d0 fffff801`cb65ca89 : ffffe800`5eb64bc8 ffffd001`577c6a40 00000000`00000000 ffffe800`5eb64bc8 : Ntfs!NtfsCommonWrite+0x2e2d
ffffd001`577c6a00 fffff802`84ac3adb : fffff801`cb65d424 fffff801`cb65c860 ffffe800`5eb64bc8 ffffe800`5f705040 : Ntfs!NtfsFspDispatch+0x229
ffffd001`577c6b50 fffff802`84b3f794 : 00000000`00000000 ffffe800`5f705040 ffffe800`5f705040 ffffe000`57455900 : nt!ExpWorkerThread+0x293
ffffd001`577c6c00 fffff802`84bca5c6 : ffffd001`54600180 ffffe800`5f705040 ffffe800`5f74e540 00000000`00000246 : nt!PspSystemThreadStartup+0x58
ffffd001`577c6c60 00000000`00000000 : ffffd001`577c7000 ffffd001`577c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  vhdmp!ExFreeToNPagedLookasideList+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vhdmp

IMAGE_NAME:  vhdmp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52e848da

IMAGE_VERSION:  6.3.9600.16521

STACK_COMMAND:  .cxr 0xffffd001577c5bc0 ; kb

BUCKET_ID_FUNC_OFFSET:  3c

FAILURE_BUCKET_ID:  0x24_vhdmp!ExFreeToNPagedLookasideList

BUCKET_ID:  0x24_vhdmp!ExFreeToNPagedLookasideList

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x24_vhdmp!exfreetonpagedlookasidelist

FAILURE_ID_HASH:  {9c4ed974-e3f7-aed7-e34e-cf68671dc0ce}

Followup: MachineOwner
---------

18: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 000000b500190637
Arg2: ffffd001577c63b8
Arg3: ffffd001577c5bc0
Arg4: fffff801ccc12154

Debugging Details:
------------------


EXCEPTION_RECORD:  ffffd001577c63b8 -- (.exr 0xffffd001577c63b8)
ExceptionAddress: fffff801ccc12154 (vhdmp!ExFreeToNPagedLookasideList+0x000000000000003c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffd001577c5bc0 -- (.cxr 0xffffd001577c5bc0;r)
rax=000000000840542f rbx=ffffe8005b4df080 rcx=ffffe8005a81d220
rdx=ffffe8005a81d220 rsi=ffffe8005b4de000 rdi=ffffe8005a81d220
rip=fffff801ccc12154 rsp=ffffd001577c65f0 rbp=ffffd001577c6670
 r8=0000000000000001  r9=000000000000002f r10=fffff80284a065b0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000001
r14=ffffe8005c2d2440 r15=ffffe8005c2b94f0
iopl=0         nv up ei ng nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010292
vhdmp!ExFreeToNPagedLookasideList+0x3c:
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h] ds:002b:ffffe800`5b4df0b8=????????????????
Last set context:
rax=000000000840542f rbx=ffffe8005b4df080 rcx=ffffe8005a81d220
rdx=ffffe8005a81d220 rsi=ffffe8005b4de000 rdi=ffffe8005a81d220
rip=fffff801ccc12154 rsp=ffffd001577c65f0 rbp=ffffd001577c6670
 r8=0000000000000001  r9=000000000000002f r10=fffff80284a065b0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000001
r14=ffffe8005c2d2440 r15=ffffe8005c2b94f0
iopl=0         nv up ei ng nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010292
vhdmp!ExFreeToNPagedLookasideList+0x3c:
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h] ds:002b:ffffe800`5b4df0b8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff

FOLLOWUP_IP:
vhdmp!ExFreeToNPagedLookasideList+3c
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h]

FAULTING_IP:
vhdmp!ExFreeToNPagedLookasideList+3c
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h]

BUGCHECK_STR:  0x24

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffff801ccc3bd98 to fffff801ccc12154

STACK_TEXT:
ffffd001`577c65f0 fffff801`ccc3bd98 : ffffd001`577c6660 ffffe800`5b4de000 00000000`00000010 ffffc001`f9c91d00 : vhdmp!ExFreeToNPagedLookasideList+0x3c
ffffd001`577c6620 fffff802`84b0f378 : ffffe000`5d429810 ffffe000`5d429800 ffffe000`5d429adb ffffc001`f9c91da0 : vhdmp!VhdmpiCTFlushBuffersIOCompletion+0x18c
ffffd001`577c6690 fffff801`cb670130 : ffffe800`5eb64b00 00000000`00000001 ffffe800`5eb64bc8 ffffe000`5d429810 : nt!IopfCompleteRequest+0x588
ffffd001`577c67a0 fffff801`cb66ca58 : 00000000`00000000 ffffd001`577c6a40 ffffc002`01b57c30 00000000`00000048 : Ntfs!NtfsExtendedCompleteRequestInternal+0x150
ffffd001`577c67d0 fffff801`cb65ca89 : ffffe800`5eb64bc8 ffffd001`577c6a40 00000000`00000000 ffffe800`5eb64bc8 : Ntfs!NtfsCommonWrite+0x2e2d
ffffd001`577c6a00 fffff802`84ac3adb : fffff801`cb65d424 fffff801`cb65c860 ffffe800`5eb64bc8 ffffe800`5f705040 : Ntfs!NtfsFspDispatch+0x229
ffffd001`577c6b50 fffff802`84b3f794 : 00000000`00000000 ffffe800`5f705040 ffffe800`5f705040 ffffe000`57455900 : nt!ExpWorkerThread+0x293
ffffd001`577c6c00 fffff802`84bca5c6 : ffffd001`54600180 ffffe800`5f705040 ffffe800`5f74e540 00000000`00000246 : nt!PspSystemThreadStartup+0x58
ffffd001`577c6c60 00000000`00000000 : ffffd001`577c7000 ffffd001`577c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  vhdmp!ExFreeToNPagedLookasideList+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vhdmp

IMAGE_NAME:  vhdmp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52e848da

IMAGE_VERSION:  6.3.9600.16521

STACK_COMMAND:  .cxr 0xffffd001577c5bc0 ; kb

BUCKET_ID_FUNC_OFFSET:  3c

FAILURE_BUCKET_ID:  0x24_vhdmp!ExFreeToNPagedLookasideList

BUCKET_ID:  0x24_vhdmp!ExFreeToNPagedLookasideList

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x24_vhdmp!exfreetonpagedlookasidelist

FAILURE_ID_HASH:  {9c4ed974-e3f7-aed7-e34e-cf68671dc0ce}

Followup: MachineOwner
---------

18: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 000000b500190637
Arg2: ffffd001577c63b8
Arg3: ffffd001577c5bc0
Arg4: fffff801ccc12154

Debugging Details:
------------------


EXCEPTION_RECORD:  ffffd001577c63b8 -- (.exr 0xffffd001577c63b8)
ExceptionAddress: fffff801ccc12154 (vhdmp!ExFreeToNPagedLookasideList+0x000000000000003c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffd001577c5bc0 -- (.cxr 0xffffd001577c5bc0;r)
rax=000000000840542f rbx=ffffe8005b4df080 rcx=ffffe8005a81d220
rdx=ffffe8005a81d220 rsi=ffffe8005b4de000 rdi=ffffe8005a81d220
rip=fffff801ccc12154 rsp=ffffd001577c65f0 rbp=ffffd001577c6670
 r8=0000000000000001  r9=000000000000002f r10=fffff80284a065b0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000001
r14=ffffe8005c2d2440 r15=ffffe8005c2b94f0
iopl=0         nv up ei ng nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010292
vhdmp!ExFreeToNPagedLookasideList+0x3c:
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h] ds:002b:ffffe800`5b4df0b8=????????????????
Last set context:
rax=000000000840542f rbx=ffffe8005b4df080 rcx=ffffe8005a81d220
rdx=ffffe8005a81d220 rsi=ffffe8005b4de000 rdi=ffffe8005a81d220
rip=fffff801ccc12154 rsp=ffffd001577c65f0 rbp=ffffd001577c6670
 r8=0000000000000001  r9=000000000000002f r10=fffff80284a065b0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000001
r14=ffffe8005c2d2440 r15=ffffe8005c2b94f0
iopl=0         nv up ei ng nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010292
vhdmp!ExFreeToNPagedLookasideList+0x3c:
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h] ds:002b:ffffe800`5b4df0b8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff

FOLLOWUP_IP:
vhdmp!ExFreeToNPagedLookasideList+3c
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h]

FAULTING_IP:
vhdmp!ExFreeToNPagedLookasideList+3c
fffff801`ccc12154 ff5338          call    qword ptr [rbx+38h]

BUGCHECK_STR:  0x24

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffff801ccc3bd98 to fffff801ccc12154

STACK_TEXT:
ffffd001`577c65f0 fffff801`ccc3bd98 : ffffd001`577c6660 ffffe800`5b4de000 00000000`00000010 ffffc001`f9c91d00 : vhdmp!ExFreeToNPagedLookasideList+0x3c
ffffd001`577c6620 fffff802`84b0f378 : ffffe000`5d429810 ffffe000`5d429800 ffffe000`5d429adb ffffc001`f9c91da0 : vhdmp!VhdmpiCTFlushBuffersIOCompletion+0x18c
ffffd001`577c6690 fffff801`cb670130 : ffffe800`5eb64b00 00000000`00000001 ffffe800`5eb64bc8 ffffe000`5d429810 : nt!IopfCompleteRequest+0x588
ffffd001`577c67a0 fffff801`cb66ca58 : 00000000`00000000 ffffd001`577c6a40 ffffc002`01b57c30 00000000`00000048 : Ntfs!NtfsExtendedCompleteRequestInternal+0x150
ffffd001`577c67d0 fffff801`cb65ca89 : ffffe800`5eb64bc8 ffffd001`577c6a40 00000000`00000000 ffffe800`5eb64bc8 : Ntfs!NtfsCommonWrite+0x2e2d
ffffd001`577c6a00 fffff802`84ac3adb : fffff801`cb65d424 fffff801`cb65c860 ffffe800`5eb64bc8 ffffe800`5f705040 : Ntfs!NtfsFspDispatch+0x229
ffffd001`577c6b50 fffff802`84b3f794 : 00000000`00000000 ffffe800`5f705040 ffffe800`5f705040 ffffe000`57455900 : nt!ExpWorkerThread+0x293
ffffd001`577c6c00 fffff802`84bca5c6 : ffffd001`54600180 ffffe800`5f705040 ffffe800`5f74e540 00000000`00000246 : nt!PspSystemThreadStartup+0x58
ffffd001`577c6c60 00000000`00000000 : ffffd001`577c7000 ffffd001`577c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  vhdmp!ExFreeToNPagedLookasideList+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vhdmp

IMAGE_NAME:  vhdmp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52e848da

IMAGE_VERSION:  6.3.9600.16521

STACK_COMMAND:  .cxr 0xffffd001577c5bc0 ; kb

BUCKET_ID_FUNC_OFFSET:  3c

FAILURE_BUCKET_ID:  0x24_vhdmp!ExFreeToNPagedLookasideList

BUCKET_ID:  0x24_vhdmp!ExFreeToNPagedLookasideList

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x24_vhdmp!exfreetonpagedlookasidelist

FAILURE_ID_HASH:  {9c4ed974-e3f7-aed7-e34e-cf68671dc0ce}

Followup: MachineOwner
---------

18: kd> lmvm vhdmp
start             end                 module name
fffff801`ccc09000 fffff801`ccc98000   vhdmp      (pdb symbols)          c:\symbols\vhdmp.pdb\264A69A11D4744DDAE6F46BEFACB46EC1\vhdmp.pdb
    Loaded symbol image file: vhdmp.sys
    Mapped memory image file: c:\symbols\vhdmp.sys\52E848DA8f000\vhdmp.sys
    Image path: \SystemRoot\System32\drivers\vhdmp.sys
    Image name: vhdmp.sys
    Timestamp:        Wed Jan 29 01:18:34 2014 (52E848DA)
    CheckSum:         00092FA0
    ImageSize:        0008F000
    File version:     6.3.9600.16521
    Product version:  6.3.9600.16521
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     vhdmp.sys
    OriginalFilename: vhdmp.sys
    ProductVersion:   6.3.9600.16521
    FileVersion:      6.3.9600.16521 (winblue_gdr.140128-1545)
    FileDescription:  VHD Miniport Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Hi,

another post with more or less the same issue as numerous other posts, for example:

http://social.technet.microsoft.com/Forums/en-US/a09e56fc-f952-427d-8dc5-53fbd1c3ca38/live-migration-failed-while-quick-migration-is-ok?forum=winserverhyperv

http://social.technet.microsoft.com/Forums/sharepoint/en-US/822bb097-e7ff-47ac-ad83-c40174e7b441/live-migration-failed-while-quick-migration-is-okvirtual-machine-with-synthetic-fc-hba-?forum=winserverhyperv

http://social.technet.microsoft.com/Forums/scriptcenter/en-US/51ddfc57-4250-4553-9592-1702ad87c12a/live-migration-failed-using-virtual-hbas-and-guest-clustering?forum=winserverhyperv

Mentioned post were of no heklp though. In this setup I have 2 2012R2 Hyper-V boxes in a Failover Cluster and a HP MSA2040 SAN. Within this cluster I have 2 2012R2 guests that are also clustered. They have 2 Synthetic Fibre Channel Adapters, each one connected to another physical port on the host. Quick Migration works any time, Live Migration only once in a while. I get messages like:

'<GuestOS>' Synthetic FibreChannel Port: Failed to finish reserving resources with Error 'Unspecified error' (0x80004005). (Virtual machine ID 8AABB243-7333-4729-A060-120EF8E993A7)

Facts:

• Basic stuff like NPIV support is ofcourse enabled and all HBA's and switches support this;
• MPIO is setup accordingly to HP recommendations;
• The hosts have 2 fibre ports each connected to a seperate fibre switch;
• Guest VM's have 2 Fibre Adapters, each connected to a seperate Virtual SAN;
• Initially I had all WWPN's defined in one host on the SAN, as per a recemondation in one of the mentioned threads I split that up and made a seperate host on the switch for each WWPN set. As the switch only cares about WWPN / WWNN's rather than the aliases they are 'bound' to this did not help;
• Virtual SAN's are equally setup on the hosts, and each matching Virtual SAN is connected to the same Fibre Switch so physical pathing should be ok;
• Zoning is correct; all 4 wwpn's are added to zoning and can access the luns (if not it would not work 'sometimes');
• When I start the live migration, the 'not-active-WWPN-set' is immediately presented at the switches and the switches see the respective WWPN's as active. At that point all 4 WWPN's of the guest are active according to my switches. The switches also recognize these WWPN's as 'NPIV' WWPN's;
• When I stop the guest, and manually switch the addresses of set A and B over and start again, I see all my storage. This again to make sure zoning is ok and all storage is available on all 4 WWPN's;

Now the point of interest: The MSA2040 seems to be rather slow to recognize or 'discover' as HP calls it presented WWPN's. This is the same for physical hosts as well as virtual hosts. Sometimes it takes up to a minute or two before a host is actually discovered by the SAN. Then it presents the configured LUNs to it and that step again takes a while. I think this is the base issue here. When I do a live migration all 4 WWPN's are available but the storage only discovered 2 of them. At the sporadic times Live Migration DOES work, the SAN (ofcourse) discovered the WWPN's and as soon as the LUN's are presented to them, the migration immediately continues as expected.

The same happens when starting a guest with Synthetic Fibre Channel Adapters: Starting such VM immediately presents the WWPN's at switchlevel, then 'stalls' at 10% for about a minute and then continues booting. Sometimes the SAN discovers the WWPN's faster, and as soon as the LUN's are presented the booting continues and everything is ok. However most of the times the SAN is 'too slow' and after a timeout of a minute or so the VM continues booting. This results in the storage not being available in this guest until the SAN discovered the WWPN's.

The same happens with Quick Migration. With Quick Migration there is no requirement for the LUN's to be active and therefore it works. And again when the SAN is quick enough the storage is there immediately when the migration is done, when it's too slow the storage is not available after migration, until the SAN discovered the WWPN's again.

With Live Migration ofcourse there is a requirement that the LUNs are available to all 4 ports at time of migration. Unlike a quick-migration, Live Mgration will not continue when LUN's aren't available.

So I have 2 options here that I think would fix my issue:

• Have the SAN to pickup new presented hosts faster;
• Have Hyper-V to wait longer before a live migration times out.

The first is not an option, HP does not have any settings for this in the MSA2040 (and neither in the P2000 G3 which we have as backup as well in this setup).

So maybe we can increase the Hyper-V live-migration-wait-for-lun-timeout?

The concrete question:

Is there a regkey or something for increasing the 'waiting for storage' timeout on live-migration?

Ofcourse any other 'magical' solution to this issue is welcome :)

I'm setting up Hyper-V Replication between two Failover Clusters.
One Primary and the other our Disaster Recovery location.

I have been using guides and pretty much everything is clear to me, except the Replica Files part.
There is about zero information about this, except that a vague mention about setting it up.
But not where it should be or is allowed, or the storage size for it.

I found a capacity planner, but that crashed after half an hour or gathering information.
So that was useless.

Of course I can understand that the storage size of the location needs to be large enough to accomendate the replica files while replication. But can I use a CSV for this, or do I just configure one local disk per Failover Cluster node?
And is it used during the initial replication of a VM?

If the last one is "yes" then I will have a problem with a 4 to 5TB CSV for our fileserver...
I don't have that much space available on the SAN.

I really like some more information regarding this part.