Having an issue with my Hyper-V Core 2012 server as I plan to migrate my VMs to a MD3200i storage device.   When I restarted the server after installing the two 4p Intel I350-t NIC cards, 7 of the 8 ports appear in Network Settings in sconfig.cmd.  The 8th port isn't listed, just my original NIC team and 7 of the Intel ports.  Using DevManView I can see all 8 ports and I've even tried to enable the selected device and still it doesn't appear in sconfig.cmd.  I have tried a different cable to rule that out as well, but no luck.  I have also tried connecting the 8th NIC slot to different ports on the MD3200i and have determined it is definitely not the MD3200i but the NIC port on the server. 

What should I be looking at next as I can't seem to get his 1 port active and it's delaying me from moving forward with the MD3200i implementation?

Hi,

I've built a test cluster in my lab. The kit consists of:

2 Hosts (5 X 1GB nics each).

1 X 16 port switch

1 server with 2012R2 (has the iSCSI target installed.

1 VM on another host which acts as a DC/ DNS for the cluster.

 on each host server, nic allocation is as follows:

nic1 (USB): Management network (host 1:192.168.2.40, Host2: 192.168.2.41)

nic2&3 (team): VM Access Network (no ip as it's just a virtual switch)

nic4: iSCSI1 (Host1: 192.168.50.10, Host2: 192.168.51.10)

nic5: iSCSI2 (Host1: 192.168.50.20, Host2: 192.168.51.20)

MPIO is installed and configured. 

On the iSCSI target, I have 1 nic for the network and 2 nics for iSCSI (192.168.51.30, 192.168.50.30).

All three servers run Windows Server 2012R2 Enterprise and the two hosts have failover clustering and the hyper-v role installed. All the iSCSI traffic is VLAN'd on the same switch (VLAN50).

There is a Quorum disk on the iSCSI target and a CSV for Virtual Hard Disks. The Quorum disk shows on the owner as Drive Q. The CSV drives can only be seen in disk management or server manager>disks. on both hosts

To test I've created 2 HA VMs and live migrated VM's them between both hosts and that works fine.

I've powered down each host and the VMs come up on the other host(For example, VMs are on Host1 and I power it down. If I log onto host 2, they will then power up).

I've tested the teaming by removing 1 nic cable at a time and that's fine as well. I've tested MPIO/ iSCSI by removing 1 cable at a time and everything is ok.

The issue is as follows:

Scenario1: Disk Quorum Owner is Host 2, I have a running VM on host 1. If I unplug the cables from both iSCSI nics on host 1, Host2 goes offline (I can't ping or connect to it, VMs on Host 1 go off, VMs on Host 2 go off, failover clustering manager on host one cannot find the cluster). If I reboot Host 2, everything works fine. The VMs startup on Host1. Not sure why host2 goes offline. Can anyone please advise?

Scenario2: Disk Quorum Owner is Host 2 owner of data CSVs is Disk 2, I have a running VM on host 2. If I unplug the cables from both iSCSI nics on Host 2, Host2 does not go offline. Instad all CSVs and Quorum move to Host1 ( VMs on Host 1 run as normal, VMs on Host 2 run as normal, failover clustering manager on both hosts work as normal and the csvs are shown as mounted on host2). How is this possible/ is this expected behavior?

Thanks very much,

Regards,

HA

Hello,

Way back in 2008 when we configured our virtualized datacenter (used Virtual Iron, now defunct) it was recommended practice to use identical iscsi cards for all hostnodes.  We have since migrated to hyper-v 2008 r2, and are now moving on to hyper-v 2012 r2.  We are currently spec'ing out a new hostnode, and I'm looking for advice on whether it's still the recommended practice to keep all iscsi cards as similar as possible. 

The hosts will be connected to a MD3220i SAN.

The reason I'm asking is because we currently use Broadcom's 5709c's in all our hosts.  They have had their problems, so I'd like to move away from them.  Right now I have my eye on the Intel i350's.  It's a choice between the two since those are the only affordable offers we have.  I did a quick search online and found that Intel iscsi cards are much preferred over Broadcoms.  It's not in our budget to switch out all existing cards with intel's, so I'm wondering if it's now considered relatively safe practice to let iscsi cards from different manufacturers play together, since the technology has become more mature.  Any advice would be welcome.

Thanks in advance

hi , 

I have installed Windows 10 preview in my Hyper V using Windows 8.1.

 i have followed this steps in these urls

http://blog.credera.com/technology-insights/microsoft-solutions/using-your-windows-8-wireless-connection-inside-hyper-v/

http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/01/09/using-hyper-v-with-a-wireless-network-adapter.aspx

But the WiFI Isnt working in Windows 10 guest OS.

Im getting network as limited and its not working.

How i can set it up

Thanks

Thank You , Shan Ali Khan

Over the past couple of months I have experienced 4 dead 2008 R2 SP1 domain controllers after power failure on Hyper-V 2012 hosts. The domain controller VMs will start after power failure and have varying degrees of file system corruption. In each instance the corruption has rendered the domain controller unusable. The problem has not occurred with every power failure, but in testing the failure rate has been over 10%.

The Hyper-v 2012 hosts are as follows:

• Dell PowerEdge r720 with flash backed write cache on Raid controller
• Dell PowerEdge T710 with battery backed write cache on Raid controller
• Dell PowerEdge T310 with a single SATA hard drive and write cache disabled
• Generic system with a single SATA hard drive and write cache disabled

The VM configuration experiencing corruption is as follows:

• Each VM was created from a base 2008 R2 SP1 syspreped VHDx image template file (40 Gigs)
• The image template was originally created as a VHD and was then converted to a VHDx
• The VHDx file has 512k sectors instead of the native 512e of VHDx files (a result of VHD - VHDx conversion)
• Each VM was assigned 1024 Meg RAM and 1 virtual processor
• The domain controllers were created by promoting the base 2008 r2 install to a DC after base image deployment
• Only one corrupt VM was not running the 2012 integration components. The rest were running current 2012 integration components

I have done extensive testing on this issue and the problem for me seems to revolve around the VHDx file format. I have managed numerous Hyper-v installations since the original 2008 server version was released and I have never seen corruption like this until 2012 and VHDx.

For the past few days I have been testing fixed sized VHD VMs on a 2012 host and I have not been able to reproduce the data corruption issue. I seem to only be able to reproduce the problem when using dynamic VHDx files. I have not done any testing on 2012 hosts with fixed size VHDx files or dynamic VHD files.

It would be great to hear from anybody else experiencing similar issues so that we can compare notes and hopefully get to the bottom of this problem.

Hi,

I just setup a couple of Windows Server 2012 Hyper-V boxes and enabled the replica of a VM. All seems to work fine. These 2 boxes are connected to corporate LAN through a NIC and each other through a crossover cable over another NIC. As I can see, the replica trafic flows through corporate LAN. I'm trying to move it over the crossover lan, to save corporate bandwith for VMs, but I can't figure out how. I tryed to setup the replica using the IP address of the "crossed lan", but in this case the replica setup fails with a kerberos error (maybe because that lan is detected as public and not as a domain one). I've not tryed with certificate authentication, but this seems to me quite cumbersome considering that both servers are members of the same domain (Kerberos seems the smarter choice).

Has anyone ever tryed this kind of configuration ? What's the best thing to do ?

Thanks a lot.

Massimo Piceni.

We've got a couple of Windows 2012 / Hyper-V 3 clusters, and I have a problem with network adapters on them.

If the VM is powered off, and I move it to another host (quick migration via Failover Cluster Manager), the network adapter loses its connection to the virtual switch - it turns to "Configuration Error".

If it's powered on, both live migration and quick migration work fine.

It's possible to demonstrate on an empty VM. I created a new VM via the Failover Cluster Manager (ie not via Hyper-V manager on one of the nodes). One NIC, attached to the single VSwitch we have. Not much memory, disk. Don't need to install an OS.

Quick migrate with the power off, and it fails to pick up the VSwitch on the next host.

Turn it on, and live migration and quick migration both work fine.

Is this supposed to happen, or a buglet in 2012?

Hi frineds

i am looking for a link or document to find out the limitations of hyper-v in windows 8.1 in comparison with windows 2012 R2. but i was unable to find a good link.

may someone please help ? 

Vincent Sprague

Hi you all,

Totally excited about the Microsoft Hyper-V solution, but difficult to get started.

I'm looking for a good baseline Hyper-V solution for all those smaller companies.
Those companies who always have difficulty in spending money on IT.
I know there has to be a way to use Hyper-V in a Small-Businesses environment. But where to start?
Followed many MVA instructional movies, attended the Microsoft Teched 2014 in Barcelona etc.. but no where a baseline solution for this group of companies.

A few questions that come in mind:

-How to config an environment with the least amount of hardware, so minimizing total cost
-Local storage vs central storage?
-And which Raid setup to use then?
-Use of Windows 2012 Storage server?
-Or use Scale-Out-File-Server, but then again maybe already too expensive.
-What to do with backup? Where to put the offline backup such as tapes?
-Use Disaster Recovery to Microsoft Azure?

In other words WHERE TO START. There a too many options, but what are the best practices.
Are there some guidelines to follow to get this huge group of companies to use Virtualization based on Microsoft Hyper-V?

Someone can guide me? 

Thanks in advance!

Bas Janssen

Hi all,

I have been running Windows 8.1 and in Hyper-V Manager, i can see 2 VM ( 1 Linux-Ubuntu , 1 Win 7 ) for couple of months.

Few days ago as usual i wanted to connect one of them while they were running but it did not work. I tried actions below already:

- Checked the event logs and they were saying vmconnect is crashing

Faulting application name: VmConnect.exe, version: 6.3.9600.16384, time stamp: 0x5215cae5
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
Exception code: 0xe0434352
Fault offset: 0x0000000000008b9c
Faulting process id: 0x6c0
Faulting application start time: 0x01d02e59f75297d7
Faulting application path: C:\WINDOWS\system32\VmConnect.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: 351cf3fd-9a4d-11e4-beaf-7446a0bad879
Faulting package full name:
Faulting package-relative application ID:

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

Application: VmConnect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
Stack:
   at Microsoft.Virtualization.Client.Interop.IMsRdpClientNonScriptable3.set_NegotiateSecurityLayer(Boolean)
   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl.SetSecureModeOn()
   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl.CreateRdpClient(Boolean)
   at Microsoft.Virtualization.Client.InteractiveSession.RdpViewerControl..ctor(Microsoft.Virtualization.Client.InteractiveSession.RdpConnectionInfo)
   at Microsoft.Virtualization.Client.InteractiveSession.InteractiveSessionForm..ctor(Microsoft.Virtualization.Client.InteractiveSession.RdpConnectionInfo)
   at Microsoft.Virtualization.Client.InteractiveSession.VmisApplicationContext.TryParseCommandLine(System.String[])
   at Microsoft.Virtualization.Client.InteractiveSession.Program.Main(System.String[])

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

- Stop antivirus Avira, remove Hyper-V, restart add Hyper-V again, restart

- reboot, shutdown computer

- add new VM, delete existing one

-add/delete/modify virtual swtich and add/delete/modify virtual switch accordingly the connected VM

- restart Hyper-V Management services from services.msc

I dont know what is going on... When i open Hyper-V Manager i can start/stop VMs and i can see from preview that they are running.

Several months ago we got a call from a client with a standalone 2012 R2 HyperV host: Absolutely NO network traffic was going through any of the virtual switches, yet we could see no errors or warnings of any kind in any of the logs.  Desperate to get them back up and running we simply deleted all the virtual switches, recreated them (identical to what they were) and reattached all the VMs.  We chalked it up as a fluke....until today:the EXACT same thing happened to a completely different customer.

Clearly there is something systemic here which needs to be addressed.  I dont want to get another call in the middle of the night to have to recreate virtual switches.

Hugo Monge

Server 2012 R2 with Hyper-V stand-alone, no cluster. I created new virtual machine. When I rebooted host, I noticed that creation date of the VM becames wrong, something of 01/01/1601.

VM creation date does not persists between Hyper-V host reboots or restarting of the VMM service.

Hi

We have a Hyper-V 2012 3 node cluster, the VMs are stored on a Server 2012 based 2 node Scale Out File Server.

We created this setup from new in October 2013 and it has generally worked OK since but we do get the occasional "General Access Denied Error (0x80070005)" when we try to live migrate a virtual machine.  The instructions in the below TechNet article do not work for us - the result indicates success but when we try the Live Migration again we get the same error message.

http://support.microsoft.com/kb/2249906/en-gb

I have in the past resolved this by removing the virtual machine from Failover Cluster Manager, migrating it via Hyper-V Manager, logging on to the destination Hyper-V host and re-importing it to Failover Cluster Manager from there.

However last night I was doing some system maintenance and went to drain a host via Failover Cluster Manager.  The host had around 20 VMs on it and only two VMs successfully migrated - the other VMs did not migrate and now I cannot move them from that host for love nor money!

The Event Log for FCM indicates they have the "General Access Denied" error.

I have tried the following:

• Use instructions in above mentioned TechNet article (shows success, but same error happens when I try to Live Migrate)
• Tried the method I have mentioned above (removing from FCM etc.).  Get the Access Denied message
• Checking the folder permissions on the "Virtual Machines" folder where XMLs are stored.  Permissions appear OK for all Hyper-V hosts (also checked the VMs VHD permissions)
• Trying the Live Migration directly on Hyper-V host rather than via a Constrained Delegation scenario
• Checking Constrained Delegation in AD (seems fine as per when I set it up in October)
• Checking permissions on the Scale Out File Server

With regards to the Scale Out File Server I have noticed in the past some odd permissions things going on.  I have seen the permissions for the Hyper-V hosts going from (for example) "Full Access" on "This Folder, Subfolders & Files" to random things like " Read/Modify" on "This Folder Only".  Manually changing the permissions back to Full Control resolves the issue, but does not stop it recurring again.

So I'm a bit confused really!  It looks like a mixed basket of permissions issues going on!  Some of our most critical machines are on that host at the moment and they cannot be moved.  Any suggestions appreciated.

Many thanks

Dear Sir,

I am a new admin and have 5 Blade server "HP ProLiant BL660c Gen8".

I access these servers through HP enclosure.

I have to install Hyper-V on server 1 which consisted of the OS windows server 2012 R2 Datacenter edition.

I created a plan to create 5 Hyper-V VM's on the physical server and I requested the IT department network Admin that I want these 5 VM's to able to connect to each other.

The network Admin created a Trunking configuration on the physical server and after this setup he provided me Hyper-v node IP address and 5 more IP addresses for the 5 Hyper-v VM's.

Now it was left to me to Add the Hyper-v role and create 5 VM's.

While Adding the Hyper-V role, I was asked in the middle of the setup to add the network adapter for connecting to external network.

I went inside the network connection settings and I see one network adapter "Microsoft Multiplexer" which had the IP address of the Hyper-V node which was given  to be me by Network Admin.

Besides this I found following Network Adapter: (Mgmt,Trunk):(Mgmt A, Trunk A);(Mgmt B, Trunk B) =Total 6 Network Adapter out of which only "Mgmt" was configured with the IP address of the Hyper-v node given by my Network Admin. Remaining all other Network adapters IPV4 configuration was unchecked except "Mgmt" 

So I selected the "Mgmt" connection while Installing the Hyper-v role

SO I chose this Network connection for adding the Hyper-V role.

My question: Did I chose the correct Network Adapter.

After doing this I created a VM-1 and tried to assign the IP address given by the Network Admin. But the network Admin did not provide me the default gateway so I used the deafult gateway according to the IP address and used the last digit as "1" like a general installation.

Now my question is: 1.How can I use this VM to be used as a Virtual server?

2. I would like to open this VM through my browser by entering the IP address of this VM-1. How can I do this?

Because I access my physical server through the IP address. SO in the similar way I want to access this VM-1 through the IP address OR is there any alternate way to access this VM-1 separately.

My Requirement: I need to give VM-1 access to another admin to Install his application on it. SO how to give him to access this VM directly?

This is my main query.

Waiting for your reply.

Thanks & Regards,

Ahmed

I have a development environment on Hyper-v i want to be able to develop windows phone apps for this i need a Hyper v installation on my dev environment so i installed Hyper-v.

But if i start debuging the virtual hyper v says : The Virtual Machine Management Service failed to start the virtual machine 'Emulator 8.1 WVGA 4 inch.administrator' because one of the Hyper-V components is not running (Virtual machine ID)

can anybody help me out on this one as it looks all good. If i try to start the hyper v machine within hyper v i get the same error.

thanks in advance.

Check my website http://kbworks.nl or follow me on@KbWorks be sure to Check my SharePoint-Specialist.nu for dutch information workers check Wat Is microsoft SharePoint.nl for dutch readers who want to know what microsoft office365 is.

My company is moving heavily into virtualization.  We have about 50 HW servers and 2 HyperV 2008 single hosts.  I just built a pretty beefy Hyper-V 2012 clustered server and connected it to a brand new SAN.

I've read several articles before building the system to ensure that i follow those best practices, like this one.

http://blogs.technet.com/b/askpfeplat/archive/2013/03/10/windows-server-2012-hyper-v-best-practices-in-easy-checklist-form.aspx

The new system is running great.  It has a dedicated NIC for live migrations, which has been tested.

My questions are really about resource usage.  Determining how many virtual machines to put on one physical NIC, and how many virtual processors to give a virtual machine.  I found an article that described mathematically what my limits are for a single virtual server.  My server has 24 cores with 48 logical processors and 512 GB RAM.  

What i'm not sure of is how many virtual processors I should give a machine.  What I'm doing currently is starting small and just visually rating performance.  If the machine seems slow i turn it off and give it two more processors.  Does this sound like a good method?

Also, does anyone know how processor affinity work for HyperV.  I would assume that HyperV balances threads across all cores.  Or does it load up cores first them move to others.

Then there are the physical NICS.  The back end ISCSI nics for the SAn are 10G and isolated and HyperV isn't allowed to use them.  The front end NICS for the virtual servers are 1G.  I'm watching them for load, but they seem to be no where near saturated.  How many virts should I put on a single NIC?  Is it just based on saturation or are there other considerations?

Thanks,

I currently have 1 physical server with Server 2012 R2 Essentials, running Windows Server Backup to external HDD. Is there anyway to use this backup to rebuild the server onto new hardware with Hyper-V?

I've installed Server 2012 with Hyper-V on to the new hardware, booted a VM from an ISO on a USB and tried "Repair your computer" with the backup HDD attached but can't locate the system image. Am I missing something really simple?