Using NIC Teaming and a virtual switch for Windows Server 2012 host networking and Hyper-V.

October 6, 2014, 5:49 am

≫ Next: Shared nothing live migration wrong network

≪ Previous: Un-Virtualizing a Hyper-V VM

$

0

0

Using NIC Teaming and a virtual switch for Windows Server 2012 host networking!

http://www.youtube.com/watch?v=8mOuoIWzmdE

Hi thanks for reading. Now I may well have my terminology incorrect here so I will try to explain  as best I can and apologies from the start.

It’s a bit of both Hyper-v and Server 2012R2. 

I am setting up a lab with Server 2012 R2. I have several physical network cards that I have teamed called “HostSwitchTeam” from those I have made several Virtual Network Adaptors such as below examples.

New-VMSwitch "MgmtSwitch" -MinimumBandwidthMode weight -NetAdaptername "HostSwitchTeam" -AllowManagement $false

Add-VMNetworkAdapter -ManagementOS -Name "Vswitch" -SwitchName "MgmtSwitch"

Add-VMNetworkAdapter -ManagementOS -Name "Cluster" -SwitchName "MgmtSwitch"

When I install Hyper-V and it comes to adding a virtual switch during installation it only shows the individual physical network cards and the HostSwitchTeam for selection.  When installed it shows the Microsoft Network Multiplexor Driver as the only option. Is this correct or how does one use the Vswitch made above and incorporate into the Hyper-V so a weight can be put against it.

Still trying to get my head around Vswitches,VMNetworkadapters etc so somewhat confused as to the way forward at this time so I may have missed the plot altogether!

Any help would be much appreciated.

Paul

---

Paul Edwards

---

Shared nothing live migration wrong network

November 8, 2013, 8:21 am

≫ Next: Peachtree PAWEncrypt AcquireOurContainer Error Hyper-V

≪ Previous: Using NIC Teaming and a virtual switch for Windows Server 2012 host networking and Hyper-V.

$

0

0

Hey,

I have a problem when doing shared nothing live migration between clusters using SCVMM 2012 R2.

The transfer goes ok. But It choose to use my team of 2 x 1GB nic (routable) instead of the team with 2x10GB (non routable, but opened between all hosts).

I have set vmmigrationsubnet to correct net. Check live migration setting, and that port 6600 is listening on the correct IP.

But still it chooses to use the 1GB net.

Anyone got any idea what I can do next?

//Johan Runesson

Peachtree PAWEncrypt AcquireOurContainer Error Hyper-V

March 4, 2014, 7:07 am

≫ Next: Shared nothing live migration using the wrong network

≪ Previous: Shared nothing live migration wrong network

$

0

0

Alright so i know there's posts for this all over the internet, but i haven't seen a case of the error in the same environment that Ive gotten the error in. So to anyone who isn't familiar with the error:

It occurs with the Sage50/Peach tree software and has either something to do with .net or is a windows related issue. Sage50/Peach tree suggests reinstalling windows, or deleting the user account that is causing the error and recreating the account in order to fix it(which on a working domain is obviously not a good decision).

In my company we are running Hyper-V with a small pool of machines (which run the Peach tree software). A few weeks ago we had a power failure in our city for a few hours over the weekend. Prior to the failure the software was working fine on Hyper-V, however following the failure our remote users get a error message saying "PAWEncrypt AcquireOurContainer Error -<Numbers>". When i use the Hyper-V console at the server i have no issues, so that one is a tad confusing.

Ive tried updating IE (which worked until i logged off then back on to the machine), We have also tried the regedits suggested on the various pages regarding this issue. I've seen a lot of this issue out there but none of the issue while in Hyper-V, I'm wondering if there's any guru's out there with a possible fix. We can always blow the pool away and recreate it but the issue there is windows Licenses. I'm trying to not throw them away if possible.

I did call sage50 which they said that this issue is generally indicating that there's a problem in windows regarding the users account on the domain(But we only have this issue remotely so i would think that the account is fine).

Also one note in case anyone else is visualizing Peach tree, Ive fixed this issue once in the past. I had to blow the pool away and recreate from a new gold image. I wouldn't suggest doing that unless your totally out of options.

We are running Hyper-V on server 2012. And as for Steady State, It has never been on any of my servers.

