I come from the ESX world but I am slowly falling in love with the simplicity of Hyper-v. I have a stack of dell c2100's I have been experimenting with. each have 2 1gb connections  teamed to a cisco switch. when testing bandwidth with a file copy I get around 240MBps. however if I add a hyper-v switch I max out at 90Mbps. worse than no teaming at all (112Mbps). 

team is with integrated broadcom nics, LACP and I can confirm I get full bandwidth between 2 2012 r2 machines until adding a hyper-v switch. removing the switch lets me transfer at full bandwidth but then I cant use Hyper-v guests.

my goal will eventually be to add dual port 10gb cards to 5 of the C2100's and run them in a cluster to host all my VM's in HA. I don't want to waist my money on the switch and nics until I can get what i have working correctly.

HDD speed is also not the issue as each has 12 3tb WD re4 drives with 2 Intel 250GB ssd as cache. they easily hold 3000MBps sustained.

I have one user who is having issues with Hyper-V on Windows 8.1. Anytime we create an external virtual network the host loses connectivity and the virtual network continues to say, "Identifying." I believe that Hyper-V is having trouble creating the virtual network. Here are some of the steps we've taken thus far:

• Removed the Hype-V feature and added it back
• Updated all the network drivers
• Disabled antivirus (Trend)
• Installed all recent Windows updates
• Disabled Windows Firewall
• Ran Hyper-V with elevated privileges

We are experiencing the same issue with the Wi-Fi connection. I've been using Hyper-V on Windows 8 for quite a while and haven't seen this issue before. Any suggestions would be much appreciated.

Host Name:                 SERVER1
OS Name:                   Microsoft Hyper-V Server 2012 R2
OS Version:                6.3.9600 N/A Build 9600
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Server
OS Build Type:             Multiprocessor Free
Registered Owner:          Windows User
Registered Organization:   
Product ID:                06401-029-0000043-76293
Original Install Date:     4/3/2014, 4:07:15 PM
System Boot Time:          5/4/2014, 1:56:47 PM
System Manufacturer:       Dell Inc.
System Model:              PowerEdge T420
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 45 Stepping 7 GenuineIntel ~2200 Mhz
BIOS Version:              Dell Inc. 2.1.2, 1/20/2014
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC-09:00) Alaska
Total Physical Memory:     32,723 MB
Available Physical Memory: 12,716 MB
Virtual Memory: Max Size:  37,587 MB
Virtual Memory: Available: 17,129 MB
Virtual Memory: In Use:    20,458 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    OIT
Logon Server:              \\SERVER1
Hotfix(s):                 31 Hotfix(s) Installed.
                           [01]: KB2843630
                           [02]: KB2862152
                           [03]: KB2868626
                           [04]: KB2876331
                           [05]: KB2883200
                           [06]: KB2884846
                           [07]: KB2887595
                           [08]: KB2892074
                           [09]: KB2893294
                           [10]: KB2894179
                           [11]: KB2898514
                           [12]: KB2898871
                           [13]: KB2901101
                           [14]: KB2901128
                           [15]: KB2903939
                           [16]: KB2904266
                           [17]: KB2908174
                           [18]: KB2909210
                           [19]: KB2911106
                           [20]: KB2913760
                           [21]: KB2916036
                           [22]: KB2917929
                           [23]: KB2919394
                           [24]: KB2919442
                           [25]: KB2922229
                           [26]: KB2923300
                           [27]: KB2923768
                           [28]: KB2928193
                           [29]: KB2928680
                           [30]: KB2930275
                           [31]: KB2939087
Network Card(s):           3 NIC(s) Installed.
                           [01]: Broadcom NetXtreme Gigabit Ethernet
                                 Connection Name: NIC1
                                 DHCP Enabled:    No
                                 IP address(es)
                           [02]: Broadcom NetXtreme Gigabit Ethernet
                                 Connection Name: NIC2
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.1.12
                                 IP address(es)
                                 [01]: 192.168.1.135
                                 [02]: fe80::915b:8de0:712e:29f1
                           [03]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (External NIC 1_Internal)
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.1.11
                                 [02]: fe80::2d35:f582:4958:9eb2
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

I have a PowerEdge T320 with 
Xeon E5-2420
16GB Ram
PERC H710 (512mb cache w/ batt)

