Hi All!

we are using hyper-v 2012 ending up with low space after deleted checkpoint. How to manually merge the AVHDXs to VHDX?

Please guide.

Product: windows server 2012 R2

Regards,

Gopal

AIO

 WIn2012R2 Standard + Hyper-V

We found out a VM that seems to be re-configured and maybe it had got back in time, maybe applying an old snaphost

Developers are complaining about a theorical time machine effect, where someone had applied a old snapshot

I couldn´t find any event log proofing that.

 i´ve created a TEST VM, created a snapshot, merged/deleted the snapshot and the event viewer has shown the event id related to the merging proccess

BUT...

i´ve created a TEST2 VM, created snapshot and APPLIED  the snapshot (going back in time) and.. no event ID logged, no trace of the operation.

It is right?

All Hyper-V advanced logs are enabled in event viewer (and i see  the merge) but i see the applying of the snapshot

wich event id would appear in applying snapshot?

Why is that?

There something elese to do enable more logs?

This is by design?

Floyd Kershner, PMP MCSE

Hello Community

    On WS2012 I have created a disk image of a hard drive so that if
anything happens to the hard drive I can just put it back the way
it was when there were no problems with the drive.

    The question is can that same disk image be used  by Hyper-V
to create a VM?

    Thank you
    Shabeaut

Am new to hyper-v. I was trying to installing linux redhat but the screen frozen out. I didnt reach the options to select language. The was creen become frozen as if its painted with colors.

please help

Hi,

I am trying to build a script to run in an isolated VM machine with no network access (Connected to close switch inside the Hyper-v).

In VMware there is an easy whey to do it with "Invoke-VMScript" command in power CLI. Didn't fond any whey to do it in Powershell for Hyper-v.

See example for VMware Power CLI:

Invoke-VMScript "ping Server1" -vm server -HostUser User -HostPassword Pass -GuestUser User2 -Pass2 -ScriptType "bat"

Thanks

Erez

Vladimir Shipitsyn

Hi there, 

When creating new virtual machines on Hyper-V (on Windows Server 2012 R2 host), each virtual machine is assigned 1 virtual processor by default. There is no Virtual Processor Configuration during the creation process, and this number can only be changedafterwards by going in to the the Settings of the virtual machine.

The servers that we are installing have quad core processors, and have multithreading enabled, giving a total of 8 logical processors. We run Windows Server 2012 R2 Standard, so we normally create two virtual machines on each host. Do I need to edit the virtual machines and assign more virtual processors to each virtual machine? 

I successfully passed the 74-409 Server Virtualisation exam last December and there was no mention of virtual processors at all.

regards, 
J

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?

All,

I am tasked with developing a solution for a test automation solution on a Hyper-V platform.  The automated tests require the ability to to run tests that interact with the desktop of the VM.  These tests will run as part of the nightly build and deployment and as such there will not be individuals present to unlock/tend to the VM's.  My intent is to establish a VMConnect 'host' that will run some type of script on startup to launch VMConnect sessions to X number of VM's, login to a domain account and be ready to run these UI based automated tests.

Does anyone know this if this is possible with VMConnect or is this something that would need to be implemented via group policy on the VM's?  

Also, slightly off topic but I am having difficulties making a VMConnect connection when running via command line, running the app manually works great but when I run via command line I get this:

Hyper-V cannot find a virtual machine with the name '<machinename>'.  Verify that your user account has permission to access virtual machines.  Or use Run as Administrator and try again.

I've tried running from an administrator command prompt and using the runas command with the same results.

Any ideas?

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.

I had a laptop die and I wanted to preserve the OS drive as a VM, so I created a VM in Hyper-V in Windows 8.1x64 and attached the physical drive and booted successfully.  I then defragged and zero'd out free space on the physical drive from within the VM and shut it down.  Next, I used Disk2vhd v2.01 to convert the physical disk to my vhdx file, which resulted in approximately 34 GB and is a dynamic vhdx file.  So far, success.

Now the problem; I want to convert this vhdx from dynamic to a fixed vhdx, of approx. 40 GB.  When I boot up the current dynamic vhdx and attempt to shrink the volume in disk management, it tells me there is not enough free space to complete the operation. The physical disk was 320 GB, and within the running VM it still shows as a 298 GB volume, the same as the physical disk did.  I also tried converting the 34 GB dynamic vhdx file to a fixed vhdx from within the Hyper-V GUI, but it did not prompt me for a fixed size and the result was a vhdx file 298 GB in size!

Worth noting, the original physical drive has since been secure erased and had it's platter drilled for disposal, so starting from there is not an option.  Moving forward, I only have the 34 GB dynamic vhdx and the 298 GB fixed vhdx files to work with, however at this point I am not sure how to proceed to accomplish my goal.  Any assistance with this issue would be greatly appreciated.

Hi

we have windows Server 2012 r2 Hyper V failover Cluster..  we face slow network performance issue in widows 2012 R2

terminal Services .. VMQ is disable on Physical NIC of Hyper V Network.

Remaining Servers are working perfectly only issue face on terminal user login on terminal server node..

Any idea 

I'm trying to set up Hyper-V Replica between two Windows 2012 R2 hosts.   They are not part of a domain, but they do belong to the same workgroup.

