Hyper-V forum

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!

Recently wanted to do a project on the Hyper-v, development of language is C++,But,to find the relevant information is all about C#。 included Microsoft Hyper-v document。 Anybody know how Hyper-v used inC or C++，tKs

I had a HP Proliant DL360 G5 Server running windows 2008 R2. I made a Hyper-V VM using the disk2VHD tool from sysinternal. I ran that image in a hyper-v host (win2k8 R2) and facing following problems

1- When i install the Hyper-v integration services the setup goes through fine and completes without any error.

2- But after reboot the services are not working. I am unable to use the mouse and unable to add Network adapter. Only legecy adapter works.

3- I have uninstalled all HP stuff from the physical server.

Please Help

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

Hi Guys,

I was just looking for some insight as to why my VLAN configuration doesn't seem to work in Hyper-V

I have a cisco catalyst 4510R switch with multiple VLANS , i've created a trunk port from the Cisco and connected it to the physical port on the hyper-v host.

I create a new Virtual switch in Hyper-V.

Then I create a VM and assign it to the newly created network, whilst i'm there i set the VLAN ID to 150 (which is my server VLAN)

I set a static ip address from within the VM that is on the same network and perform a series of tests, mainly ping tests to see if i can reach certain destinations. Unfortunately i can't reach any destination other than myself (localmachine)

have i missed something? I'm sat here scratching my head..

The network card in the server is a Broadcom BCM57095 if that helps.

Any tips would be great!

Many Thanks.

Andy

Help!

I expanded a VHD to the full 2TB limit now I get an error saying there’s not enough room for the assigned memory to load. (If I cut the assigned memory to 1GB the VM will load. Also, I have not expanded any drive space in the VHD yet.) How can I correct this to get reasonable space for assigned memory?

Thanks!

I have just embarked on a project to v2v 250 VMs from vSphere 5.1 to Hyper-V 3.0. I thought I'd start a discussion string on v2v experiences. I have used the native v2v conversion with in VMM, 5nine's Easy Converter, Starwind's Converter and MVMC. I'm not happy with any of them. They are so inconsistent and frustrating, I see this project as literally taking years. Sometimes the VMM converter works, sometimes it just fails with crypt error messages. At the beginning it would crash the management interfaces on the ESXi servers but a ticket with VMware and increasing some system values solved that.

Most of the time, it will run for an hour or two, then just fail with no explanation. Same for MVMC. Occasionally I have some luck doing a p2v instead of a v2.

5nine usually fails, but gives me the VHDX files so I can create the VM from there. Ditto for Starwind.

Even if I could get a product that works consistently, the fact that 5nine and VMM actually make 2 or 3 copies of the VMDKs during the conversion process is pretty ridiculous. I have had to carve out terabyte LUNs to attach to a Hyper-V host just to have enough scratch disk to convert, then watch the conversion take literally hours.

All in all, a very frustrating experience. Have others been faced with similar issues? And if so, how did you tackle it?

Thanks.

Hello,

cannot find any info on web and View problem details in VIRTUAL MACHINE CONNECTION error box:

"virtual machine connection has stopped working".

I get this error when click Connect in HV Manager. The machines are on and are accessible through RDP.

This is a lab host after restart it randomly works. I have this problem during last week.

Just interesting to know what could cause the problem and if other were seeing something like that...

Also, can connect to machine from SCVMM.

Thx.

"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

Ive got a 2012 Storage server, running 10Gb nic to a HyperV host also running 10Gb. The Host is running 10Gb to the LAN.

Transfer rates between the host and the storage server on a direct copy are running around 5-6Gbps however if I attach a VHDX on the storage server (SMB 3.0 share) to the host and start the VM the transfer rate is about 300-400mbps.

Ive enabled SR-IVO on the nic and I thought that visibly made a difference however the task manager is not reporting that increase and still reports 300-400mbps

Both the host and the storage server have 1Gb management nics but I have made 100% sure that the traffic isn't going up those ports, using IP instead of host names and also setting host files on both machines to reflex to SAN subnet. The management ports report kbps when the 10Gb is reporting mbps.

Anybody shed any light?

Regards

Tim

i need to query hosted VMs for some OS parameters. i can query for FQDN and/or IP of the machine but as they are in numerous VLANs and are secured with FW and are in several domains... it will not be possible to make it as for normal server.

as Integration Services gives some kind of bridge between host and guest i was thinking that maybe there is some way to query internal OS of VM somehow through it?

same question in reverse: how would you automatize some administrative tasks on VMs on hosted environment?

...of course i know it's against security blablabla ... anyway maybe there is some backdoor giving access to VMs q:

-o((: Leliv

Hi,

I have a VM that failed after moving VM storage in Hyper-V, and on reboot the server is now showing "A disk read error occurred. Press ctrl alt delete to restart". Today I moved several VMs, all others moved without issue.

I have tried a couple of recovery steps:

1 - CHKDSK - I get an error about corrupt master file table and then chkdsk exits.

2 - bootrec /fixmbr and bootrec /fixboot - no change after reboot

3 - attaching all the disks (1x IDE & 2x SCSI) to another VM - once brought online they show as RAW and containing no data.

The file sizes are still correct. What else can I do to attempt to recover data from this disk?

I have an application that draws corrupted I-beam and Wait cursors. There may be other cursor modes affected, but I haven't investigated them. The client is a Windows 7 x64 guest running on Hyper-V Server 2012 Datacenter Edition. The sequence to reproduce the issue may appear slightly complicated, so bear with me.

The Windows 7 x64 Hyper-V guest RDP's to a jump server running Server 2012 Standard on which the application runs. After much struggle, I finally found that lowering the Hyper-V video adapter's acceleration one notch to the left (on the Windows 7 x64 Hyper-V guest) allows the application to draw cursors correctly. The Hyper-V guest is managed through the native vmconnect.exe Hyper-V console. The corruption doesn't occur with the mouse arrow, but does occur with the I-Beam and Wait cursors. There is no corruption on any cursors directly within the Server 2012 Standard edition (jump server), only the application that the jump server executes.

I have verified that physical Windows 7 x64 clients do not exhibit this issue with the RDP/application, only the Hyper-VM client. I prepped a secondary Windows 7 x64 client just to be sure the problem wasn't specific to the installation. The issue still occurs.

I have fielded a support request to the application developers, but when work-around can be found by changing video acceleration on the Hyper-V guest, I have to suspect it's a bug in the Hyper-V video adapter.

Has anyone experienced this issue on a Hyper-V guest? I see postings relating to physical video adapters which prompted me to adjust acceleration on the Hyper-V video adapter.

Hi Forum,<o:p></o:p>

We are running hyper v 2012. Our requirement is to create bare VM's and assign VM to users so that the user shall have control over their VM.<o:p></o:p>

I tried installing hyper v manager in client machines but they have access to all the VM and other features.<o:p></o:p>

We want to know whether it is possible to install hyper v manager on client machines and give access only to their respective VM's (ie, only their respective VM's should be visible or they should have control only over their VM)

Regard's

J.P Raj

<o:p></o:p>

Latest Images