DirectAccess Hyper-V Manager RPC Server Unavailable Server 2012

February 22, 2013, 12:53 pm

≫ Next: Need to increase size of C: drive on Exchange VM

≪ Previous: Move-VM - 'Incorrect function.'('0x80070001').

I have a windows 8 enterprise client connected remotely via DirectAccess (server 2012) to a hyper-v server running server 2012. Both are a member of the domain and when the windows 8 client is on the local LAN, hyper-v management works just as it should. I can't figure out what is needed to be able to manage virtual machines in Hyper-V manager. I keep getting RPC server unavailable, unable to establish communication between hyper-v server and my da client. I have also ran the hvremote tool and which didn't seem to do anything, until a bit later I noticed that I shouldn't since the version isn't supported yet for 2012. I also found an article aboutEnabling Hyper-V Management through DirectAccess but that article doesn't seem to work or be for server 2012.

Anyone have any ideas? If its all just client firewall settings I would like to just make a GP for the firewall exceptions so that any other client I want to work I don't have to mess with anything client side.

Thanks!

↧

Need to increase size of C: drive on Exchange VM

July 27, 2013, 3:13 pm

≫ Next: Default credentials not being saved in Hyper-V Manager for a single VM

≪ Previous: DirectAccess Hyper-V Manager RPC Server Unavailable Server 2012

I have Exchange running on a 2008 Hyper-v server. The C: drive is about 100 meg, the data store is on D: By the way, the C: drive is compressed (I didn't do it, I inherited this setup.)

Anyway, I'm using a backup solution that takes snapshots and there isn't enough room on the C: drive for the snapshots so it fails. I'd like to increase the C: drive size enough to accommodate the snapshot and decompress the drive.

I've had some bad luck with some of the machines here (dynamic compressed drives on the servers, etc.) so I need a fool-proof solution, failure is not an option. Any ideas?

↧

Default credentials not being saved in Hyper-V Manager for a single VM

August 10, 2011, 1:05 pm

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

≪ Previous: Need to increase size of C: drive on Exchange VM

Greetings,

I have a Server 2008 R2 SP1 Standard Hyper-V box running about 8 virtual machines on it. The machine is joined to a 2008 domain.

Recently, I moved the .VHD file for a single machine from one folder to another folder. After doing so, when I connect to ONLY that specific machine via Hyper-V manager, I receive the error: "Your credentials did not work. Your system administrator does not allow the use of default credentials to log on to the remote computer XXXXXX because its identity is not fully verified. Please enter new credentials."

I have the "Use default credentials automatically (no prompt)" option checked in the Hyper-V settings, and I have tried checking and unchecking this box and saving multiple times. I have also deleted the saved credentials and the system reports no saved credentials.

I have attempted to change settings in the group policy (gpedit.msc) regarding enabling the Local Computer Policy > Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow Delegating Saved Credentials with NTLM-only Server Authenticaton setting, something I found in older blog posts here in the Hyper-V forum and on other websites, and it has not made any difference.

At this point, I can only assume this must be some sort of bug because I cannot identify any other possible solution for getting rid of this annoying Windows Security pop-up box. There are no entries in the Windows event log that indicate anything odd. When I enter the correct username/password, I can still access the VM, but the credentials are never remembered, and ONLY for this single VM.

Does anybody have any knowledge of how to fix this issue? I can't believe that just moving a VHD caused all these problems.

Thanks!

↧

Windows Server 2012 BSOD caused by vmswitch.sys

July 22, 2013, 3:12 am

≫ Next: windows server enterprise without hyper-v 32 bit to Windows 2008 R2 Enterprise 64bit

≪ Previous: Default credentials not being saved in Hyper-V Manager for a single VM

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

↧

windows server enterprise without hyper-v 32 bit to Windows 2008 R2 Enterprise 64bit

July 28, 2013, 1:44 am

≫ Next: Modify the minimumbandwidthweight value

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

can i upgrade windows server enterprise without hyper-v 32 bit to Windows 2008 R2 Enterprise 64bit

↧

Modify the minimumbandwidthweight value

July 28, 2013, 4:56 am

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

≪ Previous: windows server enterprise without hyper-v 32 bit to Windows 2008 R2 Enterprise 64bit

Hi,

I deployed a converged network with Hyper-v R3 and I would like to modify the minimumbandwidthweight value for the LiveMigration.

How can I do it with PowerShell please ?

Thanks.

↧

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

July 24, 2013, 6:26 am

≫ Next: hyper-v networking woes

≪ Previous: Modify the minimumbandwidthweight value

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 networking woes

March 6, 2008, 7:27 am

≫ Next: VHD and VHDX won't Compact

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

Hi guys... I'm trying to get Hyper-V to work on 2008 and am running into multiple difficulties with the networking.

First run/installation I created a Vista VM to test things out.. Vista installed flawlessly but there was no network adapter visible within the OS. So, I played around with creating an adapter in "Virtual Network Manager" and tried assigning one to Vista... still didn't see it...

I tried a few different variations of adapters in the "Virtual Network Manager" and eventually deleted them out of there after nothing worked. Here is my first problem.... Although everything is cleared out of the virtual network manager, I still have MANY adapters installed under device manager....

Microsoft Virtual Network Switch Adapter #2 #3 #4 and #5

No matter what I try, I cannot remove them! That is the first problem I would like to resolve.... not sure how to remove these things even when they're cleared out of Hyper-V.

I tried removing the role and reinstalling it and they're still there... but now I have created a 2nd problem... When I try to go into the virtual network manager I get an error indicating the "Msvm_VirtualSwitchManagementService" object was not found... with error: "There was an error enumerating the machine's network switches. Make sure the Microsoft Hyper-V networking service is installed and working properly."

So, I verified all the services are running... "Microsft Hyper-V Image Mana..." "Microsoft Hyper-V Netowrking.." "Virtual Machine Management"

Not sure what to do at this point... 1) need to get rid of old adapters from previous installation... 2) would like to somehow setup a network adapter that actually works within VM...

