Quantcast
Channel: Hyper-V forum
Viewing all 19461 articles
Browse latest View live

Hyper-V "Failed to import a virtual machine"

$
0
0

This feels very much like a repeat of other questions, but I've been through the forums and can't find an answer.

We have two Hyper-V servers: one is Windows Server 2008 R2 with Hyper-v installed (not core, the full server installation) the second is Hyper-V server 2008-R2.

I created a Virtual machine on server 1 (call it VMH1) to upgrade our Dynamics SL installation, so it has SQL Server on it as well. Using the Hyper-V Manager, I shut down the VM and exported the VM. That took about 20 minutes and finished with no errors. I then copied the export files to VMH2, the Hyper-V Server (which took about an hour) and ran the import there. Got the "Import file format error" which seems to have happened frequently with the 2008 RTM version, but everyone agrees was fixed with 2008 R2. The .exp files don't have server names in them.

So, I created a brand-new VM running Windows Server 2008 on VMH1, joined it to the domain, etc, then shut it down and exported it, moved it to VMH2, and imported it successfully. So, there doesn't appear to be anything wrong with the fundamental export-import procedure, I just can't export our actual production VM server to the other VMH.

An additional complication is that since VMH2 is core, there's no GUI, so I am running the Hyper-V manager on VMH1. Can't find any error messages or anyplace where the errors would be written on either server.

What do I do?


Hyper-V - Can not install Integration Services

$
0
0
Hello, people!

Disk2vhd: I used to try to migrate a physical server (SF01) virtual server (SV01).
The SF01 is a Windows Server 2003 Standard Edition SP2.
Physical server (SF02), Windows Server 2008 R2, was installed Hyper-V role.

I created the VM, and set the vhd to SV01. And I started it.

To my surprise! Both in normal startup mode or safe mode with networking. After logging in, there is a

screen for the registration of the license.
If you do not activate the license, a logoff occurs.

I ran the winproductkey both the SF01 as the SV01, and the product key is identical.
And when I try to activate the license for the same product key (Change Product Key option), back to the License Activation screen!

When activating the license of SV01 with the same SF01. It displayed an error!

Another problem:
In safe mode without networking. Can not login (SV01), but I can not install Integration Services.
But, the file C: \ windows \ vmguestsetup.msi.log is mentioned some errors:
Failed to connect to server. Error: 0x8007043C
Failed to connect to server.
MainEngineThread is returning 1601

What are the procedures to properly install the Integration Services?
And also to Activate License?<object height="0" id="fb6b5838-0b89-8fa2-e9bb-09bc3ababd9e" style=";left:0px;top:0px;" type="application/gas-events-cef" width="0"></object>

Se eu estiver respondendo a sua pergunta, e a mesma tiver utilidade. Vote com útil. Se for minha dúvida, e você me ajudar na solução, terei o maior prazer em votar como útil. Esse é o espírito do Forum MSDN !!! Valew !

Hyper-V guest loses network connectivty

$
0
0
I have a server runing windows 2008 R2 SP1 with hyper-v role.  I have a windows 2008 R2 SP1 guest running that loses network connectivity.  I am getting this event message when the issue happens.  Event Id 7042

The TCP/IP NetBIOS Helper service was successfully sent a stop control.

The reason specified was: 0x40030011 [Operating System: Network Connectivity (Planned)]

I have disabled the power management option on the network adapter on the hyper-v server and rebooted but I am still getting network connectivity loss.  I have tried hotfixes that is supposed to fix the issue but the install says it is not for my computer.  Any suggestions on this would be helpful.

Thanks


XP/SP3 & Hyper-V RC1 - cannot upgrade integration services

$
0
0

 

I have two XP / SP3 vitrual machines, and on each one, after I dismiss the "found new hardware" wizard, and try to install the Integration Services, I receive the "A previous installation og Hyper-V integration services has been detected"

 

I click OK to "upgrade or repair", and I get the following error message:

 

"An error has occured: Fatal error during installation."

 

