Greetings,

I have a Windows Server 2012 R2 Standard VM running on Hyper-V (Windows Server 2012 R2 Datacenter). I'm attempting to activate Windows using Automatic Virtual Machine Activation as described here: https://technet.microsoft.com/en-us/library/dn303421.aspx. I'm getting the following error:

License Activation (slui.exe) failed with the following error code:
hr=0xC004FD02
Command-line arguments:
RuleId=a5b3220c-2d48-42e8-9733-0374090e4a25;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=f002931d-5536-4908-8d93-40ae584e24d6;NotificationInterval=120;Trigger=UserLogon;SessionId=2

It's running as a generation 1 VM, as I created it quickly and overlooked the generation. Here's the (redacted) output from slmgr /dlv:

Under Automatic VM Activation client information, the host machine name is the other node in the cluster (not the one it's currently running on). I don't think it matters but thought I'd mention it. Server Manager also shows "Not activated" for product activation. Any help would be appreciated, thanks!

I have been trying to upgrade our windows server 2012 installation that is running hyper-v, but have a problem with the physical nic. The issue is that upon finalising the upgrade, WinSer2012R2 presents a BSOD (IRQL_NOT_LESS_OR_EQUAL) and the only hardware device I cannot remove prior to the upgrade is the NIC so I assume this is giving me the grief.

I have tried to remove the NIC driver, but Hyper-V depends on it (all vPcs depend on it as well as a logical switch).

How can I remove the physical NIC? Is my only option to reconfigure all vPcs to have no NIC and delete the logical switches? This is a lot of work to reconfigure and error prone as well.

I would have checked log files for the boot, but for some reason, WinSer2012R2 does not create any log entries or memory dumps for me to look at. So all I have is the above mentioned BSOD hint.

Suggestions?

We are getting this error in Hyper-V Cluster Volume, and it is in failed state. 

Hyper-V Cluster is 2012 R2 with 3 nodes in the cluster, We haven't installed any antivirus in this, can someone please help me to get rid this issue.

I am having an odd issue with enabling replication between my Hyper-V hosts. We don't have a central CA so I am using a TechNet blog post "Hyper V Replica Certificate Based Authentication Makecert" (Sorry, my account has not been verified so I can't post links)

These steps have worked 100% on 4 of my Hyper-V hosts but I have 1 host that keeps giving me the following error:

"Hyper-V failed to enable replication.

Hyper-V failed to enable replication for virtual machine 'vsprdrec12': The certificate's CN name does not match the passed value. (0x800B070F).

The Replica server's name  for Hyper-V does not match the received certificate's subject common name (CN) or subject alternative name (DNS Name): The certificate's CN name does not match the passed value (0x800B010F)."