-Trey

Shared nothing live migration using the wrong network

October 6, 2014, 1:05 pm

≫ Next: Hyper-V Server 2012 Remote Management From Windows 7

≪ Previous: Peachtree PAWEncrypt AcquireOurContainer Error Hyper-V

$

0

0

I have a cluster server and a standalone (both 2012 r2). Both are managed through vmm2012r2. Both have a  vEthernet (Live migration) which consist of 2 10 gig nics and a physical mgmt nic that is 1 gig.

a) I want to do shared nothing live migration across this network. I opened up cluster manager and set the Live Migration as the only live migration Nic for the cluster (inter-cluster migration works fine)

b) I opened up hyper-v on the standalone and enabled live migrations, I specified the network to use.

The live migration is non routable at this time. I can ping each of the interfaces from all the servers. Not too sure what else to try?

Hyper-V Server 2012 Remote Management From Windows 7

October 6, 2014, 10:57 am

≫ Next: Client VPN through VM

≪ Previous: Shared nothing live migration using the wrong network

$

0

0

Problem:

I've installed Hyper-V Server 2012. I've been painstakingly making my way through each step to be able do things that should be easy to do. Remote Desktop, Remote Server Manager, Remote Hyper-V configuration.

I'm using a Windows 7 x64 client. Each step along the way results in another need to go back to the Hyper-V 2012 Server and run another command to enable another firewall rule (netsh advfirewall firewall add....) or an Enable-NetFirewallRule, etc.

Can anybody point me toward a decent complete set of instructions anywhere so that I can get out of this, take one step forward, hit the next stumbling block, Google for solutions, fix the next stumbling block, hit the next stumbling block,  and on and on.

This is ridiculous!

I still can't connect using the Remote Server Management on Windows 7 and I've run the Enable-NetFirewallRule -DisplayGroup "Windows Remote Management" command, which completed successfully.

I can connect using the Hyper-V Management UI from the Windows 7 client, but now the main panel says 'Cannot connect to the RPC service on computer 'aaa.bbb.ccc.ddd'. Make sure your RPC service is running. (It is. I verified this using the Task Manager)

I know through brute force and numerous Google searches that I'll get through this, but seriously, is there an accurate and comprehensive set of instructions on how to complete this configuration around anywhere?

Client VPN through VM

October 6, 2014, 11:44 am

≫ Next: Unable to join virtual machines to domain controller

≪ Previous: Hyper-V Server 2012 Remote Management From Windows 7

$

0

0

I am trying to setup a VM environment that can access a customers environment. We will talk via cisco VPN that is the customers vpn. The customer does not support split tunneling

The problem, when connecting via remote desktop to the VM I get the following message "vpn establishment capability from a remote desktop is disabled. A vpn connections will not be established." Is this a problem on my side or the customers.

I also have setup a vnc to the VM and got farther and actually connected to the VPN; however I lost connection to the VM. I had to restart the VM to reconnect.

the customer is not helpful and I am spinning my wheels. any suggestions to get this resolved?

Unable to join virtual machines to domain controller

October 6, 2014, 8:37 am

≫ Next: Hyper - V Windows 2012DC, Performance of guest machine is very poor. All allocated RAM is already under utilisation at start up.

≪ Previous: Client VPN through VM

$

0

0

Hello all

I am studying for MCSE 2012 R2 and have decided to move from VMware Esxi 5.5 to Hyper-V in Server 2012R2.

I built the host (Server 2012r2) and so far 3 VMs (all are Server 2012R2 VMs) . I promoted one of the VMs to a Domain controller and things appear to have installed with no issue. This is what I have done so far:

Added Static IP addresses for all VMs

Configured each VM's DNS setting to use the DC 

When I try to join one of the virtual servers to the domain controller this is what I get.

Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "wolfpack.local":

The error was: "DNS name does not exist."