My event viewer doesn't seem to have any relevant information.

 

Ideas?

 

Karl

VMSMP Event ID 28 filling System Log

$
0
0

Hello all.  I've gone in circles on search engines and here trying to find an answer.  It's shocking how common this problem is, that it affects servers so should have a very high priority for somebody at MS to look into, and yet notbody has ever found an answer that I can see.  Most posts I see are older though so I am hoping July 2013 has some answers :)

In short, I believe the problem may have begun 2 days ago when we replaced the building's only network switch with a new Cisco 2960-S switch.  These are simple GbE switches that work out of the box so nothing new has been configured.  I do intend to further configure at some point but this was an emergency replacement. 

Yet the Hyper-V host (2008 R2) is now showing VMSMP Event ID 28 messages in the System Log at a rate of about 30,000,000 entries per day.  Any time I look, there are about 46,000 entries, if I Clear Log and count to 10, refresh and I have between 3000-5000 more entries.  I guess 46,000 is the limit before older ones start ot disappear. 

The VM's appear to be unaffected, but because I exclusively RDP to just the host machine and use Hyper-V manager to access the VM's, I can't be sure.  No users have complained yet. 

However my RDP session freuqntly needs a refresh due to disconnect so clearly this problem affects the host. 

NIC setup is:

4 physical NIC.

4 VMs

VM1 is the primary AD DC, and shares the NIC with the host.  The other 3 NIC's are dedicated to the other 3 VMs. 

The 4th VM though is not in use yet, so in theory the 4th physical NIC is free, however I'm afraid to try to use it for VM1 (thus breaking the "share with host" relationship) because being a little fresh on these subjects I"m not sure what that'll do to the IP address of the AD DC, which if I mess that up brings down the network for the users. 

Of course I'd rather solve the VMSMP problem but as a workaround, can I just assign the 4th NIC to the VM1?  I'm doing this remotely too, so don't want to uncheck "share with mgmt OS" and cut myself off...

Btw, I did try to set static MAC addresses for each VM - no change.  This has never worked for anybody in any post/thread I've seen either if that says anything. 

Totally lost, please help! 

Drawing Network Diagrams For Virtualized Networks.

$
0
0

Hi guys, 

I'm looking at drawing up simple network diagrams of the virtualised servers and IP addresses.. To make it easier to remember the IPs of the virtual machines and the hypervisor, which can get confusing at times. Is there any basic starting diagram I could use to give a simple, clear visual representation of the virtualized network, which I could then use as a template for drawing custom network diagrams for my clients. 

nb. I dont have visio, but I have photoshop my plan would be to get an image file and just edit this as required. 

thanks, 

J


Import and Export of VMs from remote file server won't work for Windows Server 2012

$
0
0

I have three different Windows Server 2012-based Hyper-V networks currently running. I ran these environments originally on 2008 R2 Hyper-V. I only recently built Windows 8 managmenet workstations to to remote management of these domains. In each of the domains, there is a file server that contains shares to export and import VMs form the Hyper-V hosts. I just noticed that I cannot import or export VMs from the file shares when I remotely administer the Hyper-V hosts.

In the import wizard I can browse through the share and select the VM folder, but when I hit Next in the wizard I get "The folder (the remote file server path) could not be found. You might not have permission to access it."

The export wizard gives more or less the same error, but with an added possibility: with no changes happening on the network during my tests, the export will sometimes run with no error and export to the remote file server, but later on when I test it again it will resume giving access denied errors.

To make remote administration work in in these scenarios the usual fix is to to a constrained delegation on the hyper-v host of the cifs service to the remote file server. I did this on the old 2008 R2 Hyper-V hosts and didn't have any notable issues. I have made the same delegation for the Server 2012 Hyper-V hosts but I do not get the expected good result.

What's strange is that nonoe of the three Server 2012-based networks I am running will do the delegation correctly. I haven't seen any web pages recommending any other settings to make this work. Is there some extra step to make Hyper-V 3.0 do the delegation successfully?

 

