Hello there,

Is configuring a VM with two virtual NICs, connected to the same Hyper-V switch, and then teaming them up, worth anything? I know teaming inside a VM of vNICs connected to different Hyper-V switches associated with different physical NICs, makes sense for fail over purposes; but is there any gain to add more vNICs that are connected to the same Hyper-V switch, to a VM for more bandwidth throughput? 

Case in point: Hyper-V node with a 4 port NIC (one card with 4 ports), plus 2 NICs on board (used and configured for management and Live Migration); the 4 ports on the single card are team up and then assigned to a Hyper-V switch. If a VM is configured with more than one virtual NIC attached to this Hyper-V switch, and those vNICs are then teamed up, will that result in more network bandwidth for the VM?

What about creating two Hyper-V switches (each using a team of two network ports from the 4 port card) and then configuring the VM with two vNICs one from each of the Hyper-V switches, and them teaming both vNICs inside the VM; does that changes anything?

Thanks,

Hi,

I have 4 nodes hyper-v on windows 2012. When I do shutdown or reboot 1 node. it shuts down VMs , move them to another node, and start the VMs.

Is there a way to configure it to do live migration automatically when a host node is shutting down?

Thank you.

-Mehdi

I have a Hyper-V server set up but under roles and hyper-v it says I need to add a virtual machine. I go to my manager and I have the machine up and running but it does not recognize it. 

 i have hyper V inside host server the host server connect via ISCSI to storage now such storage  

crashed but the Hyper V machines still running and his case is running-Critical how i can save the VHD file in different location

I'm trying to install Hyper-V Server 2012 on one of our servers. After the first installation phase, the server reboots and gives me the "Initializing devices" screen. After this, the server reboots again and presents me with a screen with stop error 0xc0000017, and won't let me boot into the OS.

After much fiddling, I found out that installing Hyper-V Server 2012 while the server is in UEFI mode causes this error. When I install in BIOS mode, everything works fine. I can't find much about this stop error in combination with Hyper-V server on the internet.

Has anyone encountered this error before?

HI,

I'm planning a new lab environment and due to all sorts of reasons I have limited disk space available for the various (10+) machines. To overcome the disk space problems we're going to build the environment using differencing disks on Hyper-V 2012.

However, we want to keep the lab up-to-date with Windows Updates. I'd like to inject these updates into the parent disk and not have all the updates in the child disks of the various machines.

I have 2 questions about this scenario:

1. Is it at possible to use a non sysprepped disk as a parent disk (I've used differencing disks before but always worked from a sysprep image)?
2. If the above is possible the following question would be if it's possible to update the parent VHDX (or replace the parent VHDX with an updated version) without breaking the configuration of all the depending machines?

Hello,

I am seeing a strange situation where I cannot exceed 8 paths in a vfc guest and wanted to see if anyone else has seen this.

I have server 2012 parent with Hyper-v and connecting to a storage controllers which have 16 target ports. 8 nodes, 2 ports each.

I have a brocade dual fabric and connect a single initiator to 8 targets in a zone on each fabric. 

After enabling the zones I see on the parent 16 virtual ports in my qlogic qconvergedconsole on the Parent server. 8 on each HBA port. I go to my guest and I do not see a lun. I reboot the guest and check for a lun nothing.

After rebooting the server 2012, I check the vm and a lun is seen with 8 only paths. I check the parent and now I only see 4 virtual target ports per HBA.

I tried the same scenario with 4 node controllers and 4 target ports. Same behavior. 16 targets show up in HBA, after reboot of parent server only 8 ports.

Does Hyper-v have a hidden limit of only 8 paths and reduce the number of exposed virtual ports in the parent server?

Has anyone tried more than 8 paths and it work?

Thanks in advance.

I am not looking to team two network ports that are available to our Hyper-v virtual server, but rather I have a server co-located in another city which we want to repurpose as a Hyper-v host server.

Currently it has teamed NIC's.

Can the NIC team be made available inside to the virtual server or do I have to break the team in order for this to happen? (In which case I could team the virtual server, but not team the host server)

I am having a rather strange problem while live migrating VMs with no shared storage on Hyper-V 2012 (core version).

If I try to live migrate (LV) between two hosts it fails. The funny thing is this problem is rather intermittent. Sometimes LV does succeed. By the way, constrained Kerberos delegation has been configured for both CISF and MS Virtual System Migration Service.

Right now, however, if I live migrate to a CSV (cluster shared volume) on the same host and THEN live migrate to the other host, it succeeds! Why?

Scenario which fails:

1. Live Migrate a VM running on hyperv2’s local storage to hyperv4

Here is the error I get.

Scenario which succeeds:

1. Live Migrate a VM running on hyperv2’s local storage to hyperv2’s CSV (cluster shared volume) (same server, different storage), making it essentially storage migration.
2. Then live migrate the same VM running on hyperv2 to hyperv4

Can someone please help!

-Rajeev rajdude.com

I have an application on a Server 2012 Hosted 2008 R2 VM that performs roughly 1/5 the speed of the same application on a Server 2008 R2 hosted VM.  Because the application software is the same, I suspect this is due to differences in the environments.  Each machine is assigned 4 processors, the 2012 hosted VM has 48 GB RAM while the faster 2008 VM has 32 GB.  FWIW, the application is WSS 3.0 based and involves a timer job that loads data into a list.  I am getting 5 x the number of records per minute on the 2008 VM. SQL tracing is not showing me any long running queries.

Any tips on how I can confirm or rule out the VM?  The host server itself is mostly idle.

Hey,

I have 2 Windows Server 2012 Datacenter Edition servers running Hyper-V on them. On each host I have a server that I am trying to setup guest clustering for a fileserver and they both are sharing the drive via iSCSI. But when I try to create the cluster it fails on the forming cluster step. However when I have the nodes on the same Hyper-V host I am able to successfully create the cluster. When I had it working on one host I migrated the VM to the second host and the cluster service on that server failed. Any ideas on what it could be?

We did a clean rebuild of our Hyper-V environment just over 2 weeks ago.  3 HP DL360 G7 servers, two clustered with Failover Cluster Manager, the third is a stand-alone host for Dev/Staging servers.  The clustered pair were 2008R2, wiped, and installed Server 2012 fresh.  The stand-alone was an OS upgrade from 2008R2 to 2012.  While the servers were being rebuilt, we used the HP utility to update all the drivers/firmware/etc.  They are up-to-date on WinUpdates as of May 16th.  We came in last Monday to discover that one of the clustered Hyper-V hosts had issues over the weekend - VMs hosted on that host were all marked "Host Not Responding" in VMM, and the host was inaccessible via RDP entirely, and access at the KVM showed the server hardlocked.  However, all of the VMs running on the host were up and functioning.  Knowing that we were doing scheduled downtime this week, we chose to leave things as is.  Today, we came in to find the other host in the cluster had done the same exact thing, but again all VMs running on that host are up and working fine.  All production servers will be patched and rebooted this week for regular maintenance, but we'd like to avoid this issue occurring again in the future.  At the time of the initial host going unresponsive, the only error in the event log of the other host was below:

Log Name:      Microsoft-Windows-FailoverClustering/Diagnostic

Source:        Microsoft-Windows-FailoverClustering

Date:          5/27/2013 9:25:11 PM

Event ID:      2051

Task Category: None

Level:         Error

Keywords:     

User:          SYSTEM

Computer:      HOST.domain.com

Description: [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'

What is somewhat disturbing is that no VMs were migrated off at the failure, and we had no clean way to migrate the VMs off that were running on the failed host.  VMM doesn't allow us to migrate (option grayed out), and the remaining host (at the time) didn't see the cluster, so couldn't access those VMs in Failover Cluster Manager either.  Ping is successful to either host, but nothing past that.  SCOM flipped a heartbeat alert on the first host, but nothing past that in terms of alerts.  Have there been any fixes/updates released for Server 2012/Hyper-V hosts that we should be sure we grab when rebooting tomorrow night?  Anyone else experience something similar?  We can re-run the HP driver/firmware update utility to check again for updates of that sort while rebooting, but I want to make sure we cover all bases now so this doesn't happen again.  Any suggestions are appreciated.

Hi,

every wizard in hyper v manager that I run hangs, but it completes the action I guess it those not sent the confirmation that it is done, this happens with all the servers, if I try to create a VHD from a windows 7 machine it creates it and give's me an error that it already exists,  I think this started happening after I installed the CA,

all of the pc's/servers/users are auto enrolled with certificates

i'm ruining windows 8 and hyper v core 2012

Hi!

If we setup a new system with 2 Hyper-V hosts that are clustered they must be domain joined. We dont have a domain configured yet, since this is a new system. We only have 2 Hyper-V hosts. So to solve this, do I first create a Hyper-v node 1, install the Hyper-V role, then create a new vm, install the domain controller role on this vm. Then I join the Hyper-V node 1 to this domain. Install Hyper-V role om node 2 and join this to the domain, and then configure the Cluster feature ?

Thanks for reply.

Regards

Andreas

I’m going to use Hyper-V replica for disaster recovery of production environment. The system includes Navision on MS SQL 2008 R2 for around 35 users which I’m going to move to Virtual Machine (with separate SAS HDD volumes dedicated for SQL DB and Logs).

Just wander if anybody could help me find answer for following questions:

1. I know, Hyper- v replica requires some space for logs, do they have to be on the same volume as drive or could they be on completely different volume?
2. Can I use all space available on those hard drives for VHD file or do I need to leave some free space?
3. What will be replication performance impact on SQL server?
4. Do I have to use recovery point to make sure my SQL database is consistent? I read somewhere, recovery point has significant impact on server.
5. Any other advice about configuration?

Thank you

I have the following server setup:

-Storage Server, with an SMB file share
-hyper-v host 1
-hyper-v host 2

All three servers are in the same domain, and the VMs are hosted on the host servers but stored on the storage server. When I try to move a VM from one host to the other I get the following error message:

Virtual machine migration operation failed at migration source.

Failed to establish a connection with host 'host 2': No credentials are available in the security package (0x8009030E).

The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source host: no suitable credentials available. Make sure the operation is initiated on the source host of the migration, or the source host is configured to use Kerberos for the authentication of migration connections and Constrained Delegation is enabled for the host in Active Directory.

[Expanded Information]
Virtual machine migration operation for 'VM' failed at migration source 'host 1'. (Virtual machine ID .....)

The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'host 2': No credentials are available in the security package (0x8009030E).

Failed to authenticate the connection at the source host: no suitable credentials available.

All the servers already have constrained delegation enabled, with "use kerberos only" checked

Does anyone know what the problem is here?

Thanks

We are a vmware shop evaluating Hyper-V 2012 for the first time. I've done quite a few searches on this error, but have not been able to find a solution for this issue we are experiencing. Your help would be greatly appreciated.

We are running Hyper-V 2012 SP1 on two physical hosts with a separate machine running SCVMM and another running AD and DNS

When I use Hyper-V manager to enable replication for one of the vm sessions, I am able to get to the last part of the process, but when I click finish I am getting the following error:

Hyper-V failed to enable replication
Failed to perform the operation, the virtual machine is not in a valid state to perform the operation.
Hyper-V failed to enable replication
 for virtual machine 'vmtest1'; Operation Aborted (0x80004004)

The firewalls are disabled via GPOs,

Same error with and without snapshots on the VM

There is no media attached to the vm (CD/DVD set to none)

It does not matter if the vm is running or shut down

SPN's all check out

Using Kerberos on Port 80

Port 80 responds via telnet

The folder structure get's created on the destination (Hyper-V replica folder)

Using local disk

No NIC teaming setup

If you need any additional information just let me know. The replication piece is a critical feature for us to move forward with implementing Hyper-V

All,

I hope anyone can offer an answer.

We have a HA Windows 2012 Hyper-v Server cluster with an EqualLogic storage.

We have serveral machines running on passthrough disks with no issues. When I am trying to add a new VM with passthrough disk, the machine fails to start up with the error above.

Furthermore, the disk is showing as online on Storage Manager of the node (as well as on the Cluster Disks). When trying to set offline on Storage Manager, it reports:

"The specified disk or volume is managed by the Microsoft Failover Clustering component. The disk must be in cluster maintenance mode and the cluster resource must be online to perform this operation." Following this instructions did not make a difference and the VM still failed to start.

The process followed to add the passthrough disk to the clustered VM is as perhttp://alasdaircs.wordpress.com/2010/04/11/clustered-hyper-v/ (with the slight difference of creating the volume on the iSCSI) which has worked fine for all other VMs currently in production.

The disk appears in Cluster disks as C:\ClusterStorage\Volume2 as opposed to \\?\GLOBALROOT\...

Any ideas?

Just downloaded the updated version of MOC 20410 and none of the 8 vm's included will import.  I receive the following error (but note that {GUID}s are unique for each machine):

Failed to import a virtual machine

Import file format error: C:\Program Files\Microsoft Learning\20410\Drives\20410B-LON-CL1\Virtual Machines\{GUID}.exp

I get the same error for the remaining 7 machines:

LON-CL2, LON-DC1, LON-RTR, LON-CORE, LON-SVR1, LON-SVR2, LON-SVR3

I have to get this setup and imaged for a delivery of 24 students on June 10th

On a side note, I have been an MCT for many years and have delivered hundreds of classes that I have setup personally, so yes, I followed the HVS document! I am also responsible for the setup of classes at our training company and this is a show stopper.  I have seen some links referring to a <VALUE></VALUE> key that should be blank where <PROPERTY NAME="ScopeOfResidence" TYPE="string"> is found in the exp file, and these are already blank so the information athttp://support.microsoft.com/kb/968968?wa=wsignin1.0 is of no help.

Hi All,

With Hyper-V 2008 R2 installing Ubuntu 10.10, 11.04 and 11.10 used to work with no issues. The synthetic network driver worked and was stable.

However, we recently upgraded to a Hyper-V 2012 environment. Upon moving the exsting Ubuntu VMs (versions above) all kernel panic if the Synthetic NIC is loaded. If the legacy NIC is loaded the performance is appalling (pinging local gateway at over 2000ms).

A fresh install of those OSs also fails, with a kernel panic as soon as you include the synthetic network adapter in the VM profile. The legacy network adapter misbehaves on all of them and is not usable in production.

Note that Ubuntu 12 and 13 both work 100% fine on both Hyper-V 2008 R2 and Hyper-V 2012.

Ubuntu 10.10, 11.04, 11.10 work 100% fine on Hyper-V 2008 R2, but not on Hyper-V 2012.

We have some clients who need to run Ubuntu 10 or 11 and we have no way of continuing to provide them services using Hyper-V. Does anyone have a solution for this (please only answer if you have a tested solution, we run hundreds of VMs across many operating systems in clustered and non-clustered environments, so we know what we are doing)?

Thanks,

- Will