(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.wolfpack.local

Common causes of this error include the following:

- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

10.0.0.14

- One or more of the following zones do not include delegation to its child zone:

wolfpack.local

local

. (the root zone)

---

Phil Balderos

Hyper - V Windows 2012DC, Performance of guest machine is very poor. All allocated RAM is already under utilisation at start up.

September 23, 2014, 3:13 am

≫ Next: No Standalone RemoteFX machines?

≪ Previous: Unable to join virtual machines to domain controller

$

0

0

Hi Experts,

Greetings!

I have created Hyper - V host on Windows server 2012 DC. (256GB RAM is available on host)

I created a windows 7 x64 bit sp1 host with following memory allocation,

Start up memory - 1024MB

Enabled dynamic memory

Minimum RAM - 512 MB

Maximum RAM - 8192 MB

Memory Buffer - 20%

Memory Weight - Medium

Latest update of Integration services is installed.

Now, When I start guest machine and login into it, It is showing 70% of memory allocation is already in use and performing any operation causes delay (Response time is poor) . Launch of MS-Word or MS-Excel takes time.

How Can I solve this problem? Is dynamic memory allocation actually working?

Please Guide.

~Sumit Deshpande

---

No Standalone RemoteFX machines?

October 6, 2014, 6:45 pm

≫ Next: Windows Server 2012 R2 Hyper-V Hosts Login Screen froze

≪ Previous: Hyper - V Windows 2012DC, Performance of guest machine is very poor. All allocated RAM is already under utilisation at start up.

$

0

0

I have a machine in a lab that I had hoped to use for RemoteFX projects. It is purposefully not connected to another domain.

But in order to use RemoteFX you have to have Remote Desktop, which requires RD Licensing, which requires a domain, which requires active directory. And Active Directory and Remote Desktop can't coexist on one machine - so my project needs to be rethought. Correct?

Windows Server 2012 R2 Hyper-V Hosts Login Screen froze

September 27, 2014, 5:59 pm

≫ Next: Hyper-V VM Generation 2 - How to boot from .ISO

≪ Previous: No Standalone RemoteFX machines?

$

0

0

September 2014 Windows Updates Issue on Hyper-V hosts?

I performed some End of Month updates this weekend which froze the login screen on my Hyper-V hosts, no mouse movement, Ctrl+Alt+Del did nothing, non responsive. We were forced to perform a hard reset on the machines that is currently hosting around 100 VMs. I am glad we were able to recover from this malfunction but I am having issues trying to determine what exactly caused this issue.

Has anyone else seen this issue on Windows Server 2012 R2 platform and where should I start my investigation?

I have not noticed any issues on my physical servers, workstations, etc. except on the Hyper-V hosts.

Hyper-V VM Generation 2 - How to boot from .ISO

November 8, 2013, 12:31 am

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

≪ Previous: Windows Server 2012 R2 Hyper-V Hosts Login Screen froze

$

0

0

Hi guys, 

Server OS: Windows Server 2012 R2

I have a VM Gen2 with following settings: 

I can boot fine from the same .iso from a Gen1 VM so the .iso is bootable. 

I know that the Gen2 VM uses SCSI instead of IDE, but I have no clue regarding how to boot from the .iso..

Any ideas?

Thanks in advance!

Best regards,

Kenny

Windows Server 2012 BSOD caused by vmswitch.sys

July 22, 2013, 3:12 am

≫ Next: Core versus GUI

≪ Previous: Hyper-V VM Generation 2 - How to boot from .ISO

$

0

0

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

Core versus GUI

October 7, 2014, 10:54 am

≫ Next: Estimating Snapshop merge time

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

$

0

0

Looking for feedback virtualization with Hyper-V.

I'm currently setting up a virtual machine under Hyper-V. This machines role will be that of an AD server.

During the installation of Server 2012 R2 Standard, I have the option of Core or GUI.

I'm feeling hesitant about choosing Core but I feel like that is just because I'm so used to using the GUI for all server administrations in the past. As I think about the activities that I've performed after the initial installation of my AD environments in the past, it's actually rare to need to login to the AD servers for anything other than setting up users and/or reviewing event logs, etc. I've never had the need to run any 3rd party software (other than virus protection) on my AD servers.

Is there any reason to install the GUI other than to have the comfort level? Can the typical Administrative Tools be used on a Core installation? Can virus protection software and Windows updates be managed effectively if I were to install the AD role on just a core server?

Any input will be appreciated.

Estimating Snapshop merge time

October 7, 2014, 10:45 am

≫ Next: Cant create replica and Hyper V virtual machine management service slow shutting down

≪ Previous: Core versus GUI

$

0

0

Is there anyway to estimate how much time it may take my VM to merge after I shut it down post Deleting the Snapshot Subtree?  There is only one snapshot, but it was back from 12/19/13 when I was first learning about Hyper-V and didn't realize the impact of not merging it back then.  Only reason I ask is there is an essential application we use 24/7 being an EMS company so I wanted to provide a timeframe for it being down overnight.

My host Hyper-V 2012 Core server is a Dell R710, 2x6 Core CPU (24 virtual), 48GB RAM with only 2VMs. 

My current VHD and AVHD file sizes for this particular VM are as follows:

C: 65GB AVHD / 63GB VHD (last mod. 10/2/14 @ 3:45p)
E: 140GB AVHD / 55GB VHD (last mod. 10/2/14 @ 3:52p)
a060744a...: 16.5K AVHD / 53K VHD (last mod. 10/2/14 @ 3:39p)

Cant create replica and Hyper V virtual machine management service slow shutting down

October 7, 2014, 1:24 pm

≫ Next: What is the best approch to Patch Hyper V Host with cluster nodes

≪ Previous: Estimating Snapshop merge time

$

0

0

Hi,

I cant create replica and Hyper V, I go through the process and all looks good it even starts to create the hard disk but it stops at 4096K and the wizard just keeps going.

The management console is also slow or wont load virtual machines - stuck on loading virtual machines

The Hyper V virtual machine management service slow shutting down over 30 minutes on re boot of Hyper V core 2012 R2

Any ideas ?

---

What is the best approch to Patch Hyper V Host with cluster nodes

October 7, 2014, 8:32 am

≫ Next: Store avhds separate from vhds

≪ Previous: Cant create replica and Hyper V virtual machine management service slow shutting down

$

0

0

Hi

Please let me know What is the best approch to Patch Hyper V Host with cluster nodes

If we dont have SCCM and VMM is installed.

Store avhds separate from vhds

October 7, 2014, 11:26 am

≫ Next: virtual machine front end / manager

≪ Previous: What is the best approch to Patch Hyper V Host with cluster nodes

$

0

0

Is it possible in 2012 R2 to store the avhd files separate from the vhds?

Thanks,

Emily

virtual machine front end / manager

October 7, 2014, 1:14 pm

≫ Next: Virtual HDD incorrectly detected as SSD by Guest VM

≪ Previous: Store avhds separate from vhds

$

0

0

Is there a way to have vm's assigned randomly on user login?  I have a pool of 5 vm's that I would like to offer to my users without assigning specific machines.  I just want the user to connect and get the next one that is available.  Is this easily accomplished?

Thanks

Virtual HDD incorrectly detected as SSD by Guest VM

October 7, 2014, 12:29 pm

≫ Next: Hyper-V Server 2012 R2 Support

≪ Previous: virtual machine front end / manager

$

0

0

I have a Dell MD1000 with a SCSI hard drive array.  I have a Dell server running Server 2012 and Hyper-V, which is connected to the MD1000 via a PERC controller card.  I created a VM running Server 2012 with one "Virtual hard disk" (c:) and one "Physical hard disk" (d:).  In the VM's HyperV settings, the D: points to the MD1000's HDD array called "Disk 1 406.50 GB Bus 1 Lun 0 Target 0."  It's basically passed through the Host so the Guest can use it semi-directly.

When I boot that VM and go to the Windows Defrag tool, it inaccurately shows the D: as a "Solid State Drive" and I cannot defrag it.  In that drive's hardware properties though, it says it's a "Virtual HD ATA Device."  On the Host, the drive is marked Offline (it has to be for HyperV to use it) and its hardware properties window shows it's a "DELL PERC 6/E Adapter SCSI Disk Device."

Why is the Windows VM detecting this drive as an SSD when it's actually a SCSI HDD array?  How can I tell Windows that this is not an SSD so I can defrag it?

The VM hosts a database and stores the DB files on that D:, so I chose to pass the array straight through to the VM thinking I'd get better performance than if I used a VHDX file for the D:.

Hyper-V Server 2012 R2 Support

October 7, 2014, 12:27 pm

≫ Next: Configure Networking in Hyper V

≪ Previous: Virtual HDD incorrectly detected as SSD by Guest VM

$

0

0

I am using the free hypervisor, but want to know what my options are for support when I end up needing it.