Tape Drive In Child Partition?

$
0
0

Can one attach a physical tape drive to a guest operating system with Hyper-V?


Where to install Remote Desktop Services.?

$
0
0

I have been working on documentation on how to install Hyper-V on a HP ProLiant, and have it pretty much finished.. But one thing is baffling me... 

Server has Windows 2012 and Hyper-V installed as the Management OS. In Hyper-V, I have one virtual Windows 2012 server that is domain controller / DHCP / DNS for the network... The Management OS is a domain member server and I am logged in as the Domain Administrator..  I set up remote desktop services on the Management OS, assigning it all of the required roles (Connection Broker etc etc).. Then I create a Personal Desktop Collection (again on the Management OS) using a sysprepped Windows 7 virtual machine in Hyper-V. Then the users then log in to the Management OS IP/hostname from the browser to access their Personal desktop. 

I have read that some people set up RDS on one of the virtual machines, and assign the virtual machine all the roles, but I dont understand how this can work as the sysprepped machines are sitting on the Hyper-V server.. But I also understand that no services other than Hyper-V should be running on the Management OS... What is the best way to set this up for a small business where only one/two users will be accessing personal virtual desktops.. 

thanks, 

How to connect USB external Harddisk to Hyper-v virtual machine

$
0
0

Hi,

We are running hyper-v server 2008 R2, we have external USB harddisk connected in hyper-v Manager, we are not able connect this USB to virtual machine.. is this option is available in hyper-v? if no is there any document from microsoft stating the same?

Regards

Asha


Windows Server 2012 BSOD caused by vmswitch.sys

$
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

Hyper-V on 2012 host compressed drive

$
0
0

I just noticed that on my 2012 host server, the drive where I have been placing my VM hard drives is compressed.  I can imagine that this is not desirable on many levels, so I would like to turn off the compression setting for the drive.

What do I need to watch out for?  I am thinking that if I shutdown each VM first, before I turn off compression, it should be fairly safe.

Is Hyper -V free for big organization

$
0
0

Is hyper -V can host 400 virtual machines?

How is it counted for licenses and fees?

We have vmware but it is too expensive so we want to do comparison between hyper -V and Vmware to see the difference for price and functionality and limitations of VMs.

Hyper V Create VM with custom settings using WMI attach VHD

$
0
0

Does anyone have a complete example of how to create a VM that has custom settings and VHD's attached using WMI from PowerShell? (need to use WMI and not the library from codeplex)  I have found a lot of partial scripts that create default vm's without vhd's attached and a lot of broken links pointing to solutions.  Have also seen reference that it can be done with AddVirtualSystemResources but have not seen any examples.  Here is what I have so far, and thanks in advance!

Create VM with no VHD's, and create VHD but don't know how to connect the VHD or create it during the VM creation steps:

#get the current computer name
$currentname=get-wmiobject Win32_ComputerSystem

$namespace=$currentname.name

#create a VHD
$disk = Get-WmiObject Msvm_ImageManagementService -namespace "root\virtualization" -computername $namespace

$disk.CreateDynamicVirtualHardDisk("$env:systemdrive\nameofvhd.vhd", 20000000000)|out-null
$newvm="Test"
$description="This is the Description"
$path="$env:systemdrive\testvmfolder"

# Create a VM

# Get a new instance of Msvm_VirtualSystemGlobalSettingData

$vsgsdClass = [wmiclass]"root\virtualization:Msvm_VirtualSystemGlobalSettingData"
$vsgsd = $vsgsdClass.CreateInstance()
$vsgsd.ElementName = $newvm
$vsgsd.Description = $description
$vsgsd.ExternalDataRoot = $path

# Get the managment service and define the system from the embedded instance
$vmms = gwmi -namespace root\virtualization Msvm_VirtualSystemManagementService

$result = $vmms.DefineVirtualSystem($vsgsd.GetText(1))

