I am running Windows Server 2012 R2 Essentials as a VM on Hyper-V Server 2012 R2 (server core).  In checking MSINFO32 I see "Secure Boot State" is "On" for Essentials, but given my current configuration I believe this should be "Off?"

I setup a new Hyper-V Server 2012 R2 (server core) using an Areca ARC-1224-8i RAID controller.  It was unclear to me whether or not the Areca RAID controller would support UEFI or not, but since Secure Boot was desirable I decided to try a UEFI installation. I created two volumes on the RAID controller.  C drive of 80 Gb and D drive of the remainder (about 9 Tb).  I checked the file C:\Windows\Panther\setupact.log and saw the message which told me this was an EFI installation/boot.

After Hyper-V was installed I then setup Essentials as a VM on the D drive.

When I ran MSINFO32 in both Hyper-V and Essentials and I saw the Secure Boot State was On which was expected (and desired) for both OS levels.

Several days later I started having problems.  The system seemed to have crashed and during multiple attempts to reboot the Hyper-V server couldn't seem to detect the RAID controller.  If I tried a new Hyper-V installation and loaded the RAID driver the RAID controller was seen, but when Hyper-V itself tried to boot it seemed as though the RAID driver was not being loaded and thus the RAID controller could not be found (and along with it my C boot drive was missing)?

Since I had some suspicion that the RAID controller might not support UEFI I decided to re-install Hyper-V, but this time using the Legacy BIOS.  After the installation was completed I again verified the setupact.log and saw BIOS rather than EFI (as expected).

I then re-attached my Essentials VM (which was left untouched on the D drive) and got everything running again.

But now when I check MSINFO32 within Hyper-V it showed Secure Boot State Off (expected given that UEFI was not used).  But when checking MSINFO32 within Essentials it showed Secure Boot State On.

I thought one purpose of Secure Boot was to create a chain of trust.  Given that Hyper-V can no longer verify this chain (since UEFI is not used) I would have expected any VM running above Hyper-V to be in the same state, i.e., Secure Boot State Off? When the underlying Hyper-V layer changed I would have expected that to change Essentials view of the world?  So it looks to me as though this is not being handled correctly?

Thanks for any assistance you can provide.

P.S.  In case this makes any difference I am using a motherboard with a TPM and both the C and D drives were encrypted with BitLocker.  The C drive used a TPM key and the D drive had a password and was setup to autounlock.

After I re-installed Hyper-V on the C drive I then manually entered the BitLocker password in order to access the Essentials VM on the D drive.

Theokrat

MARK D ROCKMAN

Hello

I got a Server 2012R2 Hyper-V Cluster with Windows 8.1 guests.

I there any chance to configure different IP address ranges for the Clients in the collections?

e.g.

Clients from collection A got addresses from .10 to .20

Clients from collection B got addresses from .21 to .30

Thanks for your answers

Hi,

I'm wondering, if SCOM is capable to monitor incoming & outgoing traffic (current and total over time) of VMs in Hyper-V?

Tried to search about it, and found only 3rd party tools or the monitoring is only available for Router, not VMs.

Thanks.

Okay..

First things first.

I have a virtual setup on a Windows Hyper-V Server 2012 R2 that i moved from a Windows Server 2008 R2 Enterprise.

It worked fine on my server 2008 R2 but after i transported it over to my hyper-V server and made the same configurations there it dosent seems to get online other then local.

I have checked the router and that one can ping 8.8.8.8 whit success.

The server it self is also online.

Does anybody have an idea for the solution?

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.

Hello,

I have an Windows 2008 Standard x64 machine. In "system event. log" appear every 10 minutes  events 1103 (source DHCP-client):

Log Name:      System
Source:        Microsoft-Windows-Dhcp-Client
Date:          ....
Event ID:      1103
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     

Description:
Your computer was successfully assigned an address from the network, and it can now connect to other computers.

Any thoughts on what could be causing this event to appear?

Thank in advance for your help.

Jazabra

I have a 2TB wd(western digital) branded harddisk , initially i was installed windows 7 , my friend gave me windows 8.1, so i planned to install windows 8.1 in the Hard disk , while installing i got an error "Cannot install with MBR partition ", so have to use diskpart command prompt ,i have converted the file system to GPT , !!! there comes the problem , i used the command 'clean', even which is not nesscary .,what happened is ,all the partitions in the hard disk got removed ,when i came to know that the hard disk is blank ,i become mad,

Then after two hours of research i found a software namely 'find and mount' which help me to scan the deleted partition and mount the recovered drives with my precious data ,even though it mount the drive we have only limted access to the drive ,we cant add files ,we cant write in the drives ,in the disk management the mounted drive will not be shown ,while rebooting it unmount etc.. ,i understand its a temporary process to take backup ,i need one more 2 TB hard disk to copy  my recovered drives , so what i did is ,i opened the diskmanager and format the unallocated drive ,i got a fresh 2TB ,and i copied those files from the temporaly mounted drive files to my real time drive .

now my doubt is ,

 Still the copying process is not end ,if i supossed to get all the missed drives with files from the temporary drives ,still the 'Find and mmount ' software shows the old files . if so my drive might be holding 4TB of data ,but the harddisk is only 2TB.What happens to the lost data after taking backup or overwritten with new data .

Hi friends!!

I am new here... i don't know how to post a article here...

I am just asking can i install Android on my Hyper-V like that virtual box.

if yes then please tell me the step-by-step process to install the same.

i have installed it at my Virtual box but as i most of using Hyper-V i want to install on it.

Please help me in this regard..

Thanks in advance.. :-)

Hi,

I had HyperV replication for a few virtual machines sucsesfully installed and up and running.

i configured port 443 for the replication and i use self signed certificates.