Any assistance is greatly appreciated... thanks

↧

VHD and VHDX won't Compact

July 12, 2012, 11:29 pm

≫ Next: Windows Backup in side Hyper-V guest

≪ Previous: hyper-v networking woes

I also have the same problem.

If I compact a VHD or VHDX the compact runs for one second and ends, and the VM's remain uncompacted.

I am using REFS format on the drive, and the VM's are Windows 7 x86, if that makes any difference.

I have disabled System Restore in VM's, as that was a known problem with 2008 R2.

Can this be reported as a bug in Server 2012 RC.

↧

Windows Backup in side Hyper-V guest

July 29, 2013, 1:08 am

≫ Next: Unabel to setup remote desktop access to isolated HyperV lab

≪ Previous: VHD and VHDX won't Compact

I have Installed Hyper-V R2 as host. I have total 8 guest which is server 2008R2x64 with SP1. for safety i have configured

windows backup in side hyper-v guest. i have created 3 partitions in all 8 servers.

C:\ for OS and APPS

D:\ for data and other files

E:\ Windows Backup

my question is if one of my vm gets fails can i use windows backup to restore vm in gusest??

Akshay Pate Server Administrator

↧

Unabel to setup remote desktop access to isolated HyperV lab

July 29, 2013, 3:07 am

≫ Next: Failover Cluster WMI Provider detected an invalid character - W2008R2 SP1

≪ Previous: Windows Backup in side Hyper-V guest

Hey Guys,

I have an isolated HyperV lab made of 5 VMs which are in fact copies of live production VMs.
The lab is made of 4 SharePoint VMs + 1 DC and is working fine on its own. All VMs are connected to the same private HyperV network. Because these VMs are SAN copies of live machines, they can never communicate with the company LAN.

I now need to provide RDP access to the lab. We've first tried to use the HyperV manager to connect to the lab, which works fine, but is not comfortbale to use and only allow on connection at the time per VM.

So the idea is now to setup the host as a Terminal Server, the developpers can then RDP to the host and hop with a 2nd RDP to any VM in the lab.

My idea is to implement the following setup :

The Remote Desktop Services have been installed and configured, but I have the following issue: I cannot RDP to the host as soon as I enable the virtual NIC connected to the internal hyperv network. It's like of the traffic was not routed in the corrected direction. When that NIC connected to the internal hyper network is enabled, I cannot ping any machine from production and I must connect through iLO to manage the host (iLO = HP's console). As soon as I disable the NIC connected to the internal hyper network everything works fine again (except that I cannot of course reach my lab).

I've tried to play a bit with the order of the NIC in the avanced settings, but this didn't help.

What am I missing here ?

Thanks in advance for your help and have a nice day

↧

Failover Cluster WMI Provider detected an invalid character - W2008R2 SP1

July 29, 2013, 6:44 am

≫ Next: Access Device Manager in Hyper-V 2012

≪ Previous: Unabel to setup remote desktop access to isolated HyperV lab

We have a four node Hyper-V cluster running Windows 2008 R2 SP1 Data centre edition

For several months the following error has been flooding the application logs on the servers.

Failover Cluster WMI Provider detected an invalid character. The private property name 'PreviousOfflineAction' had an invalid character but the provider failed to change it to a valid property name. Property names must start with A-Z or a-z, and valid characters for WMI property names are A-Z, a-z, 0-9, and '_'.

The exact issue is detailed here with a Hotfix http://support.microsoft.com/kb/974930

Unfortunately the Hotfix is not applicable / won’t install on Windows 2008 R2 SP1

I've seen a few articles mentioning SCVMM, we run SCVMM 2012 SP1 it seems none of the fixes I've found so far relate to that.

Any ideas on how I can eliminate this error?

↧

Access Device Manager in Hyper-V 2012

September 6, 2012, 1:58 am

≫ Next: Strange behaviour of Hyper-v 2012 network

≪ Previous: Failover Cluster WMI Provider detected an invalid character - W2008R2 SP1

When I try accessing Hyper-V Server 2012's Device Manager via MMC I get "Make Sure that this computer is on the network, has remote administration enabled, and is running the "Plug and Play" and "Remote registry" services.

The Error Was: "The machine selected for remote communication is not available at this time.