if($result.ReturnValue -eq 4096){
    # A Job was started, and can be tracked using its Msvm_Job instance
    $job = [wmi]$result.Job
    # Wait for job to finish
    while($job.jobstate -lt 7){$job.get()}
    # Return the Job's error code
    return $job.ErrorCode
}
# Otherwise, the method completed
return $result.ReturnValue

 

VSS fails on mounting a virtual copy of a LUN

$
0
0

I have a HyperV-Server 2012, there are VMs running with following configuration.

Configuration A:

  1. Windows 2008R2 Server x64.
  2. Exchange Server 2010 SP3.
  3. LUN presented via Virtual Fibre Channel.
  4. MailBox created on a LUN.

Configuration B:

  1. Windows 2012 Server x64.
  2. Exchange Server 2010 SP3.
  3. LUN presented via Virtual Fibre Channel.
  4. MailBox created on a LUN.

We are performing backup tasks related to LUN, like taking snapshot, mounting, restoring etc.

In configuration A we are successfully able to do the above operations, but in configuration B we are facing VSS issues while mounting the snapshot.

Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {5f466535-9c6c-4b33-be9f-8f3147381cf5}. Routine details Routine ImportSnapshotSet failed with 0x800423f8 [hr = 0x800423f8, An expected disk did not arrive in the system.].

Does anyone has any idea why this issue is being hit only in Windows 2012 Environment?

NOTE: Both the configurations A & B are working fine in VMDirect(VMware). This issue is being faced only in Virtual Fibre Channel(HyperV).



How to find out the creator who created snapshot on a Hyper-V host?

$
0
0

question as the subject...

I cannot find any thing in the log file which can show me who create the snapshot.

HyperV planned failover fails reversing replication. FQDN is truncated.

$
0
0

Hi,

I am having an issue with planned failover between two hyper-v hosts

- HostA and HostB are on the same domain
- DNS is all fine both servers can ping each other using FQDN and hostname
- Using kerberos authentication between hosts

I can go to the "other" host fine and manually start the reverse replication fine, it just will not do it automatically as part of the planned failover.The same thing happens regardless of which way I am failing over HostA to HostB or HostB to HostA

A screenshot probably explains it best, notice the second highlighted section is missing the .LOCAL

I have only found one other reference to this issue http://social.technet.microsoft.com/Forums/windowsserver/en-US/af8704b3-6623-40ba-af78-567f69a9eca1/hyperv-2012-replication-planed-failover-failed-to-resolve-the-replica-server#c7a08d0e-479a-40d1-8b64-fac309741e21

Andy


Andrew

Replicate Hyper-v Virtual Servers

$
0
0

Hi.

We currently have a small SAN and a 2 node 2008R2 Hyper-V cluster with a couple of CSV's. Just recently we had a fire in the building and this has made everything sit back and think a little bit more about DR.

Up the road we have another building and a 100mb fibre pipe between the 2. As a quick solution we would like to stand up a single server running Hyper-V with a fair bit of storage. Then replicate the virtual machines here in case of DR.

I would like to know if anyone has done something like this, and if there is a best way to replicate the machines without turning the live ones off. We would only replicate the mission critical ones, as all the others are backed up and tapes off site.

What commands did you use or 3rd party software is recommended?

Or is the simple answer to upgrade to Server 2012 Hyper-V?

many thanks

Olly

Removing for dependencies: kmod-microsoft-hyper-v

$
0
0

When I try a yum update (CentOS 6.3 over Hyper-v 2012) in propose to remove hyper-v integration:

Removing for dependencies:
 kmod-microsoft-hyper-v

Why? Is ok?

thanks

problem with internet in Virtual Machine in Windows Server 2008 R2

$
0
0

Hello,

I am using Windows Server 2008 R2, I have Statis IP configured in one of my Ethernet NIC which I am sharing on external Ethernet NIC. When I install Hyper V and create one Virtual Machine, The internet on Virtual Machine is not working. I have tried all the possible steps but yet did not got any appropriate solution.


Wasif K Niazi

Viewing all 19461 articles
Browse latest View live




Latest Images