(Sorry again, account hasn't been verified so no screen shot of the error.)

The primary and the replica servers are set up exactly like my other primary and replica servers, but only this one gives me the error.  Anyone have any suggestions on a remedy of resources?

Hi,

I have a small customer who are utilising Hyper V 2012 R2 and would like to create a cluster.

They have 2 Hyper V hosts each having 6 1GB NICs installed and a Dell SAN running FreeNAS.

In the environment they have:

5 Windows VMs (1 x Exchange 2013, 1 x Lync Std, 1 x Lync Edge, 1 x DC, 1 x ARR Reverse Proxy)
4 Linux VMs
1 Physical DC.

For the networking I was thinking the below on each host:

2 x Server and Client vSwitch (Incl Management) Teamed. Their client and server are on the same VLAN, I have advised against this but they are happy with how it is!
2 x iSCSI Multipathed (Not Teamed)
1 x Live Migration
1 x Cluster Network

Would that be good utilisation of the NICs? For Exchange, I was going to put the DB/Logs on a separate VHDX. Not that its going to make that much difference as the SAN is one big RAID 6.

Any advice greatly appreciated.

I am installing Windows Server 2012 into Hyper-V for the first time.

I would like to know what to expect in doing so.

It installs from an ISO, that is expected.

When it boots up you put in the Password it goes back to ctrl-alt-delete and it just lets you do administrative functions and Task Manager, no Server Manager or Roles.

Is this what is to be expected of in Hyper-V?

I've recently replaced a PERC H310 RAID controller with a PERC H710p RAID controller on a Dell PowerEdge R820 running Windows Server 2012 R2 and started experiencing this problem. Everything I've investigated so far doesn't point to this being the issue, but wanted to mention it in case someone encountered something similar.

We were having terrible disk performance until the RAID card was swapped out, and as a precaution I moved all existing VMs off of this Hyper-V host server. Once everything was back up and running, I began a live migration back to the affected host server and it blue screened. Tried again and same result. I then tried copying the VM images manually through a UNC share and hit the same problem. It doesn't always happen at the same time during the copy. I've had blue screens happen 4-5 GB into a transfer, and 200 GB into a transfer.

I've updated the RAID controller driver and firmware to the latest available from Dell, and have installed the latest BIOS and chipset driver. The server has Broadcom 5720 series NICs, updated with the latest drivers and firmware provided by Dell. All Windows/Microsoft updates have been applied.

After all these firmware/driver updates the blue screens still kept occurring during network transfers. All the minidumps show a 0x133 DPC_watchdog_violation error, where the DPC time allotment is 500 ticks and the blue screens happening at 501 ticks. Running the minidumps through Windows Debugger pointed to tcpip.sys, netio.sys, and vmswitch.sys initially. Since tcpip.sys and netio.sys aren't typically the issue, I looked around for anything related to vmswitch.sys being the problem.

I disabled the Hyper-V vSwitch in the OS and did a transfer 100% successfully, with the traffic running through the same NIC the vSwitch was configured to use. Once I re-enabled the vSwitch and transferred more files......the blue screen came back.

In researching, I found reports of this issue when a Hyper-V host was using NIC Teaming. We don't have any of the NICs on this server teamed, but I figured it wouldn't hurt to apply the latest hotfix that addressed the issue.3031598 - even after applying it I was getting more bluescreens. I couldn't find a way to use the updated vmswitch.sys that came with the hotfix (6.3.9600.17714); I tried deleting and recreating the vSwitch, but the old driver (6.3.9600.16384) is what gets applied and searching the OS for an updated driver doesn't turn up anything. I also can't find any info online about manually updating the driver after applying a hotfix.

I'm fairly certain vmswitch.sys is the issue, but I don't know where to go from here. Are there any NIC or vSwitch settings I can adjust to help with this? Has anyone encountered a similar issue? Can anyone lend a hand in diagnosing this issue? I found some good resources on debugging and troubleshooting this issue further (2 URLs below), but this has gone from "this is a good learning experience" to "this needs to get done" in the few weeks I've been troubleshooting.

http://blogs.msdn.com/b/ntdebugging/archive/2012/12/07/determining-the-source-of-bug-check-0x133-dpc-watchdog-violation-errors-on-windows-server-2012.aspx

http://blogs.msdn.com/b/ntdebugging/archive/2009/12/11/test.aspx

All the minidump's from every time this has happened can be viewed here: http://1drv.ms/1R6CfAO.

Here are all the suspects from those minidumps:

I can't seem to get Hyper-V installed.

I am running Windows 8.1 Pro 64

Steps to reproduce:

1. Add/Remove Features

2. Add Hyper-V, and all subsets

3. Click OK.

4. Click Restart when prompted.

5. Computer will reboot and then work on configuring features.  At 91% the computer will stop and display the error message "Unable to add feature..." and then roll back entirely.

Does anyone have any ideas as to the cause and fix?

Thanks,

Daniel

Hi,

I have a small customer who are utilising Hyper V 2012 R2 and would like to create a cluster.

They have 2 Hyper V hosts each having 6 1GB NICs installed and a Dell SAN running FreeNAS.

In the environment they have:

5 Windows VMs (1 x Exchange 2013, 1 x Lync Std, 1 x Lync Edge, 1 x DC, 1 x ARR Reverse Proxy)
4 Linux VMs
1 Physical DC.

For the networking I was thinking the below on each host:

2 x Server and Client vSwitch (Incl Management) Teamed. Their client and server are on the same VLAN, I have advised against this but they are happy with how it is!
2 x iSCSI Multipathed (Not Teamed)
1 x Live Migration
1 x Cluster Network

Would that be good utilisation of the NICs? For Exchange, I was going to put the DB/Logs on a separate VHDX. Not that its going to make that much difference as the SAN is one big RAID 6.

Any advice greatly appreciated.

Hi,

I'm trying to rename a VM, and I've succeeded in all Fields, except on the name in the summary of the failover cluster (Zsap03 is the name I want and that is appearing in the menu and everywhere, and it is appearing Zsap03V1 on the virtual machine summary)

How is it possible to change it?

Note: I've changed on the Hyper-V Manager, on the failover cluster properties of that VM and also on the settings. I can't find anything else to find.

I turned on Hyper-V in Windows 2012 Standard so that I could install Windows 8.1 in a VM and test.  The first problem I had was that the VM could not get to the outside world.  I believe it had a 10.100.1.x address.  I changed the filtering setting on the virtual switch so that it could see the outside world and rebooted 8.1.  After reboot, it had a proper address and was able to see the outside world.  Today, though, most of the computers are getting 10.100.1.x addresses!  That means they don't work.  I have tried a number of things to no avail.  I just completely uninstalled hyper-v and rebooted the server.  I will be checking shortly to see if that fixed things.  Does Hyper-V have its own DHCP server?  If so, how do I turn it off?  I assume uninstalling will get rid of it, unless it is using the built-in Windows DHCP server in some weird way that is not showing up in the config. 

If that doesn't do it, what do I need to do to get things back to normal?

Thanks!

Hello.

We have Windows 2012 R2 Datacenter Hyper-V cluster. 4 of VMs are TMG servers (2 proxy/reverse proxy and 2 Exchange 2010 Edge with TMG). TMG server pairs included in NLB clusters.

On each Hyper-V node I enable network team (Dynamic mode) with SCVMM Logical Switch.

I try to enable VMQ on its nodes. All is okay, but 4 TMG VMs don't receive VMQ for NLB virtual adapters and lost connection thru NLB. Other NLBs (SharePoint, Exchange, AD RMS, CRL) work as expected. TMG VMs get VMQ only for 3rd, non-NLB adapter (TMG intra-array communication).

I try to disable VMQ on problem virtual adapter but without success.

Last Emulex network adapters firmware and drivers were installed. I also install KB3031598 on Hyper-V nodes.

I disable VMQ on physical adapters until another solution.

I have a Server 2012R2 host running a handful of VM's. Host configuration: i7 Core, 16GB RAM, System Disk C: 46GB free, Disk E: 906GB free, Disk F: 895GB free.

There are currently 7 small VM's running (mix of Debian and Server 2012), total 6912MB assigned memory, no dynamic memory is used.

When starting an 8th VM I get the error indicated in the title. Additional message: "The system was unable to create the memory contents file on 'E:\Hyper-V\....xxxx.bin' with the size of 1025MB. There is plenty of space on all disks and when I shutdown another VM, this VM starts just fine. The same goes with other combinations of VM's; there somehow is a limit a run into at about half the host physical memory size.
The eventlog has no additional entries related to this error (except the ones I already stated).

I did a chkdsk on the disk where the VM's are stored (no errors). A reboot of the host made no difference either. So, where else to look for a solution?

Hi,

We are having 4 Hyper-V Servers with Windows 2012 Datacenter. Taking weekly backup's of VM on a remote server through Veeam Backup & Replication.

Is there any way to backup Hyper-V host configuration which later can be used in case of server failure, re-installation or RAID controller failure.

Hello,

I am experiencing an intermittent issue with the backup of a Exchange 2013 VM. Normally, backups take less than an hour on both the Host and Exchange VM. The host is backed up first, then the Exchange VM several hours later. After x amount of days a backup will fail and the VM's status changes to Running-Critical with the backup still in progress. At this point it appears to create a 4KB AVHD and becomes inaccessible until that is merged back in. Looking in the event logs I can't see anything in particular that is triggering it, though I may not be looking in the right place. I get event IDs 18190 and 18200 at 5 minute intervals on the host during this period. On the VM the last events are that the virtual disk service has stopped and that the Exchange databases have been frozen by VSS. This is at the time the host backup takes place.

If left to it's own devices it will recover, though this can take over 48 hours. The Exchange VM will then carry on as normal and complete's its backup as if nothing has happened.

Setup:

Windows 2012 R2 Host with 3 VM's.

VM 1: Windows 2012 R2 with Exchange 2013cu7

VM 2 & VM 3 have no issues.

Windows Server Backup runs nightly on Host and Exchange VM.

Both Host and VM OS's are fully up to date.

Has anyone else had a similar issue? Or can point me in the right direction?

Scenario

I have a 3 Windows 2012 R2 Hyper-V hosts which is participating in a cluster, all of the virtual machines are hosted on CSV's. We also use Dynamic Memory for most of the servers

We do regular reboots every week for our virtual machines, but we've found that sometimes, a virtual guest will suddenly stop requesting additional memory.  At the time of writing, I have identified 10 machines - on different hosts, and even different clusters which are exhibiting this behaviour.  They're also running OS's ranging from Windows 7 to Windows 2008 R2 and Windows 2012.

I have selected one to demonstrate below.

Here, you can see the virtual machine is configured to use Dynamic Memory

and here, you can see that it's not actually demanding more than the start memory, despite the fact that I've overloaded the servers virtual memory by using MSPAINT.

Workaround

Rebooting the virtual machine does not resolve the issue, but live migrating the virtual machine from the host it is on to another host suddenly allows it to demand more memory.  One can then live-migrate it back to the original host and the problem is no longer there.

Troubleshooting

We have performed the following troubleshooting steps:

• Verified that the Integration Services are up-to-date (currently running 6.3.9600.16384)
• Verified that the virtual server has up-to-date Windows Updates
• Checked the Hyper-V-Worker\Admin event log on the current host - no errors pertaining to this VM.
• Verified that the Hyper-V host has sufficient RAM (currently only using 542 out of 768 GB)
• Checked the System event log on the virtual machine - nothing out of the ordinary to report.
• Verified that all services which start with the word "Hyper-V" on the guest machine is running.

Using the following command, I can easily identify which machines are affected (this command applies to SCVMM only):

Get-SCVirtualMachine | where {$_.DynamicMemoryEnabled -eq $true -and $_.DynamicMemoryDemandMB -eq $_.Memory} | ft Name,HostName,OperatingSystem,Memory,DynamicMemoryDemandMB,DynamicMemoryMinimumMB,DynamicMemoryMaximumMB

I do not know any diagnostic program which can give me more information regarding the memory status of a server - specifically one which can tell me more information about Memory demand, and why it's not working. 

Considering that the problem is resolved when I live migrate the affected machine, it would suggest that the issue is with the host, but as live migrating it back no longer exhibits the issue - that seems to negate that theory.  Additionally, the other 103 virtual machines which run on this host seem to not show this issue.

It's almost as if the machine is being ran with static memory, and Hyper-V doesn't realise it's dynamic, but the moment it's live migrated, it suddenly realises this and enables dynamic memory.

Any thoughts?

Hi 

We changed the MTU from 1500 to 1472 with HV VMs. We doubt whether need to change the MTU with HV host server NICs as well. If needed please help on the steps that we need to follow on interface as well on team 

Thanks in advance

LMS

Hello,

I have two Windows 2008 x64 servers, running Hyper-V.  I have about 15 VM's on each server.  I manage the VM's all through the Hyper-V Manager.  When I try to connect to Hyper-V Manager and manage my VM's I get "Connecting to Virtual Machine Management Service."  This times out after a few minutes and then the Hyper-V Manager displays:  The operation on computer 'localhost' failed.

This happens about 2-3 weeks after a reboot.  The only fix I have found is to reboot the server, but since these are production servers this is kind of a pain.

Hello everyone,

Using the "Copy Cluster Roles"-Wizard I'd like to migrate some VMs from one cluster to the other.
I did that quite often, but here comes the question:

Is it possible to use that wizard to migrate VMs from a cluster in domain A to a cluster in domain B, without having a trust relationship?

Best Regards,
Jens

jensit.wordpress.com

Good afternoon,

I am almost done with configuring a new Hypervisor running Windows Server 2012 R2. 

I have noticed that when comparing this server to the exisiting Windows Server 2012 Hypervisor, there are slight differences in the network area of things.

I have attached the screen shots with the differences to this post for your review. 

Network Connection Details On Current Hyper-V Server (Left) vsNetwork Connection Details On New Hyper-V Server (Right):

Why is the new server not showing any IPv4 WINS Servers and why is the NetBIOS over Tcpip not showing to be enabled?

I would prefer that the new server has the IPv4 WINS Server addresses displayed in the Network Connection Details.

I have checked the configuration for IPv4 on the current Hyper-V server and the server does not have any entries for WINS Servers and NetBIOS is set to default.

Network Connection View On Current Hyper-V Server (Left) vs Network Connection View On New Hyper-V Server (Right):

Why am I seeing both bridged NICS on the new Hyper-V server? I would prefer that the network connection displayed the network to which the server is connected to, just like you can see on the current Hyper-V Server.

The new server is on the network without problems. I am just interested as to why I am seeing these differences.

Please provide any suggestions that will be of help to me.

Thanks in advance!