I disabled the Hyper-V Firewall and followed the steps outlined here for "Allow remote access to the Plug and Play interface":
http://mikefrobbins.com/2010/12/02/enabling-remote-access-to-device-manager-on-server-core/

Any ideas?

The Hyper-V Manager works as-well-as the Policy Editor, just not Device Manager.

↧

Strange behaviour of Hyper-v 2012 network

July 28, 2013, 11:26 am

≫ Next: Just FYI, the new topic "What's New in Hyper-V Virtual Switch for Windows Server 2012 R2" is now live at http://aka.ms/Pbzck8

≪ Previous: Access Device Manager in Hyper-V 2012

Hello!

I have been testing Server 2012 hyper-v on a server with 2 gigabit nics, each one connected to gigabit cisco switch.

One nic is "straight" management with ip 10.179.10.30 and second - ip 10.179.10.31 is used for hyper-v machines.

I created external virtual switch on interface 10.179.10.31, deploy virtual machine- everything workrd fine until I checked "Allow management operating system to share this network adapter" on virtyal switch settings.

After that all vms on host become freezing in stopping state, and i cannot restart hyper-v service. But when i disconnect cable from "straignt" interface 10.179.10.30 it again works fine.

I'm very confused of such situation and i need help to understand whats going on. No vlans used in my configuration, vm gets ip address from DHCP from the same subnet 10.179.10.0/24.

I had tested this situation on different servers but always had the same results. Maybe i should configure switch ports somehow?

↧

Just FYI, the new topic "What's New in Hyper-V Virtual Switch for Windows Server 2012 R2" is now live at http://aka.ms/Pbzck8

July 25, 2013, 10:32 am

≫ Next: After import of VM on same host network not working

≪ Previous: Strange behaviour of Hyper-v 2012 network

Hi there -

Just FYI, the new topic "What's New in Hyper-V Virtual Switch for Windows Server 2012 R2" is now live athttp://aka.ms/Pbzck8

James McIllece

↧

After import of VM on same host network not working

July 29, 2013, 8:00 am

≫ Next: Product key for HyperV 2008

≪ Previous: Just FYI, the new topic "What's New in Hyper-V Virtual Switch for Windows Server 2012 R2" is now live at http://aka.ms/Pbzck8

I need to migrate my Hyper-V VMs on my 2008 R2 Server from the current SAN storage to a new attached disk shelf in the same Hyper-V host. I exported them then deleted the existing VMs from Hyper-V Manager and then imported them back, now located on the new disk shelf. After importing them my networking is not working. All the settings were retained but I have no connection to the network. I tried removing the network card and adding back a new one, a legacy card, re-installing integration services, removing the network adapter from device manager, but nothing works. What do I need to do to get the VMs connected back to the network?

↧

Product key for HyperV 2008

July 24, 2013, 7:22 am

≫ Next: Server 2008 Hyper-V VHD File Doubled In Size After Snapshot Merge. Won't Shrink?

≪ Previous: After import of VM on same host network not working

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 !!!

↧

Server 2008 Hyper-V VHD File Doubled In Size After Snapshot Merge. Won't Shrink?

July 29, 2013, 12:04 am

≫ Next: HyperV and Remote Desktop Connection

≪ Previous: Product key for HyperV 2008

I started with a Windows Server 2003 R2 VHD which had 2 partitions, C: (40GB) and D: (960GB), which originally came from a physical 1 TB hard drive. The ACTUAL size of the VHD file was 50GB, as a dynamically expanding disk.

I'm running this virtual machine in Windows Server 2008 Hyper-V (R1, not R2).

I had made several snapshots in Hyper-V of the VHD and decided to merge them, so I did a Delete Subtree (which does a merge to the current state). This oddly created a 107GB VHD file -- it went from 50GB to 107GB. Strange...

So I moved all the files off the D: partition of the VHD to an external physical hard drive and deleted the D: partition. The C: partition was still 40GB, and the space after it is Unallocated.

The VHD file is still showing as 107GB, yet the C: partition in the VHD is 40GB and there is no other partition before or after it. I've tried defragmenting, compacting, but I cannot get the VHD file to shrink from 107GB to 40GB. How can I do it?

↧

HyperV and Remote Desktop Connection

July 29, 2013, 9:44 am

≫ Next: Server 2008 R2 Ent showing as not all RAM usable

≪ Previous: Server 2008 Hyper-V VHD File Doubled In Size After Snapshot Merge. Won't Shrink?

I have a HyperV MS server running MS Server 2008 R2. The primary server and two of three VMs connect via Remote Desktop. One of the three VMs does not. All four servers are configured the same vis a vie Remote Desktop. So why doesn't the one VM allow remote desktop connections?

↧

Server 2008 R2 Ent showing as not all RAM usable

July 28, 2013, 11:40 pm

≫ Next: 2012 Hyper-V Cluster - Microsoft Hyper-V Network Adapter no connection but Legacy NIC works

≪ Previous: HyperV and Remote Desktop Connection

Hi All,

Currently have a server running 2008 r2 Enterprise (Hyper V from clean install) unfortunately its showing only 33.9GB RAM usable (out of 44GB Installed)

I have checked the following