Hyper-V Server 2012 - Does Not Allow for Secure Boot?

July 22, 2013, 10:22 pm

Hyper-V Server 2012 (server core) does not appear to support Secure Boot? Is this true?

Various webpages imply that Windows Server 2012 (and Windows 8) both support Secure Boot which would imply Secure Boot ought to also work on Hyper-V Server 2012? (I was unable to locate any definitive answer to that question.)

I am using an Intel DQ77MK motherboard. I am able to successfully install Hyper-V Server 2012 using UEFI. (I confirmed UEFI by opening C:\windows\panther\setupact.log and looking for "Detected boot environment: EFI.")

But if I setup the motherboard BIOS to enable SecureBoot, prior to re-installing Hyper-V Server 2012, I don't get anything on my screen. It is unclear if the system hung, but I don't get any error message and am unable to install the OS. So there seems to be some compatibility problem between enabling Secure Boot and Hyper-V Server 2012? (In case you're wondering. I have the latest Intel BIOS installed on my motherboard.)

In doing some research I came across the Powershell command - Get-SecureBootPolicy

But when I try and execute that command on Hyper-V Server 2012 I get the following error message -

The term 'Get-SecureBootPolicy' is not recognized as the name of a cmdlet, function, script file, or operable program.

I came across the get-module command. I noticed different results on my Windows 8 PC -

PS C:\> get-module

ModuleType Name ExportedCommands
---------- ---- ----------------
Manifest Microsoft.PowerShell.Utility {Add-Member, Add-Type, Clear-...
Binary SecureBoot {Confirm-SecureBootUEFI, Form...

versus my Hyper-V Server 2012

PS C:\> get-module

ModuleType Name ExportedCommands
---------- ---- ----------------
Manifest Microsoft.PowerShell.Management {Add-Computer, Add-Content, C...
Manifest Microsoft.PowerShell.Utility {Add-Member, Add-Type, Clear-...

It looked as though I might need to install something in order to get Get-SecureBootPolicy to run on Hyper-V Server 2012? I tried running Import-Module SecureBoot but got this error message -

The specified module 'SecureBoot' was not loaded because no valid module file was found in any module directory.

So unless a different module name is required there does not appear to be any way for me to install the cmdlet on Hyper-V Server 2012?

The list of PowerShell 3 Cmdlets, as found here -

http://social.technet.microsoft.com/wiki/contents/articles/4694.powershell-3-cmdlets.aspx?Sort=MostRecent&PageIndex=1

looked as though it ought to be possible to perform a UEFI install and then setup the BIOS to enable Secure Boot. I had trouble getting the system to boot, but after several attempts I finally got it to come up. But given none of the other cmdlets I tried worked I cannot tell if Secure Boot is really enabled. I thought that after several failed boot attempts perhaps the BIOS reverted/regressed some configuration that allowed me to boot the system, but which effectively disabled Secure Boot?

All of which leads me to believe that Hyper-V Server 2012 (server core) does not support Secure Boot?

Thanks for any insight you can provide.

Theokrat

↧

Hyper-V servers

July 22, 2013, 6:36 am

≫ Next: Windows Server 2012 BSOD caused by vmswitch.sys

≪ Previous: Hyper-V Server 2012 - Does Not Allow for Secure Boot?

Hi,

Is there a way to list all hyper-v servers (physical machines which are running hyper-v) from powershell? There is a way when all servers have at least one VM but what to do with does that do not have any?

Thanks.

↧

Windows Server 2012 BSOD caused by vmswitch.sys

July 22, 2013, 3:12 am

≫ Next: Advice for Home Hyper-V 2012

≪ Previous: Hyper-V servers

Hello guys,

Situation is the following. I have 2 Windows Server 2012 with Hyper-V installed. We have approximately 10 VMs on each server and these VMs are replicating in both directions.

We had 2 NICs in teaming (switch independent) connected to 1 switch. Interfaces are in access mode.

On Friday evening we added another switch, where we connected the other 2 NICs of each server, so we decrease the load from the 1st switch. We added these NICs to the team. The switches are connected by trunk port.

Today (Monday) at around 11am (maybe higher network load), both servers got BSOD with 3 minutes difference. One at 11:02, the other at 11:05.

On both servers the cause is listed as vmswitch.sys. I did not find any info on this happening in Google. Here is the output from WinDBG:

Server1

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\pavel.dokov\Desktop\темп\MEMORY92.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\TEMP*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff802`96a08000 PsLoadedModuleList = 0xfffff802`96cd4a20
Debug session time: Mon Jul 22 11:05:42.903 2013 (UTC + 3:00)
System Uptime: 5 days 2:15:02.785
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols

Loading unloaded module list
.......
*******************************************************************************
*    *
* Bugcheck Analysis *
*    *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e0d, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for bxnd60a.sys
*** ERROR: Module load completed but symbols could not be loaded for bxvbda.sys
Probably caused by : vmswitch.sys ( vmswitch!VmsPtNicPvtPacketRouted+ae )

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

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

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e0d, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

TAG_NOT_DEFINED_c000000f: FFFFF8029720DFB0

LAST_CONTROL_TRANSFER: from fffff80296be1fa3 to fffff80296a62440

STACK_TEXT:
fffff802`9720cb48 fffff802`96be1fa3 : 00000000`00000133 00000000`00000001 00000000`00001e0d 00000000`00000000 : nt!KeBugCheckEx
fffff802`9720cb50 fffff802`96aa6774 : fffffa80`15bee070 00000000`01ae7950 fffff802`9720ccd0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x14600
fffff802`9720cbd0 fffff802`97176eca : fffffa80`16f35d20 fffffa80`1812d000 00000008`00000001 00000000`00000197 : nt!KeUpdateTime+0x2ec
fffff802`9720cdb0 fffff802`96a5b01e : 00000400`b1b3ba59 fffffa80`18e38a88 fffff802`971a0580 fffffa80`177c0950 : hal!HalpTimerClockInterrupt+0x86
fffff802`9720cde0 fffff880`0501694e : fffffa80`21773c58 fffffa80`16c96280 fffff802`ffffffff 00000000`624e7356 : nt!KiInterruptDispatchLBControl+0x1ce
fffff802`9720cf70 fffff880`05016487 : fffffa80`169edd20 fffff802`97200001 fffffa80`169edd20 fffffa80`181ff740 : vmswitch!VmsPtNicPvtPacketRouted+0xae
fffff802`9720cfe0 fffff880`050153e7 : ffffffff`00000000 00000000`00000000 fffffa80`16d083f0 fffff802`9720d020 : vmswitch!VmsExtIoPacketRouted+0x197
fffff802`9720d070 fffff880`050190f4 : fffffa80`1812d000 00000000`00000000 fffffa80`13103001 fffffa80`16bfe8a0 : vmswitch!VmsRouterDeliverNetBufferLists+0x2b7
fffff802`9720d160 fffff880`05013a69 : fffffa80`00000000 fffffa80`13103000 00000000`00000000 0000ffff`ffffffff : vmswitch!VmsExtMppIndicatePackets+0x34
fffff802`9720d1a0 fffff880`05013652 : fffffa80`13103000 fffffa80`13103000 00000000`00000001 a8c06200`00000001 : vmswitch!VmsExtMpRoutePackets+0x339
fffff802`9720d300 fffff880`05012fef : fffff802`9720d340 fffffa80`16d00001 00000000`00000000 00000000`00000000 : vmswitch!VmsExtPtRouteNetBufferLists+0x272
fffff802`9720d3d0 fffff880`014dcb06 : 0001ff00`00000000 00000000`00000000 00000000`00000001 00000000`000001ff : vmswitch!VmsPtNicReceiveNetBufferLists+0x34f
fffff802`9720d490 fffff880`014dc605 : fffffa80`181fd002 fffffa80`169edd20 fffffa80`130972c0 00000000`000001ff : NDIS!ndisMIndicateNetBufferListsToOpen+0x126
fffff802`9720d540 fffff880`014dc843 : 00000000`00000000 00000000`00000001 00000000`000001ff 00000000`00000000 : NDIS!ndisInvokeNextReceiveHandler+0x6f5
fffff802`9720d610 fffff880`05366695 : 00000000`00000000 00000000`00000000 fffffa80`177e9000 fffffa80`169edd20 : NDIS!NdisMIndicateReceiveNetBufferLists+0xd3
fffff802`9720d6c0 fffff880`05366161 : fffffa80`1786e880 fffffa80`177e9000 00000000`00000001 fffff802`000001ff : NdisImPlatform!implatTryToIndicateReceiveNBLs+0x1a1
fffff802`9720d730 fffff880`014dcb06 : 00000001`ff01ffff 00000000`00000000 fffffa80`169edd20 ffff3e07`000001ff : NdisImPlatform!implatReceiveNetBufferLists+0x1a9
fffff802`9720d7b0 fffff880`014dc5c9 : fffffa80`12a9d002 fffff880`00000000 fffffa80`13097008 fffff880`000001ff : NDIS!ndisMIndicateNetBufferListsToOpen+0x126
fffff802`9720d860 fffff880`014dc843 : fffffa80`16d083f0 00000000`00001001 00000000`000001ff 00000000`00000008 : NDIS!ndisInvokeNextReceiveHandler+0x6b9
fffff802`9720d930 fffff880`051974c3 : 00000000`00000030 fffffa80`16d083f0 00000000`000001ff fffffa80`16d08550 : NDIS!NdisMIndicateReceiveNetBufferLists+0xd3
fffff802`9720d9e0 fffff880`05197a3b : fffff802`9720db30 fffffa80`15bf4070 00000003`00001001 fffffa80`127d3160 : bxnd60a+0x154c3
fffff802`9720da60 fffff880`00a9319a : fffffa80`12a9d010 00000000`00000000 00000000`00000000 00000000`000001ff : bxnd60a+0x15a3b
fffff802`9720db00 fffff880`00a9573c : fffff802`9720dc58 00000000`00000000 fffffa80`12a9d010 00000000`00000001 : bxvbda+0xb19a
fffff802`9720db90 fffff880`00a9829e : fffffa80`12a9d010 fffff802`9720dc70 fffffa80`12a9d680 fffff880`010cfbf1 : bxvbda+0xd73c
fffff802`9720dc10 fffff880`00a9974f : fffffa80`12a9d010 00000000`00000000 00000000`00010000 00000000`00000000 : bxvbda+0x1029e
fffff802`9720dca0 fffff880`00a98a79 : fffffa80`12a9d010 00000400`b1b158fa 00000000`00000000 00000000`00000000 : bxvbda+0x1174f
fffff802`9720dcd0 fffff802`96a8aca1 : fffff802`96d02f00 fffff802`9720de00 fffffa80`12ab6d90 fffff880`01e12da8 : bxvbda+0x10a79
fffff802`9720dd00 fffff802`96a8a8e0 : fffff802`96d00180 00000400`20fd9641 fffffa80`185e1080 00000000`00000025 : nt!KiExecuteAllDpcs+0x191
fffff802`9720de40 fffff802`96a5c3a5 : 00000000`00000000 fffff802`96d00180 fffff880`016bfb00 fffff880`035abb40 : nt!KiRetireDpcList+0xd0
fffff802`9720dfb0 fffff802`96a5c1a9 : 0000057f`ed2551c8 fffff802`96b4bf81 00000000`00000010 00000000`00000282 : nt!KxRetireDpcList+0x5
fffff880`016bfa40 fffff802`96b4bf95 : fffff802`971926a0 fffff802`96a5ad13 fffffa80`1c6be8c0 fffffa80`1d749c01 : nt!KiDispatchInterruptContinue
fffff880`016bfa70 fffff802`96a5ad13 : fffffa80`1c6be8c0 fffffa80`1d749c01 00000000`00000000 00001f80`00400010 : nt!KiDpcInterruptBypass+0x25
fffff880`016bfa80 fffff880`0501005d : 00000000`00000001 fffffa80`1aa70690 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x273
fffff880`016bfc10 fffff880`00bdc916 : fffffa80`19f1a9c0 00000000`00000001 fffffa80`1c6be910 fffffa80`19f1a600 : vmswitch!VmsVmNicPvtKmclPacketSent+0x4d
fffff880`016bfc40 fffff880`00bdb873 : fffffa80`1aa5c0d0 fffff802`96a37b00 fffffa80`19f1a601 fffff880`016bfd20 : vmbkmcl!InpProcessQueue+0x236
fffff880`016bfcd0 fffff880`0107807f : fffffa80`19f1a600 fffffa80`1342d800 fffffa80`1cf8ca10 fffffa80`1cf8ca10 : vmbkmcl!InpProcessingWorkerRoutine+0x1b3
fffff880`016bfd20 fffff802`96a34fd9 : fffffa80`133d2780 00000000`00000080 fffff880`01084110 fffff802`96d5a880 : vmbusr!WPP_SF_+0xffffffff`ffffffef
fffff880`016bfd50 fffff802`96ae97e6 : fffff802`96d00180 fffffa80`133d2780 fffff802`96d5a880 fffffa80`12833980 : nt!PspSystemThreadStartup+0x59
fffff880`016bfda0 00000000`00000000 : fffff880`016c0000 fffff880`016ba000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
vmswitch!VmsPtNicPvtPacketRouted+ae
fffff880`0501694e 49897108 mov qword ptr [r9+8],rsi

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: vmswitch!VmsPtNicPvtPacketRouted+ae

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: vmswitch

IMAGE_NAME: vmswitch.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 510cbec2

BUCKET_ID_FUNC_OFFSET: ae

FAILURE_BUCKET_ID: 0x133_ISR_vmswitch!VmsPtNicPvtPacketRouted

BUCKET_ID: 0x133_ISR_vmswitch!VmsPtNicPvtPacketRouted

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

0: kd> lmvm vmswitch
start end module name
fffff880`0500f000 fffff880`050a0000 vmswitch (private pdb symbols) c:\temp\vmswitch.pdb\C3BB001449F5486880C49B8C87592D831\vmswitch.pdb
Loaded symbol image file: vmswitch.sys
Image path: \SystemRoot\system32\DRIVERS\vmswitch.sys
Image name: vmswitch.sys
Timestamp: Sat Feb 02 09:22:42 2013 (510CBEC2)
CheckSum: 0008C7E0
ImageSize: 00091000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> .bugcheck
Bugcheck code 00000133
Arguments 00000000`00000001 00000000`00001e0d 00000000`00000000 00000000`00000000
0: kd> l
^ Syntax error in 'l'
0: kd> k
Child-SP RetAddr Call Site
fffff802`9720cb48 fffff802`96be1fa3 nt!KeBugCheckEx
fffff802`9720cb50 fffff802`96aa6774 nt! ?? ::FNODOBFM::`string'+0x14600
fffff802`9720cbd0 fffff802`97176eca nt!KeUpdateTime+0x2ec
fffff802`9720cdb0 fffff802`96a5b01e hal!HalpTimerClockInterrupt+0x86
fffff802`9720cde0 fffff880`0501694e nt!KiInterruptDispatchLBControl+0x1ce
fffff802`9720cf70 fffff880`05016487 vmswitch!VmsPtNicPvtPacketRouted+0xae
fffff802`9720cfe0 fffff880`050153e7 vmswitch!VmsExtIoPacketRouted+0x197
fffff802`9720d070 fffff880`050190f4 vmswitch!VmsRouterDeliverNetBufferLists+0x2b7
fffff802`9720d160 fffff880`05013a69 vmswitch!VmsExtMppIndicatePackets+0x34
fffff802`9720d1a0 fffff880`05013652 vmswitch!VmsExtMpRoutePackets+0x339
fffff802`9720d300 fffff880`05012fef vmswitch!VmsExtPtRouteNetBufferLists+0x272
fffff802`9720d3d0 fffff880`014dcb06 vmswitch!VmsPtNicReceiveNetBufferLists+0x34f
fffff802`9720d490 fffff880`014dc605 NDIS!ndisMIndicateNetBufferListsToOpen+0x126
fffff802`9720d540 fffff880`014dc843 NDIS!ndisInvokeNextReceiveHandler+0x6f5
fffff802`9720d610 fffff880`05366695 NDIS!NdisMIndicateReceiveNetBufferLists+0xd3
fffff802`9720d6c0 fffff880`05366161 NdisImPlatform!implatTryToIndicateReceiveNBLs+0x1a1
fffff802`9720d730 fffff880`014dcb06 NdisImPlatform!implatReceiveNetBufferLists+0x1a9
fffff802`9720d7b0 fffff880`014dc5c9 NDIS!ndisMIndicateNetBufferListsToOpen+0x126
fffff802`9720d860 fffff880`014dc843 NDIS!ndisInvokeNextReceiveHandler+0x6b9
fffff802`9720d930 fffff880`051974c3 NDIS!NdisMIndicateReceiveNetBufferLists+0xd3
fffff802`9720d9e0 fffff880`05197a3b bxnd60a+0x154c3
fffff802`9720da60 fffff880`00a9319a bxnd60a+0x15a3b
fffff802`9720db00 fffff880`00a9573c bxvbda+0xb19a
fffff802`9720db90 fffff880`00a9829e bxvbda+0xd73c
fffff802`9720dc10 fffff880`00a9974f bxvbda+0x1029e
fffff802`9720dca0 fffff880`00a98a79 bxvbda+0x1174f
fffff802`9720dcd0 fffff802`96a8aca1 bxvbda+0x10a79
fffff802`9720dd00 fffff802`96a8a8e0 nt!KiExecuteAllDpcs+0x191
fffff802`9720de40 fffff802`96a5c3a5 nt!KiRetireDpcList+0xd0
fffff802`9720dfb0 fffff802`96a5c1a9 nt!KxRetireDpcList+0x5
fffff880`016bfa40 fffff802`96b4bf95 nt!KiDispatchInterruptContinue
fffff880`016bfa70 fffff802`96a5ad13 nt!KiDpcInterruptBypass+0x25
fffff880`016bfa80 fffff880`0501005d nt!KiInterruptDispatch+0x273
fffff880`016bfc10 fffff880`00bdc916 vmswitch!VmsVmNicPvtKmclPacketSent+0x4d
fffff880`016bfc40 fffff880`00bdb873 vmbkmcl!InpProcessQueue+0x236
fffff880`016bfcd0 fffff880`0107807f vmbkmcl!InpProcessingWorkerRoutine+0x1b3
fffff880`016bfd20 fffff802`96a34fd9 vmbusr!WPP_SF_+0xffffffff`ffffffef
fffff880`016bfd50 fffff802`96ae97e6 nt!PspSystemThreadStartup+0x59
fffff880`016bfda0 00000000`00000000 nt!KiStartSystemThread+0x16
0: kd> analyze -show code
Couldn't resolve error at 'nalyze -show code'
0: kd> !analyze -show code
Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
0: kd> ub fffff802`9720cdb0 fffff802`96a5b01e
^ Range error in 'ub fffff802`9720cdb0 fffff802`96a5b01e'
0: kd> ub fffff802`96a5b01e
nt!KiInterruptDispatchLBControl+0x1a9:
fffff802`96a5aff9 740e je nt!KiInterruptDispatchLBControl+0x1b9 (fffff802`96a5b009)
fffff802`96a5affb 65488b0c2520000000 mov rcx,qword ptr gs:[20h]
fffff802`96a5b004 e8e771ffff call nt!KiEntropyQueueDpc (fffff802`96a521f0)
fffff802`96a5b009 488d4580 lea rax,[rbp-80h]
fffff802`96a5b00d 48898688000000 mov qword ptr [rsi+88h],rax
fffff802`96a5b014 488bce mov rcx,rsi
fffff802`96a5b017 488b5630 mov rdx,qword ptr [rsi+30h]
fffff802`96a5b01b ff5618 call qword ptr [rsi+18h]

Server 2:

Microsoft (R) Windows Debugger Version 6.2.9200.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\pavel.dokov\Desktop\темп\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\TEMP*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
Machine Name:
Kernel base = 0xfffff802`57c0e000 PsLoadedModuleList = 0xfffff802`57ed7a80
Debug session time: Mon Jul 22 11:04:12.825 2013 (UTC + 3:00)
System Uptime: 80 days 12:16:22.194
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols

Loading unloaded module list
.......
*******************************************************************************
*    *
* Bugcheck Analysis *
*    *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 784, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for bxnd60a.sys
*** ERROR: Module load completed but symbols could not be loaded for bxvbda.sys
Page d8bdc0 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : vmswitch.sys ( vmswitch!RndisDevHostDeviceIndicatePackets+1e1 )

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

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

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000000784, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

Page d8bdc0 not present in the dump file. Type ".hh dbgerr004" for details

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

TAG_NOT_DEFINED_c000000f: FFFFF8025923EFB0

LAST_CONTROL_TRANSFER: from fffff80257de1747 to fffff80257c88040

STACK_TEXT:
fffff802`592378f8 fffff802`57de1747 : 00000000`00000133 00000000`00000001 00000000`00000784 00000000`00000000 : nt!KeBugCheckEx
fffff802`59237900 fffff802`57cb3f06 : fffffa80`2b791a00 00000000`1a93fd50 fffff802`59237a80 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13cdc
fffff802`59237980 fffff802`58378eca : fffffa80`39486c60 00000000`00000000 fffff880`01d2b830 00000000`00000000 : nt!KeUpdateTime+0x41b
fffff802`59237b70 fffff802`57c814de : 00003f44`1fafdc02 00000000`00000002 fffff802`583a2580 fffff880`01d2bb1e : hal!HalpTimerClockInterrupt+0x86
fffff802`59237ba0 fffff802`57cb428e : fffffa80`2f0aa8a0 00000000`00000000 fffffa80`3ba9dc60 00000000`80000011 : nt!KiInterruptDispatchLBControl+0x1ce
fffff802`59237d30 fffff880`04e82a31 : fffff802`59237e60 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KeReleaseSpinLock+0x1e
fffff802`59237d60 fffff880`04e82810 : fffffa80`39486c60 00000000`00000030 fffffa80`ffffffff fffff802`59237f01 : vmswitch!RndisDevHostDeviceIndicatePackets+0x1e1
fffff802`59237eb0 fffff880`04e82615 : ffffffff`ffffffff fffff802`59230000 fffff802`59237f60 fffff802`00000000 : vmswitch!VmsVmNicPvtPacketForward+0xb0
fffff802`59237ee0 fffff880`04e860f4 : fffffa80`2b7b4000 00000000`00000000 fffffa80`2b55c001 fffffa80`2f1d64c0 : vmswitch!VmsRouterDeliverNetBufferLists+0x4e5
fffff802`59237fd0 fffff880`04e80a69 : fffffa80`00000000 fffffa80`2b55c000 00000000`00000000 0000ffff`ffffffff : vmswitch!VmsExtMppIndicatePackets+0x34
fffff802`59238010 fffff880`04e80652 : fffffa80`2b55c000 fffffa80`2b55c000 00000000`00000001 00000000`00000001 : vmswitch!VmsExtMpRoutePackets+0x339
fffff802`59238170 fffff880`04e7ffef : fffff802`592381b0 fffffa80`2f170001 00000000`00000000 00000000`00000000 : vmswitch!VmsExtPtRouteNetBufferLists+0x272
fffff802`59238240 fffff880`01494e4e : 00000000`00000000 00000000`00000000 fffffa80`00000001 fffffa80`0000025f : vmswitch!VmsPtNicReceiveNetBufferLists+0x34f
fffff802`59238300 fffff880`01494815 : fffffa80`307e2002 fffffa80`2f4c8b00 fffffa80`00000000 fffff880`0000025f : NDIS!ndisMIndicateNetBufferListsToOpen+0x373
fffff802`592383a0 fffff880`01494a25 : fffffa80`2b62a1a0 00000000`00000000 00000000`00000001 00000000`00000000 : NDIS!ndisInvokeNextReceiveHandler+0x6f5
fffff802`59238470 fffff880`0520f695 : 00000000`00000000 fffffa80`2fdf2000 fffffa80`2f4c8bb0 fffffa80`2fdd6e80 : NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
fffff802`592384f0 fffff880`0520f161 : fffffa80`2fdd6ee0 fffffa80`2fdf2000 00000000`00000001 00000000`0000025f : NdisImPlatform!implatTryToIndicateReceiveNBLs+0x1a1
fffff802`59238560 fffff880`01494e4e : 00000000`0001ff00 00000000`00000000 00000000`00001001 00000000`0000025f : NdisImPlatform!implatReceiveNetBufferLists+0x1a9
fffff802`592385e0 fffff880`014947d9 : fffff802`59238902 fffffa80`2afe3900 0000926d`00000000 00000000`0000025f : NDIS!ndisMIndicateNetBufferListsToOpen+0x373
fffff802`59238680 fffff880`01494a25 : fffffa80`2b5481a0 00000000`00000000 00000000`00001001 00000000`00000000 : NDIS!ndisInvokeNextReceiveHandler+0x6b9
fffff802`59238750 fffff880`04e154c3 : fffffa80`2f17b320 00000000`0000025f fffffa80`2f17b480 fffff802`59238920 : NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
fffff802`592387d0 fffff880`04e15a3b : fffff802`59238920 fffffa80`2dfbc070 00000003`00001001 fffffa80`2dbe8160 : bxnd60a+0x154c3
fffff802`59238850 fffff880`00e0b19a : fffffa80`2ad06010 00000000`00000000 00000000`00000000 00000000`0000025f : bxnd60a+0x15a3b
fffff802`592388f0 fffff880`00e0d73c : fffff802`59238a48 00000000`00000000 fffffa80`2ad06010 00000000`00000001 : bxvbda+0xb19a
fffff802`59238980 fffff880`00e1029e : fffffa80`2ad06010 fffff802`59238a60 fffffa80`2ad06680 fffff880`010adbf1 : bxvbda+0xd73c
fffff802`59238a00 fffff880`00e1174f : fffffa80`2ad06010 00000000`00000000 00000000`00010000 00000000`00000000 : bxvbda+0x1029e
fffff802`59238a90 fffff880`00e10a79 : fffffa80`2ad06010 00003f44`1fad7a9e 00000000`00000000 00000000`00000000 : bxvbda+0x1174f
fffff802`59238ac0 fffff802`57c7df38 : fffff802`57f05f00 fffff802`59238bf0 fffffa80`2ad1fd90 fffff802`59238ca0 : bxvbda+0x10a79
fffff802`59238af0 fffff802`57caeeb0 : fffffa80`00000000 00001f80`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiExecuteAllDpcs+0x198
fffff802`59238c30 fffff802`57cb36ca : fffff802`57f03180 fffff802`57f03180 00000000`00183de0 fffff802`57f5d880 : nt!KiRetireDpcList+0xd0
fffff802`59238da0 00000000`00000000 : fffff802`59239000 fffff802`59233000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_IP:
vmswitch!RndisDevHostDeviceIndicatePackets+1e1
fffff880`04e82a31 48837dc000 cmp qword ptr [rbp-40h],0

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: vmswitch!RndisDevHostDeviceIndicatePackets+1e1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: vmswitch

IMAGE_NAME: vmswitch.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 510cbec2

BUCKET_ID_FUNC_OFFSET: 1e1

FAILURE_BUCKET_ID: 0x133_ISR_vmswitch!RndisDevHostDeviceIndicatePackets

BUCKET_ID: 0x133_ISR_vmswitch!RndisDevHostDeviceIndicatePackets

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

0: kd> lmvm vmswitch
start end module name
fffff880`04e7c000 fffff880`04f0d000 vmswitch (private pdb symbols) c:\temp\vmswitch.pdb\C3BB001449F5486880C49B8C87592D831\vmswitch.pdb
Loaded symbol image file: vmswitch.sys
Image path: \SystemRoot\system32\DRIVERS\vmswitch.sys
Image name: vmswitch.sys
Timestamp: Sat Feb 02 09:22:42 2013 (510CBEC2)
CheckSum: 0008C7E0
ImageSize: 00091000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> .bugcheck
Bugcheck code 00000133
Arguments 00000000`00000001 00000000`00000784 00000000`00000000 00000000`00000000
0: kd> k
Child-SP RetAddr Call Site
fffff802`592378f8 fffff802`57de1747 nt!KeBugCheckEx
fffff802`59237900 fffff802`57cb3f06 nt! ?? ::FNODOBFM::`string'+0x13cdc
fffff802`59237980 fffff802`58378eca nt!KeUpdateTime+0x41b
fffff802`59237b70 fffff802`57c814de hal!HalpTimerClockInterrupt+0x86
fffff802`59237ba0 fffff802`57cb428e nt!KiInterruptDispatchLBControl+0x1ce
fffff802`59237d30 fffff880`04e82a31 nt!KeReleaseSpinLock+0x1e
fffff802`59237d60 fffff880`04e82810 vmswitch!RndisDevHostDeviceIndicatePackets+0x1e1
fffff802`59237eb0 fffff880`04e82615 vmswitch!VmsVmNicPvtPacketForward+0xb0
fffff802`59237ee0 fffff880`04e860f4 vmswitch!VmsRouterDeliverNetBufferLists+0x4e5
fffff802`59237fd0 fffff880`04e80a69 vmswitch!VmsExtMppIndicatePackets+0x34
fffff802`59238010 fffff880`04e80652 vmswitch!VmsExtMpRoutePackets+0x339
fffff802`59238170 fffff880`04e7ffef vmswitch!VmsExtPtRouteNetBufferLists+0x272
fffff802`59238240 fffff880`01494e4e vmswitch!VmsPtNicReceiveNetBufferLists+0x34f
fffff802`59238300 fffff880`01494815 NDIS!ndisMIndicateNetBufferListsToOpen+0x373
fffff802`592383a0 fffff880`01494a25 NDIS!ndisInvokeNextReceiveHandler+0x6f5
fffff802`59238470 fffff880`0520f695 NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
fffff802`592384f0 fffff880`0520f161 NdisImPlatform!implatTryToIndicateReceiveNBLs+0x1a1
fffff802`59238560 fffff880`01494e4e NdisImPlatform!implatReceiveNetBufferLists+0x1a9
fffff802`592385e0 fffff880`014947d9 NDIS!ndisMIndicateNetBufferListsToOpen+0x373
fffff802`59238680 fffff880`01494a25 NDIS!ndisInvokeNextReceiveHandler+0x6b9
fffff802`59238750 fffff880`04e154c3 NDIS!NdisMIndicateReceiveNetBufferLists+0xc5
fffff802`592387d0 fffff880`04e15a3b bxnd60a+0x154c3
fffff802`59238850 fffff880`00e0b19a bxnd60a+0x15a3b
fffff802`592388f0 fffff880`00e0d73c bxvbda+0xb19a
fffff802`59238980 fffff880`00e1029e bxvbda+0xd73c
fffff802`59238a00 fffff880`00e1174f bxvbda+0x1029e
fffff802`59238a90 fffff880`00e10a79 bxvbda+0x1174f
fffff802`59238ac0 fffff802`57c7df38 bxvbda+0x10a79
fffff802`59238af0 fffff802`57caeeb0 nt!KiExecuteAllDpcs+0x198
fffff802`59238c30 fffff802`57cb36ca nt!KiRetireDpcList+0xd0
fffff802`59238da0 00000000`00000000 nt!KiIdleLoop+0x5a
0: kd> ub fffff802`57c814de
nt!KiInterruptDispatchLBControl+0x1a9:
fffff802`57c814b9 740e je nt!KiInterruptDispatchLBControl+0x1b9 (fffff802`57c814c9)
fffff802`57c814bb 65488b0c2520000000 mov rcx,qword ptr gs:[20h]
fffff802`57c814c4 e8a3a9ffff call nt!KiEntropyQueueDpc (fffff802`57c7be6c)
fffff802`57c814c9 488d4580 lea rax,[rbp-80h]
fffff802`57c814cd 48898688000000 mov qword ptr [rsi+88h],rax
fffff802`57c814d4 488bce mov rcx,rsi
fffff802`57c814d7 488b5630 mov rdx,qword ptr [rsi+30h]
fffff802`57c814db ff5618 call qword ptr [rsi+18h]
0: kd> u fffff802`57c814de
nt!KiInterruptDispatchLBControl+0x1ce:
fffff802`57c814de fa cli
fffff802`57c814df 488b0df27e2d00 mov rcx,qword ptr [nt!_imp_HalPerformEndOfInterrupt (fffff802`57f593d8)]
fffff802`57c814e6 ff11 call qword ptr [rcx]
fffff802`57c814e8 65488b0c2520000000 mov rcx,qword ptr gs:[20h]
fffff802`57c814f1 80792001 cmp byte ptr [rcx+20h],1
fffff802`57c814f5 7772 ja nt!KiInterruptDispatchLBControl+0x259 (fffff802`57c81569)
fffff802`57c814f7 0f31 rdtsc
fffff802`57c814f9 48c1e220 shl rdx,20h

Please help!

P.S. We can remove switch 2, but on Switch 1 we do not have enough interfaces to plug in the other 2 NICs of each server.

Regards

↧

Advice for Home Hyper-V 2012

July 23, 2013, 1:04 am

≫ Next: Clustering and my NIC setup

≪ Previous: Windows Server 2012 BSOD caused by vmswitch.sys

Hi,

I have installed Hyper V Core at home for a test environment

I have installed 5 VM's

VM#1 - Linux Based Router (Untangle) for routing my Internet Traffic. (requires 2 NIC's - 1 to connect to my DSL Modem and the other to connect to my LAN)

VM#2 - Linux Based PBX

VM#3 - Windows Server 2012 Domain Controller with DNS, DHCP

VM#4 - Windows Server 2012 (Member Server) with Exchange 2013 installed

VM#5 - Windows Server 2012 (Member Server) Will be used in the future for Microsoft Lync

Currently I have 3 NIC's Installed in the Box. Is this enough ?

How would you setup the NIC's (Virtual and Physical) on this box ?

Many Thanks,

Richard

↧

Clustering and my NIC setup

July 23, 2013, 9:19 am

≫ Next: Setup Virtual Network - Can't Ping Between Host and VM

≪ Previous: Advice for Home Hyper-V 2012

Hi,

I am looking to deploy a Hyper-v Server 2012 cluster. I have two physical NICs on each server, one for the external public internet, and one for the internal network.

Is this sufficient for clustering? Is there any pre-requisite that is missing that I may need?

↧

Setup Virtual Network - Can't Ping Between Host and VM

November 14, 2012, 7:44 am

≫ Next: monitoring performance with hyper-v

≪ Previous: Clustering and my NIC setup

Hi,

I'm new to Hyper-V, and networking, etc, but, I do have a question:

I set up Windows 8 on my home PC. I created a VM using Hyper-V with Windows 8 as well. Note that I do not have a domain, etc on my home network. I'm not sure if that is part of the issue here.... The bottom line is that I want connectivity between the host PC and the VM, but, I can't seem to get that working.

My host PC's IP is 192.168.1.5, and the VM IP is 192.168.137.10.

When I set up the Virtual Network, I set it to Internal. I'm under the assumption that these two networks can't communicate because they are on different networks (192.168.1.x vs 192.168.137.x).....

Any suggestions or recommendations would be greatly appreciated!

Thanks.

↧

monitoring performance with hyper-v

July 19, 2013, 12:44 am

≫ Next: Hyper V Test Lab - Hardware

≪ Previous: Setup Virtual Network - Can't Ping Between Host and VM

Hi,

I have read up a bit on bottle necks for virtualisation and one of the main areas that I seem to need to keep an eye on is the disk queue length, furthermore I have read that I should be aiming to keep this below 2 per disk, so my RAID 5 has 3 disks so im guessing I need to keep the disk queue length below 6, firstly have I got this right?

secondly, is the disk queue length reported by the resource monitor on the hyper-v host itself accurate, does it give me the disk queue length for the real disks underneath or is it giving me false readings like the CPU does (I know not to trust the CPU reading on the hyper-v host).

what other disk related counters should I be monitoring more importantly what are the recommended thresholds (I find it difficult to nail down some real figures on these counters)

Thanks

Steve

↧

Hyper V Test Lab - Hardware

July 23, 2013, 3:17 pm

≫ Next: Get-childitem with recurse and create folders in a different directory

≪ Previous: monitoring performance with hyper-v

I have a fair idea where I want to go with my hyper-v lab, but I thought I'd post what I was up to and see if anyone had some input that may help myself and others down the road.

The MS TLGs are an awesome resource, but they all seem to assume one Hyper V server. Understandably - there are so many different possibilities ...which leads me to setup my questions:

I have 3 proliant microservers with 16GB RAM and SSDs for host OS.

Instead of buying a NAS, I was going to make server1 into a storage pool (4 1TB WD REDs) / SCOM machine using server 2012 and set up iSCSI. I have 5 gigabit ports on server1 - I was going to dedicate 2 nics to a team and create a dedicated iSCSI vlan or subnet.

The other 2 servers would be hyper-V servers on their own subnet that use server1 for storage.

But then I got to thinking, after watching the jumpstart and seeing the improvements in server 2012 maybe they should all just be hyper-V servers and I should virtualize everything.

Anyone have any input on what they would do in such a situation? Any recommendations on additional hardware?

↧

Get-childitem with recurse and create folders in a different directory

July 24, 2013, 2:09 am

≫ Next: Event 47 WHEA-logger

≪ Previous: Hyper V Test Lab - Hardware

I've got a folder containing child folders which I am doing a get-childitem -recurse on. My script at the moment is zipping the top level file in the script but I need it to do a little more.

For starters I need to zip all the files in each folder found but to a mirrored directory\archive somewhere else on the file system.

I have not got any code yet, does anyone know how I would make a start on this?

Alter De Ruine

↧

Event 47 WHEA-logger

June 17, 2013, 1:46 am

≫ Next: Connecting to a VM via RDP through the host

≪ Previous: Get-childitem with recurse and create folders in a different directory

Hello ,

I have a HP DL380G6 - base server running windows server 2008 R2 - 48 GB Ram

hosting 2 virtual servers " Hyper-V " , When the virtual servers start running the base server is keep recording event ID 47 WHEA - logger

every week one of the virtual servers suddenly losing it is connectivity " The server still running but not response to any network traffic "

i have update the server firmware recently , Still same issue

any advice ?

thanks ,,

↧

Connecting to a VM via RDP through the host

May 25, 2009, 12:36 am

≫ Next: Hyper-V VM could not initialize because the hypervisor is not running

≪ Previous: Event 47 WHEA-logger

Hello,
I'm developing software for Hyper-V management. I want to implement a GUI VM client similar to vmconnect.exe application.
Acording to the following post: http://blogs.technet.com/m2/archive/2008/06/02/how-virtual-machine-manager-administrator-console-uses-virtualmachineviewer-exe.aspx vmconnect.exe establishes RDP connection to the host computer.

"With the enhancements made to Win2k8 and VistaSP1, we are able to leverage MSTSCAX to connect to virtual machines through the host. What this means is that instead of directly connecting to the Virtual Machine using RDP, we instead RDP to the host and specify the VM to connect to"

The post doesn't get into the details what properties of RDP ActiveX have to be set so it would tell the host computer to redirect connection to a VM.

I would really appreciate if someone could point me to the right direction or better yet just post a simple code example showing how host-redirected RDP connection to a VM could be estabished.

Thanks,
Yury

↧

Hyper-V VM could not initialize because the hypervisor is not running

November 1, 2011, 12:57 am

≫ Next: Remote Management of Hyper-V Across One-Way Trust

≪ Previous: Connecting to a VM via RDP through the host

Here is a machine with Hyper-V and three VMs. Everything is OK. After an suddenly power cut, Hyper-V met the problem with the error message "The virtual machine could not be started because the hypervisor is not running".

There are three suggestions below.

1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.

2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled
in the BIOS of the physical computer.

(If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on.
Resetting the physical computer is not sufficient.)

3) If you have made changes to the Boot Configuration Data store, review these changes to ensure
that the hypervisor is configured to launch automatically.

As I said before, This machine works before. So point 1 won't be a problem. point 2, also checked the item with virtualization is in the ENABLE status. Point 3, checked the BCEedit, it is in auto status.

Also after rebuild the OS, it doesn't work either.

From the old post, most of the situation like this are caused by the BIOS or the hardware. But this case,the hardware worked before.

Any help will be appreciated.

↧

Remote Management of Hyper-V Across One-Way Trust

July 17, 2013, 8:11 am

≫ Next: Connection to DC lost and enabling GUI impossible

≪ Previous: Hyper-V VM could not initialize because the hypervisor is not running

In order to abstract our hardware from the platform, we would like to virtualize all of our physical machines, installing Hyper-V server and just running one VM on Hyper-V. We hope this will allow us to quickly migrate machines that currently cannot be on our virtual environment for whatever reason.

We set up a management domain for all of the Hyper-V servers separate from our main domain. A one way trust was established between the main domain and the management domain, with the management domain trusting the main domain. On the management domain, we created a domain local group, called Management Domain Admins, which contains the foreign security principals from the main domain. The Management Domain Admins group is added to the Hyper-V built in Administrators group.

Now here is the problem, from a workstation in the main domain, we can manage every part of that server except for adding a virtual hard disk. We can manage the firewall, we can look through the event log, we can create virtual machines and connect them to existing virtual hard disks, but we cannot create a virtual hard disk. The log returns:

The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

We disabled the firewall on both the workstation and the server with the same result. Using a workstation WITHIN the management domain, logging in with an account from the main domain, we can create a virtual hard disk. We have also tried enabling anonymous DCOM and adding the Hyper-V server to the Trusted Hosts list in WinRM to no avail. Also, using inline authentication, we can create virtual hard disks on the server BEFORE adding it to the domain. But as soon as it's added to the domain, we can no longer create hard disks.

Appreciate any insight!

↧

Connection to DC lost and enabling GUI impossible

July 8, 2013, 9:19 am

≫ Next: Live Migration Failing

≪ Previous: Remote Management of Hyper-V Across One-Way Trust

I transferred my AD lab from VMware ESXi 5.1 to Hyper-V 2012 Core. I have only 1 server to act as Hyper-V host, but during the migration I wanted to join the host to my domain, so temporary I had another Hyper-V client on W8 machine, started the DC.

Everything else worked fine, I even managed to create several networks via virtual switches, and I also enabled RRAS on a Hyper-V host. Then I created last network for nodes in different pool, and after next time, when I powered up my Hyper-V host, connection the DC was lost.

I have 3 different units, lets call them:
A = Hyper-V host with RRAS, and several NICs
B = W8 client with Hyper-V client
C= DC sitting on a client Hyper-V

A can access B, but not C
D can access both
C can access B, but not C

I copied DC to Hyper-V host, thought I could start it from there, reconfigure network and access to DC there. Nope - DC will start, but console connection via Hyper-V is not possible, because of some layer of security.

Last option - I´m trying to enable GUI on Hyper-V host. Tried to used powershell, dism, server manager dashboard from B to A. Everytime the result is the same - cannot download source files, even if I specify source as DVD media or install.wim

↧

Live Migration Failing

July 24, 2013, 6:02 am

≫ Next: Split a file path to remove up to first "/"

≪ Previous: Connection to DC lost and enabling GUI impossible

Hi all,

I just migrated my cluster from 2008 to 2012 using cluster migration. But when i try to test live migration, each vm gives following error:

The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'XXXX': The target principal name is incorrect. (0x80090322).

The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source host: The target principal name is incorrect. (0x80090322).

It seems like a SPN problem but i do not know which SPN should be registered. Both nodes have same SPN listed.

Same Vswitch configured as well.

Any idea?

↧

Split a file path to remove up to first "/"

July 24, 2013, 6:20 am

≫ Next: Alternative reason for Replica server failed to authorized the connection error 80070005

≪ Previous: Live Migration Failing

IS there a way to remove the first part of the URL as follows:

$url = "c:\scripts\test"

So that I just have "test" ?

I've tried replace and also split but nothign seems to work. So far I have

$newtoplevel = "c:\archive\"
$getDir = get-childitem -recurse -path c:\scripts | ?{ $_.PSIsContainer }
$newtoplevel.count

foreach ($folder in $getdir){
$folder.fullname

#I need t split here and work with the result

}

Alter De Ruine

↧

Alternative reason for Replica server failed to authorized the connection error 80070005

July 24, 2013, 6:26 am

≫ Next: Hyper-v VM location path chnage!

≪ Previous: Split a file path to remove up to first "/"

I wanted to put this out there to save the next person who runs into this will save time on researching it as I found nothing at all relating to this. I can successfully enabled Replication between two systems for some VMs but not for others and the error 80070005 was reported for them.

Long story short if you're getting "Replica server failed to authorized the connection" with error 80070005 and none of the other threads and posts sound like your issue check the VM IDs. If you've ever exported a VM from one machine to another and then imported it and told it to keep the same ID instead of creating a new one then that's the issue.

You wont find the answer on the machine initiating the replication but on the machine accepting it.

Event Logs -> Applications and Services Logs -> Microsoft -> Windows -> Hyper-V-VMMS

You should find Event ID 29284 errors that will give you the answer. Even though the VMs reside in different locations on the systems and have different names their VM IDs are identical. The machine your attempting to replicate to is denying the replication creation process because it does not believe you have the right to modify the VM it has with the exact same ID.

The only method of changing a VM ID I know of is to export and then import the VM having it create a new VM ID. After this has been done there is no longer a VM ID collision and you can enable replication.

Systems Administrator Senior - University of Central Florida

↧

Hyper-v VM location path chnage!

July 24, 2013, 5:13 am

≫ Next: Hyper-V 2012 (Free) setup routing between Virtual Networks

≪ Previous: Alternative reason for Replica server failed to authorized the connection error 80070005

Hi I have recently relocated a VM VHD to to new location i.e. a different storage mount point. Basically what i did was shutdown the VM> Copied to vhd file new mount point location under same host> Then went to VM settings and change the VHD path location. All looks good and server came up. But now when I take the old mount point path disk offline on the host server , the VM crashes and goes to critical-save state! I believe this is because The VM when it was created and is now still poiting having it to the old mount point path! How can I change VM location path to new mount point?

thnks,

bws

↧

Hyper-V 2012 (Free) setup routing between Virtual Networks

July 24, 2013, 6:44 am

≫ Next: Product key for HyperV 2008

≪ Previous: Hyper-v VM location path chnage!

Hi,

I'm trying to set up a POC so VDI, what i'd like to do is run my VM's on a Virtual Network with a really short DHCP lease, without having to drop the lease time for my Production network. Normally i would assuming that setting RRAS to route between the 2 lan insterface would be ok, however i can't get RRAS to start on the server. Is this not avaiable to the Free Hyper-v server?

Is there another way, or better way to get this setup?

thanks

↧

Product key for HyperV 2008

July 24, 2013, 7:22 am

≫ Next: Kerberos Live Migrations Fail with 0x80090322

≪ Previous: Hyper-V 2012 (Free) setup routing between Virtual Networks

I have downloaded the ISO file from MSDn of HyperV server 2008 . In MSDN its given that no product key is required. however, while installing from the setup file, its asking for the product key. Any help on this will be greately appreciated !!!

↧

Latest Images