2x SAS 10k 300gb RAID1

2x SATA 1TB 7200rpm RAID1

I also have 4 unused external hotswap HD bays as well with another pair of 1TBs I am going to use for backup data. 

System is to be DC/DHCP/DNS on one 2012R2 VM
File Server and all/any other roles on 2nd 2012R2 VM.


I was originally going to run ESX from dual internal SD but decided to stick with Hyper-V. 

With that change that means I'll have to put the Hyper-V host on a HD... 
This system should generally be pretty low I/O in general. Files to be served would be on the SATA 1TB array (which is low I/O). 

I was wondering if having the host/vm1/vm2 on the SAS array would be acceptable. Ideally I'd prefer them to be on separate array, and maybe I'll be able to do this in the future. I do have a 64gb SSD I could throw in to be a swap drive as well. 

Also wondering if the host should have its own 32gb partition in NTFS, and VM partition as something else. 

Any other tips and ideas would be welcome. 

Guys,

I have an issue with HyperV restored VM's not starting after restoring a VM via a secondary DPM 2010 to a Windows 2008 R2 SP1 DR cluster at a DR site,and I am wondering if the issue pertains to long filenames. The VM being protected by the primary DPM 2010 server sits on another HyperV Windows 2008 R2 SP1 cluster at the Primary site. I'll try to give as much information as to where I am with this:

After the restore of the VHD from the secondary DPM 2010 to one of the Cluster Nodes in the DR site, choosing a CSV location on the DR cluster for the restore location (which runs successfully) the path to the VM's configuration file is quite long i.e. C:\ClusterStorage\TEST\VMNAME_11-24-2011_11.47.48\C-Vol\ClusterStorage\Test\VMNAME\Virtual Machines\A05C6555-35A0-45A3-9098-3CAF58F4A79F.xml. When I try to start the VM I see get an error along the lines of :

"VM is unable to initialize. An Attempt to read or update Virtual Machine Confiuration Failed"

Which to be honest is not a lot of information.

To troubleshoot I:

1. looked at the security permissions on all the restored VM files and the VMGUID had the correct rights to all these files.

2.  I then started thinking it may be some sort of longfile issue so I copied the VM's .xml file to a folder I created at the root of the CSV i.e. c:\clusterstorage\VMName\A05C6555-35A0-45A3-9098-3CAF58F4A79F.xml

3. Then using mklink I created a link file to the to c:\clustestorage\VMName\A05C6555-35A0-45A3-9098-3CAF58F4A79F.xml

4. Then using ICACLS I added the VMGUID with requisite permissions to the link file in C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\A05C6555-35A0-45A3-9098-3CAF58F4A79F and the copied VM xml file at c:\clusterstorage\VMName\A05C6555-35A0-45A3-9098-3CAF58F4A79F.xml.

5.  I went back to HyperV Manger and the VM started this time.

Can anyone tell me if this is a known long file name issue with HyperV or is there something else amiss here as this is quite a drawn out process to complete?

Thanks in Advance,

Mark

It looks like there is a problem with the KB2920189 update.

When trying to install it via Windows Update on some servers, they all fails the installation of this update - they are all running 2012 R2 inside generation 2 Hyper-V machines.

Has this update been tested with the UEFI implementation inside Hyper-V?

The link to download Hyper-v is dead:

http://care.dlservice.microsoft.com/dl/download/F/7/D/F7DF966B-5C40-4674-9A32-D83D869A3244/9600.16384.WINBLUE_RTM.130821-1623_X64FRE_SERVERHYPERCORE_EN-US-IRM_SHV_X64FRE_EN-US_DV5.ISO

From here after registration:

http://technet.microsoft.com/en-us/evalcenter/dn528863?download=dlm3&url=http://care.dlservice.microsoft.com/dl/download/F/7/D/F7DF966B-5C40-4674-9A32-D83D869A3244/9600.16384.WINBLUE_RTM.130821-1623_X64FRE_SERVERHYPERCORE_EN-US-IRM_SHV_X64FRE_EN-US_DV5.ISO

Hi Folks,

I have  a Windows 2008R2 Hyper-V server with 20 guests.  They have been using a standard network adapter for 2 years.  Last night after running this months windows updates on a number of the guest VMs, each running Windows 2008R2 some of these adapters disappeared.  That is they are not visible in "network adapters" on the guest VM, the static IP configuration is gone and instead the VM had a dynamically assigned IP shown in IP config to a Microsoft VM bus network adapter #2.  The other machines that didn't have updates run on them and have adapters visible show a Microsoft VM bus network adapter.

I don't see anything obvious in event viewer.

I've done the basic "reinstall integration services" but it still doesn't show a configurable network adapter.

I've uninstalled the windows updates and "reinstalled integration services" no luck.

Does anyone have recommendations on next steps?

I'll update the post as I move forward.

Thanks,

Ivan

Ivan

Hi,

I have created a VHD using Disk2VHD tool and it is unable to boot. I have attached the VHD to new virtual machine and VM is keep getting the start-up repair wizard. When the VM booted for first time it displays a error mentioning that C:\Windows is corrupted and need to run chkdsk. 

I have run chkdsk /f option and it has corrected few errors. but the issue remains as it is. Further, I have run following commands from command prompt when the VM is booted from Windows server 2008 R2 DVD.

bootrec/fixmbr

bootrec/fixboot

bootrec/scanos - total identified windows installations: 0

bootrec/rebuildbcd - total identified windows installations: 0

nothing worked for me and I tried using hyper-v 2.0 and 3.0 as well. same issue appear every time.

another thing I have noticed is that the physical servers doesn't show a "System Reserved" partition when creating the VHD image. So, the VHD has only the C: partition. 

Could anyone give me a solution for this...??

Regards,

Thisaru Perera.

Hi Hyper V Guru,

I am trying to do inspect on the disk of my VM by right clicking the VM-> select settings -> Select Hard Drive -> and click on the Inspect. However I am encountering the error message: "An Error occurred attempting to connect to the virtual disk management service on computer 'localhost'. Cannot connect to the RPC service on computer 'localhost'. make sure your RPC service is running. what is actually the issue that happen?

Second query: how do I accurately confirm that my VM has no snapshot?

Third Query: if my disk is fixed vhd disk, is it possible to expand it? what are the best procedures and steps of doing this task? what I should notice properly before expanding? will there be any risk of expanding VHD? as this is our production exchange server and very critical, I am really worry of doing this.

Thanks for your attention.

Regards,

Henry

Dear All,

            Some of my nodes are showing abnormal behavior.  They are restarting every now and then.  I had updated the cluster nodes, but all updates were OS specific, there was nothing specific with respect to hardware update.  It started happening when I pushed Endpoint Protection client to the nodes.  Can it cause abnormal restart?

I have analyzed crash dumps and find out that following is causing the crash:

page_fault_in_nonpaged_area (nxup.sys)

anyone has any idea about this?

Thanks in advance.

Dear All,

            I am building a Hyper-V Failover cluster.  I have created two teamed interfaces which comprise of two physical NICs.  One team is assigned to Cluster Communication, Heartbeat and Live Migration.  The other teamed interface I plan to use is for Virtual Machines.  I have following questions with regards to configuring the virtual machines teamed interface:

1.  Since, virtual machines would be of different subnet on the host, what needs to be configured on the teamed interface in order for it to support multiple VLANs? what other settings on the vms would be required?

2. How would I be managing multiple VLANs on the host?

I am running a 8 node Hyper-V Failover Cluster.
The cluster has a management interface, a VM LAN virtual switch (not shared with management OS) and a iSCSI and two DMZ virtual switches.

The SCVMM server is also a VM running on this cluster.

The general problem is that a VM on a host cannot reach the host, and vice versa. Ping, WinRM for example.
This also means that SCVMM always has a not responding host. The one where it's VM is on at that moment.

The VLAN tags used is the same for the management interface and the VM's using the VM LAN virtual switch.
We set the VLAN ID for a VM in the VM's settings, and the VLAN ID for the management interface is set in the team properties.

The NIC is a QLogic QLE3242 with four VNICs per physical port. There is a team consisting of one VNIC of each physical port.
The management team is tagged to a specific VLAN ID. The VM LAN team is untagged since we do that in the VM settings.

All QLE3242's in the nodes are connected to a Cisco Nexus 5200 switch each, which is one logical swtich.
The switch is transparent. No VLAN tagging done there at all.

Could the VLAN tagging on the team be a problem? Meaning, would setting the VLAN ID on with Set-NetAdapter be better/wiser? And more importantly, resolve my issue?

Folks

I am looking into some best practices ; here is the scenario :

Multi Node hyper -V cluster
each machine had two pairs of teamed NIC cards ( 2 teams/server )
storage network is a separate SaS network and no iSCSI ; so we will have followings for remains :

• Cluster network
• Live Migration network
• Management network
• VM production traffic

Our goal is to have an efficient network , so we are going to dedicate one Teamed-NIC to our external network.
we end up having one more teamed-NIC per server to manage cluster , Live Migration and Management network.
we do have separate switches for management environment ; so what would be the best approach ?

My thought :

1-Create different virtual NICs for cluster/liveMigration and Management within Hyper-V ; these NICs will be usable
through management operating system as well.

2- Assign different IP subnets to each network

3- Connect last Teamed-NIC to management switches ; configure VLAN and QoS ; so that cluster traffic gets priority .

OR .. should I configure QoS through HyperV virtual switch ?

Any thoughts ? suggestions ?

Is there any way of enabling the DEP and CPU virtualization in BIOS without going to BIOS.

I have misplaced my BIOS password.

Dear All...........Would appreciate understanding of following:

What is the difference between Fabric Cluster and Fabric Management Cluster?

What virtual machines should be part of Fabric Cluster and Fabric Management Cluster respectively?

Thanks in advance.

i am trying to install and test out Hyper V Server 2012 as i have being a VMware ESXi user for a very long time now.

I have a HP Proliant Microserver with a 4 x 1TB HDDs Raid5 array running on a HP P212 Smart Array Controller, i also have a 32GB micro-sd installed in the server and a 128GB USB stick plugged in too

When i am trying to install a Hyper V Server 2012 on my HP Proliant Microserver, i always encounter this error message "No drivers are found" and i couldn't clicked Next and proceed on anymore.

When installing VMware ESXi 5.5, the installer could see all 3 of my storage options and i can choose to install the VMware ESXi onto any of the 3 storage options.

This fustrating problem have being stopping me from using Hyper V over ESXi for a long time now and i hope Microsoft can do something about this and this could potentially see alot of people switch over to Hyper V from ESXi or their virtualization needs and testing.

Maybe Microsoft can release a custom Hyper V server image for use with HP Proliant severs just like what HP is doing now with VMware ESXi ?

Dear All,
        I have created a Hyper-V Failover Cluster and I want you to confirm if the configuration I have done is okay and I have not missed

out anything that is mandatory for a Hyper-V Failover Cluster to work.  My configuration is below:

1. Presented Disks to servers, formatted and taken offline
2. Installed necessary features, such as failover clustering
3. Configured NIC Teaming
4. Created cluster, not adding storage at the time of creation
 - Added disks to the cluster
 - Added disks as CSV
 - Renamed disks to represent respective CSV volumes
 - Assigning each node a CSV volume
 - Configured quorum automatically which configured the disk witness
 - There were two networks so renamed them to Management and Cluster Communication
 - Exposed Management Network to Cluster and Clients
 - Exposed Cluster Communication Network to Cluster only
5. Installed Hyper-V
 - Changed Virtual Disks, Configuration and Snapshots Location
 - Assigned one CSV volume to each node
 - Configured External switch with allow management option checked

1. For minimum configuration, is this enough?

2. If I create a virtual machine and make it highly available from hyper-v console, would it be highly available and would live

migrate, etc.?

3. Are there any configuration changes required?

4. Please, suggest how it can be made better?

Thanks in advan

I have 2 2012 Hyper-V hosts in a failover cluster. I have 2 JBOD storage shelves. I am connected via 10GB from both Hyper-V hosts to the JBODS. I have 1 HDD in shelf 1 and 1 HDD in shelf 2 (for shelf redundency). I was thinking of making a mirrored space out of the JBODS, then bringing the the volume into CSV to store VHDs. Has anyone tried this? Will it work?

I have tested a little and I can successfully create the mirrored space, but fail over cluster mgr will not allow me to bring the disk in as available storage.

Thanks for you time