suddenly a few weeks ago the replication stopped with an error. I did find out that port 443 is not listening anymore on the replication server with the error. Even a port scan to the localhost replies with 'filtered'.

A port scan of port 443 on an other HyperV replication server is sucsesful

So my question : why is port 443 not responding ? what services are responsable for the hyperv replication ?

Thx

Koen

Hoping the community can help...

I was in the middle of moving a couple of Hyper-V 2012 VMs this afternoon using the standard move operation on the source server (I've done this a bunch of times with no issues, except today).  While moving the VMs, a drive failure occurred in my destination server.  I have since repaired the destination server and am ready to move the VMs as I attempted to do earlier.

Now when I try to move any of the servers I was trying to move earlier (running or not), I get a messagebox that contains the following:

"The move operation completed, but Hyper-V could not delete a temporary version of this virtual machine that was created on the destination computer."

After digging through some logs, I also found this:

Virtual machine migration operation for 'VMname here" failed at migration destination 'destination host here'

I've done some other digging through the programdata folder and others but am still at a loss.  I'm hoping someone out there has some thoughts for me.

Thanks!

Hi, am running Win 8.1 and Win2012R2 as VMs on a Win2012R2 Hyper-V host. Unfortunately, thetext and some app graphics quality is lower on the VM whether we use direct Hyper-V Connection, or Remote Desktop (with LAN and full experience set).

A dedicated (NVIDIA 310 NVS) graphics card is pumping out the vid to the monitor and both monitor and display adapter Device Drivers are set and showing their named drivers on the Host, great - howeveron any VM, the Monitor shows "Generic Non-PnP Monitor" and the Display Adapter is set to "Microsoft Hyper-V Video".

Surely, it should pick up the proprietary drivers from the Host, as I've made sure the Integration Services are installed and updated on the guest VMs. Maybe it doesn't and these generic names are just standard tags in VMs, but the text and graphics is definitely lower quality, which is a pain to work on, especially in 1920 x 1200 which I believe should be fine since Win2008 Hyper-V.

Am I missing something? TIA,

Phil

I am trying to perform a reverse replication after an unplanned failover in a lab environment. I receive the following two errors:

Event ID 32086

davidh

I have been running into an interesting but an alarming issue with virtual switches. I have recently built a 4 node Server 2012 Hyper-V failover cluster. I have built numerous 2008R2 and 2012 Hyper-V clusters before, so I am pretty familiar with the process. I have rebuilt my VMM due to software problems, and on this new cluster, I have configured the virtual switches with nic teaming on 2 of the virtual switches.

I have 4 clusters being managed by this VMM.. and this newly built cluster keeps losing all of the VMM virtual switch configurations, meaning if I go to properties on the problem host and click on virtual switches, its blank. Refresh host cluster flags all virtual machines in this cluster as "Unsupported Configuration," making the vm unmanageable via VMM. 

All virtual servers on that host still has connectivity, as all virtual switch configs are normal when looking at it with Hyper-V Manager or Failover Cluster Manager..

The workaround is to evacuate the host using Failover Cluster Manager and reboot the host. Then refresh the host. Then refresh the VM's. I cannot consider this a 'workaround' as I cannot be rebooting my hyper-V hosts every week.. and migrating virtual servers constantly just for this reason. (DPM backups have a FIT with csv's if it tries to backup a vm on a same csv as another vm thats being migrated.)

I have been wrestling with this problem for a few weeks now. The cluster has been slicked and completely rebuilt.. Still same problems. Has ANYONE else out there seen this issue? Does ANYONE out there suggest a way to go about further troubleshooting this issue? 

Hello-

I am having an issue with one of my VM's and my setup is like this. I have a physical server running 2008-R2 that is hosting two Virtual Servers through Hyper-V. One of the VM's is a very important server as it handles a lot of our budgeting stuff. The Admin before me depended on primarily Snapshots as a form of backup. I have always known that to not be a smart move and to not run on a snapshot in a production environment for more than 2 days. So we had a lot of snapshots from different times throughout this year and some from last year and the issue we have been running into is the VM has ran out of space and halted. So the past few weeks I have been removing some obsolete snapshots from the VM as to recover space to keep the server going. However currently I am down to the current running instance and two previous snapshots and as of yesterday I still had 35GB left. Today however when I logged on i noticed that i was down to 29GB left? This was confusing as I hadnt created any more snapshots and nothing had been added to the system to take up 6GB within a 24 hour period. So after doing some looking I noticed that the AVHD files (Snapshot Files) are growing in size? If they are snapshots why are they increasing in size? I would understand the .VHD (Current Running Disk) to be growing as we use it but not sure why snapshots are growing as well. 

So what I would like to do and get confirmation on is fix this, and the solution I have come up with would be to create a brand new VM, export and copy the VHD and AVHD'S to this new "non-snapshotted" system in hopes that the avhd's would merge into one VHD. Which would give me all my space back and let me work off the VHD without any loss of data or days of work. and then moving forward using snapshot only when needed and not as a form of backup. I just need someone to help make sure this is a good option to fix this server that is running out of space due to these AVHD's growing drastically day by day. 

Please someone 

I Thank You

-K

Hi

Hyperv virtual switch manager always change from external to private intermittently, why?

when I open the virtual switch manager, the "external" just grey out.

Windows 2012 R2, NIC firmware upgraded still same.   NIC processor is Broadcom.

thanks

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?

I have created two NIC teaming, one for a 147 subnet and one for a 192 subnet,

And used these two teaming in a Hyper-V virtual switch

But when I disable one of the NIC in the 147 team, some VM will loss connection,

It seems to me that the VM originally using the disabled NIC cannot failover to the remaining active NIC.

Anyone have any idea about what might be wrong? Thank you very much.