On the secondary host, I enabled it as a Replica server and selected Kerberos for the authentication mode.  I also selected "Allow replication from any authenticated server".  I then ran the Enable Replication wizard on the primary server and went through the wizard.  After clicking Finish, I get a "Enabling replication failed" error dialog with this message:

     Hyper-V failed to enable replication.

     Hyper-V failed to authenticate using Kerberos authentication.

     Hyper-V failed to enable replication for virtual machine 'xxx': No credentials are available in the security package (0x8009030E).

    Hyper-V failed to authenticate the Replication server YYY using Kerberos authentication.  Error: No credentials are available in the security package (0x8009030E).

The one post I found that talked about this issue in a workgroup environment, http://www.chicagotech.net/win8&2012/replicaissue1.htm, suggested making sure that Everyone and Authenticated Users have permission to "Access this computer from the network" in local policies.  Did that on both machine and that didn't help.

Does anyone have any other suggestions?

Thanks,

Richard

I have a Lenovo Yoga2 Pro running build 10074. I can't enable Hyper-V and need it for some Visual Studio Phone development. It allows me to add that feature, and "configures" windows, reboots, says it is finishing, gets to 95% and fails. Then it backs out the changes, reboots and I am back where I started.

I do have Hyper-V working on my desktop also running 10074 and it works fine with Visual Studio 2013. I also have virtualization enabled on the Yoga2, and had this working on an earlier build. The upgrade to 10074 did fail and I was forced to use the recovery disk to do a "clean" install of 10074.

Any pointers would be greatly appreciated.

I have been trying to upgrade our windows server 2012 installation that is running hyper-v, but have a problem with the physical nic. The issue is that upon finalising the upgrade, WinSer2012R2 presents a BSOD (IRQL_NOT_LESS_OR_EQUAL) and the only hardware device I cannot remove prior to the upgrade is the NIC so I assume this is giving me the grief.

I have tried to remove the NIC driver, but Hyper-V depends on it (all vPcs depend on it as well as a logical switch).

How can I remove the physical NIC? Is my only option to reconfigure all vPcs to have no NIC and delete the logical switches? This is a lot of work to reconfigure and error prone as well.

I would have checked log files for the boot, but for some reason, WinSer2012R2 does not create any log entries or memory dumps for me to look at. So all I have is the above mentioned BSOD hint.

Suggestions?

I have hyper v 2012 / hyperv 2008 core running in rack server. I wanted to verify whether the server is in RAID or not. How do i check that?

Sathishkumar M

I've recently replaced a PERC H310 RAID controller with a PERC H710p RAID controller on a Dell PowerEdge R820 running Windows Server 2012 R2 and started experiencing this problem. Everything I've investigated so far doesn't point to this being the issue, but wanted to mention it in case someone encountered something similar.

We were having terrible disk performance until the RAID card was swapped out, and as a precaution I moved all existing VMs off of this Hyper-V host server. Once everything was back up and running, I began a live migration back to the affected host server and it blue screened. Tried again and same result. I then tried copying the VM images manually through a UNC share and hit the same problem. It doesn't always happen at the same time during the copy. I've had blue screens happen 4-5 GB into a transfer, and 200 GB into a transfer.

I've updated the RAID controller driver and firmware to the latest available from Dell, and have installed the latest BIOS and chipset driver. The server has Broadcom 5720 series NICs, updated with the latest drivers and firmware provided by Dell. All Windows/Microsoft updates have been applied.

After all these firmware/driver updates the blue screens still kept occurring during network transfers. All the minidumps show a 0x133 DPC_watchdog_violation error, where the DPC time allotment is 500 ticks and the blue screens happening at 501 ticks. Running the minidumps through Windows Debugger pointed to tcpip.sys, netio.sys, and vmswitch.sys initially. Since tcpip.sys and netio.sys aren't typically the issue, I looked around for anything related to vmswitch.sys being the problem.

I disabled the Hyper-V vSwitch in the OS and did a transfer 100% successfully, with the traffic running through the same NIC the vSwitch was configured to use. Once I re-enabled the vSwitch and transferred more files......the blue screen came back.

In researching, I found reports of this issue when a Hyper-V host was using NIC Teaming. We don't have any of the NICs on this server teamed, but I figured it wouldn't hurt to apply the latest hotfix that addressed the issue.3031598 - even after applying it I was getting more bluescreens. I couldn't find a way to use the updated vmswitch.sys that came with the hotfix (6.3.9600.17714); I tried deleting and recreating the vSwitch, but the old driver (6.3.9600.16384) is what gets applied and searching the OS for an updated driver doesn't turn up anything. I also can't find any info online about manually updating the driver after applying a hotfix.

I'm fairly certain vmswitch.sys is the issue, but I don't know where to go from here. Are there any NIC or vSwitch settings I can adjust to help with this? Has anyone encountered a similar issue? Can anyone lend a hand in diagnosing this issue? I found some good resources on debugging and troubleshooting this issue further (2 URLs below), but this has gone from "this is a good learning experience" to "this needs to get done" in the few weeks I've been troubleshooting.

http://blogs.msdn.com/b/ntdebugging/archive/2012/12/07/determining-the-source-of-bug-check-0x133-dpc-watchdog-violation-errors-on-windows-server-2012.aspx

http://blogs.msdn.com/b/ntdebugging/archive/2009/12/11/test.aspx

All the minidump's from every time this has happened can be viewed here: http://1drv.ms/1R6CfAO.

Here are all the suspects from those minidumps: