Hello,

We have experienced a multiple VM failures and 2 cluster node reboots in a seven node Windows Server 2012 cluster.

Multiple virtual machines crashed as a result of „STATUS_CONNECTION_DISCONNECTED(c000020c)“ error reported for multiple CSV LUNs on multiple Hyper-V nodes. This is one example of these errors:

Log Name:      System

Source:        Microsoft-Windows-FailoverClustering

Date:          26.2.2014. 22:12:03

Event ID:      5120

Task Category: Cluster Shared Volume

Level:         Error

Keywords:     

User:          SYSTEM

Computer:     CL01N04.domain.local

Description:

Cluster Shared Volume 'HYPERV_LUN_9 (SAS)' ('HYPERV_LUN_9 (SAS)') is no longer available on this node because of 'STATUS_CONNECTION_DISCONNECTED(c000020c)'. All I/O will temporarily be queued until a path to the volume is reestablished.

Two Hyper-V nodes crashed, node 5 and node 7. This was reported in the error log for one of the nodes:

Log Name:      System

Source:        EventLog

Date:          26.2.2014. 22:16:54

Event ID:      6008

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:     CL01N05.domain.local

Description:

The previous system shutdown at 22:11:37 on ‎26.‎2.‎2014. was unexpected.

Log Name:      System

Source:        Microsoft-Windows-WER-SystemErrorReporting

Date:          26.2.2014. 22:16:57

Event ID:      1001

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:     CL01N05

Description:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009e (0xfffffa81b5557080, 0x00000000000004b0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 022614-43914-01.

Four CSV LUNs were emptied from VHDX disks because of virtual machine decommissioning. These four empty CSV LUNs were removed from cluster shared volumes using „Failover Cluster Manager“ console from node 1 using right-click „Remove from Cluster Shared Volumes“. During this operation the „Failover Cluster Manager“ console hanged during removal of each disk for about 10 minutes. The disks appeared as failed after the console refreshed itself and then they could be successfully removed from the console. It took another 20 minutes for the remaining CSV disks and virtual machines to start crashing. In the attachment are excerpts from the Cluster.txt log file with some important event logged just before crashed occurred. Most notable are the following:

00000a54.00001b0c::2014/02/26-20:51:23.285 ERR   [GUM] Node 2: Local Execution of a gum request /rcm/gum/MarkGroupBusy resulted in exception ERROR_CLUSTER_GROUP_BUSY(5944)' because of 'Group is in the middle of some other operation'

00000a54.00001b0c::2014/02/26-20:51:23.285 ERR   [RCM] rcm::RcmApi::ChangeResourceGroup: ERROR_CLUSTER_GROUP_BUSY(5944)' because of 'Group is in the middle of some other operation'

00000a54.0000221c::2014/02/26-20:51:58.869 ERR   [RCM] rcm::RcmResControl::DoResourceControl: ERROR_RESOURCE_CALL_TIMED_OUT(5910)' because of 'Control(STORAGE_GET_DISK_INFO_EX) to resource 'Exchange2010' timed out.'

00000a54.0000221c::2014/02/26-20:51:58.869 WARN  [RCM] ResourceControl(STORAGE_GET_DISK_INFO_EX) to Exchange2010 returned 5910.

(Note: Exchange2010 is the CSV disk being decommissioned)

00000a54.00002a18::2014/02/26-20:54:09.516 ERR   [RCM] rcm::RcmResControl::DoResourceControl: ERROR_RESOURCE_CALL_TIMED_OUT(5910)' because of 'Control(STORAGE_GET_DISK_INFO_EX) to resource 'HYPERV_LUN_9 (SAS)' timed out.'

00000a54.00002c8c::2014/02/26-20:54:09.516 ERR   [RCM] rcm::RcmResControl::DoResourceControl: ERROR_RESOURCE_CALL_TIMED_OUT(5910)' because of 'Control(STORAGE_GET_DISK_INFO_EX) to resource 'HYPERV_SQL_LUN_2 (SAS)' timed out.'

00000a54.00002a18::2014/02/26-20:54:09.516 WARN  [RCM] ResourceControl(STORAGE_GET_DISK_INFO_EX) to HYPERV_LUN_9 (SAS) returned 5910.

00000a54.00002c8c::2014/02/26-20:54:09.516 WARN  [RCM] ResourceControl(STORAGE_GET_DISK_INFO_EX) to HYPERV_SQL_LUN_2 (SAS) returned 5910.

(Note: CSV LUNs above are production LUNs with live virtual machines. After these events the virtual machines are starting to fail.)

DPM backup was running at the time of failure. We have experienced at least 4 previous crashes because of CSV disks being unavailable during DPM backup and as a result we have configuredCSV serialization.

We have the following cluster resiliency hotfixes installed:

-         http://support.microsoft.com/kb/2878635

-         http://support.microsoft.com/kb/2796995

-         http://support.microsoft.com/kb/2813630

-         http://support.microsoft.com/kb/2870270

-         http://support.microsoft.com/kb/2838043

-         http://support.microsoft.com/kb/2869923

This is analysis from a memory dump:

MODULE_NAME: netft

FAULTING_MODULE: fffff80010a15000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5010aa07

PROCESS_OBJECT: fffffa81b5557080

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9E

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8800591c845 to fffff80010a6f440

STACK_TEXT: 
fffff880`009a37f8 fffff880`0591c845 : 00000000`0000009e fffffa81`b5557080 00000000`000004b0 00000000`00000000 : nt!KeBugCheckEx
fffff880`009a3800 fffff880`0591c516 : 00000000`00000002 fffff880`009a3b10 fffff880`009a3939 00000000`00000000 : netft+0x2845
fffff880`009a3840 fffff800`10a981ea : 00000000`00000002 00000000`00000000 fffff880`009a3b18 fffff800`1117de3b : netft+0x2516
fffff880`009a3870 fffff800`10a96655 : fffff880`009a3ab0 fffff800`10a97cff fffff880`00991f00 fffff880`009934e0 : nt!KeDelayExecutionThread+0x1a0a
fffff880`009a39a0 fffff800`10a98668 : fffff880`0098f180 fffff880`00991f80 00000000`00000001 00000000`06591183 : nt!memset+0x1be5
fffff880`009a3a40 fffff800`10a97a06 : 000006b1`f05f995d fffffa80`c25da010 000006b1`f05f995d fffff880`009a3b4c : nt!KeQueryInterruptTimePrecise+0x188
fffff880`009a3af0 fffff800`10a989ba : fffff880`0098f180 fffff880`0098f180 00000000`00000000 fffff880`0099b140 : nt!KeDelayExecutionThread+0x1226
fffff880`009a3c60 00000000`00000000 : fffff880`009a4000 fffff880`0099e000 00000000`00000000 00000000`00000000 : nt!KeQueryInterruptTimePrecise+0x4da

STACK_COMMAND:  kb

FOLLOWUP_IP:
netft+2845
fffff880`0591c845 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  netft+2845

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  netft.sys

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}

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

Has anyone exprienced an issue like this?

Regards,

Dinko

Hi

I have a laptop running Windows 8.1. This hosts a hyper-v guest running Windows Server 2012 x64 Standard. From the host I, go to Control Panel\Network and Internet\ Network Connections. I right-click my ethernet connection, right-click and select properties. I click the Sharing tab and enable connection sharing. I then start my guest VM and connect to it using remote desktop. At this point all is good, the guest has internet access. However the problem comes, if I close the lid on my laptop to put it into hibernation. When I wake the laptop by opening the lid, the remote desktop session continues to run and I can work on the guest but it has lost its internet connection. The only way I can seem to get it back is to reboot then guest - then all is good again.

Does any know if it's possible to avoid the need for a reboot of the guest following a hibernate on the host?

Thanks,

Rob.

This guide is based on the following 3 products:
Windows server 2012 (core)
Windows 8
Hyper-V server v3 / Hyper-V server 2012

The following guide will enable you to:

1: remotely manage your Hyper-V Virtual Machines with Hyper-V manager
2: remotely manage your Hyper-V servers' firewall with a MMC snap-in.
3: remotely manage your Hyper-V server (2012) with server manager

! This should also work for Core installations of server 2012, but I haven't tried.

This guide is purely focussed on servers in a WORKGROUP, or as a stand alone.
I CAN NOT tell you what you need to do to get it working in a domain.


* You can run these commands straight from the console (Physically at the machine) or through RDP.
* You will need to be logged on as an administrator.
* Commands are listed in somewhat random order; I do however advise to follow the steps as listed.
* Commands with ? in front of them are only ment to be helpfull for troubleshooting,
* and to identify settings and changes made.
* Commands and instructions with ! in front of them are mandatory.

- server: means the server core or hyper-v server (non gui)
- client: means the machine you want to use for remote administration.
- Some commands are spread over 2 lines; be sure to copy the full syntax.

> To enable the Hyper-V manager to connect to your server, you need to perform the following 2 actions: (Assuming you have already installed the feature)

1:
! Client: Locate the C:\Windows\System32\Drivers\etc\hosts file.
! right-click --> properties --> security
! click --> edit --> add --> YOURUSERNAME or Administrator --> OK
! then select this new user, and tick the "modify"-box under the "allow"-section.
! apply the change, and close.
! doubleclick the file, and open with notepad
! add the ip-address and name of your server (no // or other crap needed)
! Save the file
# I recommend putting a shortcut to this file on the desktop.
# If you change the ip-address of your server (e.g. move the server from staging to a live environment)
# you might forget to do so in the hosts file.
# Hyper-V manager, MMC, RSAT, and Server-manager all rely on the hosts-file to resolve the name.
# some of these might connect to their respective service on an i.p.-level, but some don't.
# This is the main reason you need to modify this file.

! USE AN ELEVATED CMD/POWERSHELL PROMPT TO CONTINUE !
# the next config needs to be done on windows 8.
# It seems that it's already preconfigured under server 2012

2:
! Client: dcomcnfg
! open component services --> computers
! right-click -> my computer -> properties
! select "COM SECURITY" tab
! under "ACCESS PERMISSIONS" select "edit limits"
! select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
# Without this adjustment, you can't connect to your Hyper-V server
# with the Hyper-V manager if you're not in a domain.

> And if you haven't done so already... make sure you have enabled remote management number 4 on the Hyper-V server console.
----------------------------------------------------------------------


> Next, is to get the MMC firewall snap-in working.
   The reason for this, is to have a GUI available to configure it.
   If you're happy without it, you may skip this and use a shell instead to do so.

? server: netsh advfirewall show currentprofile
# shows the current profile (public/domain/private) and its settings
# depending on your needs, you should set the right profile to fit your needs.
# You can easily do this when the MMC snap-in is done. (after you've followed these steps)

! server: netsh advfirewall set currentprofile settings remotemanagement enable
# enables remote management of the firewall on an application level 
# (In other words: allows the firewall to be remotely managed)

! server: netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
# allows remote management of the firewall, through the required firewall ports with TCP protocol.
# 4 rules will be updated to allow access: public & Domain, dynamic and endpoint-mapper.
# You can disable/add/change the rule from the MMC snap-in after finishing this guide.
# e.g. set the firewall through the MMC-GUI to only allow specific ip-addresses etc.

? server: netsh advfirewall firewall show rule all
# Shows a list of available rules, and their current state.
# when run from cmd, the list exceeds the maximum length for review.
# (from cmd,type:) start powershell, and run the command from there.

! Client: cmdkey /add:YOURSERVERNAME /user:USERNAMEONTHESERVER /pass:THEPASSWORDOFTHATUSER
# I recommend you to use a username with enough privileges for management
# All capital letters need to be replaced with your input
# CMD answers "credential added successfully" when you're done

! Client: locate MMC, and run it as an admin.
# In windows 8/2012, go to search and type MMC. Right-click the icon, 
# and choose run as admin on the bar below.

! Client: application MMC: select "file" --> Add/remove snap-in 
! --> (left pane) scroll down to "windows firewall" --> select and click "add"
! select "another computer"
! type the name of the server you want to manage (NO workgroup/ or //, just same name as you typed for cmdkey)

* Part 2 is done.
# Have a look by doubleclicking the firewall icon in the left pane.
# It looks and works the same as the GUI version that you are familiar with.

-------------------------------------------------------------------------------

! Next is the Server Manager.
# Follow the steps listed to get your server listed and manageable in the server manager.


! Client: Open the created Firewall snap-in for your server.
! Find the 3 "Remote Event Log Management" entries in the list of INBOUND rules, and enable them.

! Open powershell --> in cmd windows, type: start powershell
! run the following line in powershell
! Client: in C:\Windows\system32> set-item WSMAN:\localhost\client\trustedhosts -value YOURSERVERNAME -concatenate

# WinRM Security Configuration.
# This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
# authenticated. The client might send credential information to these computers. Are you sure that you want to modify
# this list?
# [Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): y
#
# I recommend to choose yes; unless you like to pull some more hairs...

! server: winrm qc
# WinRM service is already running on this machine.
# WinRM is not set up to allow remote access to this machine for management.
# The following changes must be made:
# Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely
# to local users.
# Make the changes? y / n
!  select yes

! Client: open the server 2012 server manager
! click manage -> add server
! select the DNS tab, and type the name of your server

Done.

You can now manage your remote server through the familiar computer management GUI.

! Right-click your remote server, and select "Computer Management"

--------------------------------------------------------------------------

A few side notes:

? The Performance tab seems to list the local machine's performance, in stead of the remote servers'
? If you want Windows server backup, you need to right-click the server in the server manager, and select "add roles and features.
? it will then become available under the "computer management" of the remote server.


If you liked this guide you may thank my employer, Mr. Chris W.
for giving me the time to work it all out.

Cheers!

Hi there,

I have an issue with TMG 2010 on Hyper-V 2012 - the Setup:

- Windows 2012 Hyper-V

- TMG 2010 SP2 Rollup 4 running on W2K8 R2

TMG 2010 (Array Node1) Network
Internal Interface: 10.0.0.10/24 (Route to 192.168.11.0/24 over 10.0.0.1)
IntraArray: 192.168.10.10/24
Perimeter: 10.0.60.10/24 GW 10.0.60.100

TMG 2010 (Array Node2) Network
Internal Interface: 10.0.0.11/24 (Route to 192.168.11.0/24 over 10.0.0.1)
IntraArray: 192.168.10.11/24
Perimeter: 10.0.60.11/24 GW 10.0.60.100

Domain Controllers:
192.168.11.10
192.168.11.11

The NICs of the TMG VMs are configured with the correct VLANs and on the Perimeter Interface as well as on the Internal Interface I activate MAC Address Spoofing.

Once I activate NLB on the Perimeter Interface all works fine. But NLB on the internal Interface does not work - I see that NLB got configured on Array Node 1 but the second one does not get the config nor is able to sync it´s configuration with Array Node 1. ALso the Servers are not able to communicate with the Domain Controllers anymore. Once I deactivate MAC Address Spoofing on the internal Interface and remove NLB the Server are able to speak to the Domain Controllers...

Any suggestions?

Hi,

We have a Dell Server with 12 processors and 256GB RAM.

Installed Hyper-V server 2012 R2 as the host OS and configured 10 VM's with windows server 2008 R2 and 2012 as the guest OS using Hyper-V Manager.

Everything was fine till yesterday... but few servers are running pretty slow,so checked one of the VM guest.it shows memory utilization as 80%.

How and where do I check the all the VM guest and host servers processor and memory utilization ?

I checked this blog http://blogs.msdn.com/b/tvoellm/archive/2009/04/23/monitoring-hyper-v-performance.aspx. In the blog, there is mention on performance counters,but I could not figure out how to monitor or get the details of those counters for review purpose. what tools should we use or need to enable any settings in the hyper-v manager .

Wanted to know ,is there anything I need to enable to monitor those and will that affect the presently running nature of VM's and Host server ?

Thanks.

I am having trouble deciding if I should go with SUM or MIN mode.  Here is my config info:

2 Dell R620 host servers - Each server has 128G RAM, 12 NICs, 2 CPUs.
Here is the result of the processor script:
PS C:\Windows\system32> Get-WmiObject -Class win32_processor | format-table -Property NumberOfCores, NumberOfLogicalProcessors -AutoSize

NumberOfCores NumberOfLogicalProcessors
------------- -------------------------
            6                        12
            6                        12

I am using 2 of the NIC ports of each server for dedicated iSCSI to my EQL.  The other 10 are in a team.  The team settings are currently Switch Independent and Address Hash, No Standby adapter.

I tried Load balancing mode: Hyper V Port (SUM mode) but kept getting errors in my event log about overlapping.  It seems like SUM mode is the best way to go but how can I properly set up 10 NICs with the 2 processors (6 cores and 12 logical processors each) to not overlap?

Is it even worth using VMQ with just 2 host servers?  We plan on eventually running about 6-8 VMs on each host.  Also someone told me that Live Migration only uses the first NIC port, even if they are teamed, to move VMs if you are in a 2 node cluster.  I'm not sure if this is true but in Task Manager, the network activity never goes much above 1G when migrating 3 VMs simultaneously.

Some additional info on our v-nics and vlans:
PS C:\Windows\system32> Get-VMNetworkAdapterVlan

VMName                VMNetworkAdapterName Mode     VlanList
------                -------------------- ----     --------
                        LiveMigration                      Access     102
                        Cluster                               Access     101
                        Management                       Access      90
BaseInstall-2012R2Std   Network Adapter     Untagged
BPD-IT7                 Network Adapter            Untagged

The minimum bandwidth QOS weights are LM = 25, Cluster = 25 and Mgmt = 15

I have the VM traffic using the v-switch that these v-nics are assigned to.  I have the "DefaultFlowMinimumBandwidthWeight" set on the switch to 35. 

Thanks for any help.

Hello i have a bad issue with HyperV and my VM

Let me explain from the start: We shut down a virtual machine to delete a Snapshot with Hyper V Virtual Manager. So the process begins but stops at 48%, not enough disk space ! We stopped the automatic merge and took another snapshot, which we interrupted at some point (dont ask me why).

Then we exported the VM to an attached NAS to merge the avhd manually, i now have 2 ahvd and vhd File. If i merge the latest to avhd as written here: http://itproctology.blogspot.ch/2008/06/how-to-manually-merge-hyper-v-snapshots.html
i cant connect the 2 "vhds" with eachother, it comes up with an error "Invalid parameter" when i try to reconnect.

If i start the VM i get an error with the broken chain sth like this:

Somehow its still trying to do an automatic merge in the background iof the Hyperv Manager, expecially if i start the VM, how can i stop this?

Any help is really appreciated

Best regards

Hello,

I have a Windows Server 2012 lab environment set up. In this I have one Domain Controller. Within this I am running Hyper-V. The network set-up seems to be perfect. However when I attempt to connect a virtual client to my physical domain controller it fails. The only time it doesn't fail is if I turn off IPv6 on the client machine. It doesn't matter if I turn it off on the server.

Thank you in advance,

Maksim Richards

Hello All,

This is my first post here, but I have used these forums many times for information. Sorry in advance for the long post.

I have a few questions regarding migration to Hyper-V server 2012 for my production environment. I have done quite a bit of reading, but I have a few direct questions and I would like to get some direct answers.

My current production environment consists of one PowerEdge 2900 with 2 Xeon X5460 Quad Core 3.16GHz CPUs, 24 GB of RAM and a RAID 10 consisting of 8, 500 GB HDDs for a total of 2TB of storage. I am currently running Server 2008 R2 Enterprise w/ GUI as the Hyper-V host OS. I have 4 virtual machines all also running Server 2008 R2 Enterprise. The 4 virtual machines consist of 1 domain controller, 1 Exchange Server with Exchange 2010 Standard, 1 Server running SharePoint 2010 Enterprise and the remaining server running IIS with FTP and HTTP.

The network topology is as follows….

Hopefully it is clear from my diagram that the Hyper-V host OS is connected to the same physical network as the domain, but is not a joined to the domain. I set it up this way because I had concerns about connectivity and manageability because the domain controller is a guest VM. Also, the IIS server is on a completely different physical network independent of the domain.

What I would like to accomplish is the migration of the above environment to Hyper-V Server 2012 as is. I want to keep my existing guest VMs unchanged and running Server 2008 R2 for now as well as keep the existing network topology intact.

I have 3 additional servers in a separate test environment that would be able to serve as temporary storage or whatever is needed for the migration process.

Here are the two main things I would like to accomplish with this migration…

1. Make the transition from Server 2008 R2 to Hyper-V Server 2012 as a host OS.

2. Migrate virtual hard disks from .VHD to the new .VHDX format.

All that being said, I have finally come to my questions regarding this process.

First and foremost, I would obviously need to back up my current setup in case something goes horribly wrong during the migration. My question regarding the initial backup is would it be better to do a bare metal backup of the Hyper-V host or should I do individual backups (bare-metal?) of the Guest VMs from within their operating systems?

Second, since I plan to use Hyper-V Server 2012, I will have to manage the host OS using the RSAT from a domain joined client running Windows 7 Professional. How much of a pain is it going to be to setup RSAT and manage the non-domain joined host from a domain joined client? Is there a better way without using SCVMM or using Server 2012 w/ a GUI as the host OS?

Third, are there any concerns I should have, precautions I should take or procedures I need to do before, during or after the migration regarding the existing VMs and the new virtualized hardware environment on the same physical host?

Forth, should I use the trial version of SCVMM 2012 SP1 (or another previous version) to perform the migration? What should I be aware of using SCVMM for the migration and then discontinuing its use after the migration is complete and moving to management using the RSAT?

Fifth, if I don’t use SCVMM for the migration, what is the best procedure for moving the VMs? Should I just copy the VHDs to a temporary storage location, install Hyper-V server 2012, copy the VHDs back, create new VMs and attach the VHDs or should I use the export/import process?

Number six, when is the best time to migrate the VHDs to VHDX format and what would be the best method?

And finally, do I need to worry about USN rollback with a single domain controller? From my reading, this seems to be a point of disagreement. Some people say it could happen while others say it won’t. Is there any point during the migration process where it could occur either during the copying of VHDs or from the switch to VHDX?

Again, sorry for the long post and thanks for staying with me this far. Any information would be much appreciated

Hello,

I have imported module "Import-Module MicrosoftIscsiTarget"  on Windows 2008 R2 - HyperV Enabled

Now when I run command "Get-IscsiServerTarget", I get below error.

I am unable to find out the specific problem and "Google" also gives very little resource.

Please let me know for what wrong is happening.

=====================================================

=====================================================

Whereas command "iscsicli.exe listtargets" gives me output as shown below

=====================================================

=====================================================

Thanks.

I can use the Hyper-V Manager in Windows 8.1 to connect my newly installed Hyper-V Server 2012 R2 - everything fine.

However, I cannot use the Hyper-V Manager in Windows 7 and Windows Vista to connect the same Server.

It just shows "Connecting to Virtual Machine Management Service ..."
Then "The operation on computer 'HYPERV' failed." - HYPERV is the computer name of the Hyper-V Server Core 2012 R2.

At the Win 7 and Vista clients, run the script [cscript hvremote.wsf /target:hyperv /show] shows everything PASS except the below warning.

-------------------------------------------------------------------------------
1 warning or error was found in the configuration. Review the 
detailed output above to determine whether you need to take further action.
Summary is below.
 
1: You are attempting to connect to a newer version of Hyper-V. 
  While some remote management *may* be possible, you should use a 
  matching operating system version on the client for full 
  management capabilities.

-------------------------------------------------------------------------------

Run the script [cscript hvremote.wsf /show] at the Win 7 and Vista clients show everything fine.

Any help?
Thanks.

Hello,

I am new to Hyper-V. I installed Windows Server 2012 R2  Preview on a physical server and installed Hyper-V role on it.

I am trying to install Windows 2008 R2 on Hyper-V as a guest OS. 

From Hyper-V manager, I created a VM and supplied 2008 R2 ISO as a boot device.

Windows 2008 R2 ISO is bootable. I have used the same ISO on VMware and it works.

I connected the VM and powered on, but OS instalaltion doesn't start.

I get error " Boot Failed. EFI SCSI Device 1." Below is th screen capture.

How to fix this problem ?

How do I go to Hyper-v VM BIOS settings ?

How do I change the boot sequence for Hyper-V VM ?

Thanks ! Jayawardhane

I am running a home Server with 2012 R2 with the Hyper-V role installed, with about 5 Windows 8.1 VM's.  I'm trying to get RemoteFX working, here's my hardware config:

• E5-4610 Processor (Supports Slat)
• Nvidia GTX 770 (Driver supports WDDM 1.3 with direct X 11)
• Gigabyte GA-X79-UD5 (All bios virtual settings enabled)

When I install the Video card driver (tried different versions using windows 8 and windows 8.1 drivers) initially it shows me the checkbox to "Use this GPU with RemoteFX" However after a reboot it says no supported video cards are available.

Before the reboot after installing the driver when it shows the GPU is capable of remote FX, I am not able to add a RemoteFX 3d adapter to a virtual machine because it is greyed out.

After I reboot, if i uninstall and re-install the driver the GTX 770 is available to use again but I still cannot add the RemoteFX adapter to a virtual machine's hardware.

I have done the following:

1. Verified in DXdiags that the direct X version is 11
2. Verified in DXdiags that the driver model is WDDM 1.3
3. Verified the E5-4610 Proc supports Slat or Extended Page Tables
4. Enabled all the Virtualiztion VT-x settings in the Bios
5. Verified the video card is supported and certified in 2012 R2
6. Verified the Remote Desktop Virtualization Host Agent is started in Services.msc
7. Tried the newest and oldest video drivers for 8.1, and newest for windows 8
8. I am using Generation 1 vm's as i heard Generation 2 is having problems with RemoteFX
9. Tried Generatino 2 VM's, there is no option to add RemoteFX hardware
10. Tried a different GTX 550Ti video card, same issue
11. Performed all Windows updates for server 2012 R2

Please advise on the next steps to be taken to get RemoteFX working, or if any of the hardware I mentioned above does not support RemoteFX in 2012 R2.

Thanks.

Hi!

I have a dead hyper-v host, that managed by my VMM Server. I successfuly removed that host from cluster in VMM Console, but when I try to remove from managed hosts, I get error 2606: "unable to perform the job because one or more of the selected jobs are locked by another job".

In first, I tried to foce remove host from PowerShell:

remove-vmhost "host-1" –force

and expectedly got same error:

Remove-VMHost : Unable to perform the job because one or more of the selected objects are locked by another job. 
(Error ID: 2606)

Either cancel those running jobs, or wait for them to complete, before trying this action again.

To restart the job, run the following command:
PS> Restart-Job -Job (Get-VMMServer localhost | Get-Job | where { $_.ID -eq "{47ea5cd7-7825-4b9a-b1fa-47b282adc547}"})
At line:1 char:1+ Remove-VMHost DMZ-MIAC-N1 -force+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    + CategoryInfo          : ReadError: (:) [Remove-SCVMHost], CarmineExcepti   on    + FullyQualifiedErrorId : 2606,Microsoft.SystemCenter.VirtualMachineManage   r.Cmdlets.RemoveHostCmdlet

Then, I tried to define what object locks currently exist from KB2795040 and got an empty result.

What am I doing wrong? Please help!

Regards.

Evgeniy.

Hello.

I have a 2008 R2 Standard server running on a IBM 3650 M4 platform and I wish to convert this to a vm so that I can run this in my Hyper-V environment, but I'm running into some trouble as I do so.

I have used the latest version of "disk2vhd.exe" to create the vhdx-file and had no problems during this procedure, but when I create a new vm and attach the disk I will not boot.  The first and only thing that appears when started is a blinking prompt in top left corner.

The Hyper-V manager is running on a 2012 R2 Standard. 

Any help would be much appreciated.

My Hyper-v 2012 R2 host has the following configuration. 

PC: HP 3330 Micro Tower

RAM : 4GB

network adapter : 2

1. Realtek PCI GRE family ( integrated with motherboard)

2. 10/100 PCI Ethernet Adapter (external, brand: Tenda model : L8139D

 I have successfully inserted the PCI LAN card (Tenda) to the PCI slot. The problem is hyper -v 2012 R2 is not recognizing the external PCI LAN card, though it is working fine with the built-in Ethernet adapter ( Realtek). When I connect the network cable to that card Hyper-v shows nothing at " Available Network Adapters " option of " 8> Network Settings" menu. I have checked the card and  the cable with other machine and i also have tested the card with different operating system in this machine they are all working fine. Please help me. thanks in advance.   

Experts !

Windows 2012 R2 Cluster.

2 Physical NICs dedicated for Hyper-V data traffic. These two NICs are used to create a team using Windows teaming (Switch Independent + HyperV Port) and this teamed interface is used for HyperV Virtual Switch.

I am getting the below warning frequently.

Log Name:      System
Source:        Microsoft-Windows-MsLbfoSysEvtProvider
Date:          11/12/2013 1:37:55 AM
Event ID:      16945
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      MSHVCLUSTER6N1
Description:
MAC conflict: A port on the virtual switch has the same MAC as one of the underlying team members on Team Nic Microsoft Network Adapter Multiplexor Driver
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-MsLbfoSysEvtProvider" Guid="{387ed463-8b1b-42c9-9ef0-803fdfd5d94e}" EventSourceName="MsLbfoProvider" />
    <EventID Qualifiers="32768">16945</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-11T21:37:55.871565200Z" />
    <EventRecordID>4861</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="6100" />
    <Channel>System</Channel>
    <Computer>MSHVCLUSTER6N1.INSIDEVIRTUALIZATION.COM</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="DriverObject">
    </Data>
    <Data Name="Member">Microsoft Network Adapter Multiplexor Driver</Data>
  </EventData>
</Event>

And while checking the Interface and MAC, the warning is true.

name                                                                   MacAddress
----                                                                      ----------
MANAGEMENT                                                     00-17-A4-77-00-6E
HEARTBEAT                                                          00-17-A4-77-00-6C
Ethernet                                                             00-17-A4-77-00-6A
LIVEMIGRATION                                                  00-17-A4-77-00-68
DATA-2                                                                00-17-A4-77-00-66
DATA-1                                                                00-17-A4-77-00-64
vEthernet (HCT-PRODUCTION-LOGICAL-SWITCH)                   00-17-A4-77-00-66
DATA-TEAM                                                          00-17-A4-77-00-64

While I did the same configuration using SCVMM for my Windows 2012 HyperV clusters, the fabric was deployed from SCVMM and hence the team and the virtual switch was just one. In the similar way, How should I do this with out SCVMM ?

Cheers ! Shaba

Hi guys

I asked this question before, but i'm not sure i phrased it correctly. It is now extremely critical I find some kind of answer, so i though i'd try and break it down a bit more in a new thread. 

- Previously, in Windows 2008 R2, you could delegate per VM Hyper-V console permissions using AzMan. This worked great. 

- In 2012 R2 this does not seem to be possible. AzMan is now deprecated. Fine. I get this. 

- What is now possible is that a user be a member of the Hyper-V administrators groups, this grants console access to all VMs. All previous mechanisms of obtaining console access work using any user that is a member of this group. 

- If you wish to delegate console permissions that are granular to a single VM in 2012 R2, how do you do this? Is it even possible now?

- I am not using SCVMM, and will not be using SCVMM at any point in the future, although the real issue here is the scoping of permissions. So if SCVMM can do it somehow, it must be delegating permissions some how?

Thanks for your time. Really appreciate it. 

Hello All

Currently we have Hyper V server based on windows server 2008 R2.We are using Windows server backup to backup the host and the Guests VM s.Guest VM s  include Windows sbs 2008 , other windows 2008 R2 servers and windows  XP and windows 7 clients .

We have purchased a new physical server and planning to install windows server 2012 R2 , install the Hyper v server role and migrate all VM s from the old Hyper v server.

Our management has decided to use the  physical hard drives which are currently being used on the current Hyper v server  on the new hyper v server.

Based on the above information what would be the best method that we can take to get the migration completed? Can we use the current Hyper backup top extract data on the new hyper v server and then import the VM s onto the new server

what are the things that we need to be careful when it comes to Licensing ?

Many thanks

Dhanushka

Hello everyone, 

I am running Windows Server 2008 R2 Datacenter SP1 with Hyper-V. I kind of messed up and accidentally deleted a VM that had snapshots. Since this was a critical VM, I had to come up with a quick fix to get my network running again, and I created a new VM. But since the original VM had snapshots the only way Hyper-V would let me start the VM was if I set the avhd as the hdd. I know this is not the right way to do things. The new VM is running fine though. How can I merge the original vhd and avhd? 

Any help is appreciated! Thanks!