Hi,

I'm running Win10 in a Hyper-V VM on a Win10 host. I've set-up an 'external' virtual switch to allow the VM access to the local LAN. Within the VM I have an app that issues UDP broadcast messages that other devices on the LAN should pick up, however it seems they never get this UDP packet. When sent from the host OS it is fine. I've disabled firewall as well and tried setting MAC address spoofing, but to no avail. TCP traffic gets out to the LAN just fine.

This is something that works fine on VMWare, so any clues how I can get it working in Hyper-V?

Virtual switch settings:

• External (connected to host PC's main NIC)
• Allow management os to share this network adapter enabled
• Under extensions, both filtering platform and NDIS capture are off.

Thanks.

I have a new z170 chipset skylake 6500 16GB DDR4 system and have hyper-v turned on in my win 10 pro install.

The problem I have and clean reinstall does not make a diff. is when connecting to win 10 from another win 10 machine using the mouse to say, scroll in a web browser, will cause the RDP session to drop. It seems to be tied to mouse commands as using the keyboard appears fine. Scrolling clicking etc all tend to drop the connection and it is also random when using the mouse will do this.

Using RDP from an older OS such as windows 7 is also affected but to a lower degree. I do not seem to have this problem if I use remote desktop to connect to a windows 10 machine that does not have Hyper-v installed.

I have a Hyper-V host running 2012 R2, minimal interface. 

VMQ related Powershell command fails to display VMQ stats, but VMQ appears to be working based on further investigation:

I decided to add the GUI, run updates, delete all my virtual switches, reset advanced settings on NICs, install driver updates, recreate my virtual networking, and see if Get-NetAdapterVMQ or Get-NetAdapterVMQQueue started to display stats again.  No change..On the other hands, Get-NetAdapaterSRIOV correctly displays all the assigned VF's.  

Looking further:

First place I went to look was inside the configuration of the NIC, under advanced, virtualization, I checked how the VMQs and SR-IOV was divided up on each NIC.  33/30... so this wasn't the issue.  I could also see that VMQ's and VFs for SR-IOV were being correctly assigned to each VM.  Turn on and off VM, and I could see the Q's being assigned:

Inside the Hyper-V manager, I could see that VMQ (OK) was displayed and enabled for said VMs.  Within Event Viewer, there were no errors like I have seen on other hosts where VMQ was not being assigned to the VM:

This is very odd, in the past running Get-NetAdapterVMQ or Get-NetAdapterVMQQueue I could easily see all the stats for VMQ, but now the PS command is not doing it's job.

Any ideas? I'm concerned that things are not working correctly..

Hi all -

I was in two minds as to whether to post, having spent some considerable time on this already and feeling well and truly defeated! However, I figured it was worth a shot.

I recently upgraded my PC from Windows 8.1 to Windows 10.
Since doing so, I am unable to connect to and manage two Hyper-V Core 2012 installations we have at a remote site permanently connected to us via VPN. These servers are in a workgroup, and my PC is in a domain.

In Windows 8.1, adding the two Hyper-V servers to my local DNS Hosts file, adding "Remote Access" to ANONYMOUS LOGON under DCOM Access Permissions, configuring the trusted hosts under winrm and adding stored credentials for the two workgroup servers was all that was required to get things working.

In Windows 10, I've tried everything I can think of, plus a lot of suggestions found within these forums (and elsewhere). It seems Windows 10 Hyper-V management connects in a slightly different way to the old Windows 8.1 management tool. One interesting find was that port 5985 wasn't actually "open" to me connecting from here. Turns out the Hyper-V server was connected using a "Public" firewall profile, which restricts WINRM connectivity to local subnet only. Never an issue with Windows 8.1. However, modifying this rule still didn't resolve my issue. I got a different error message instead.

So, as it stands, if I run Windows 10 Hyper-V Management (directly from my domain account), I get the error:
"The operation on computer 'HV1' failed: WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer HV1. Verify that the computer exists on the network and that the name provided is spelled correctly."

I've tried using the "Connect as another user" option, but as I understand it, this functionality isn't supported with older versions of Hyper-V anyway. That said, if I do try to connect with the credentials for the local administrator account on the Hyper-V server, I get the message:
"You do not have the required permission to complete this task. Contact the administrator of the authorization policy for the computer 'HV1'."

I've also tried setting up a local account on my PC with the same username / password combo as the Hyper-V server, and running the management tool under that account. The results again are different. Using this approach, I get:

This is probably because it is seeing the username as MYCOMPUTER\username, rather than HV1\username.

Nevertheless, I'm stuck currently having to manage these servers via a Windows 8.1 installation I've done on our own Hyper-V server, as I cannot get Windows 10 to play nicely with it at all.

I would be extremely grateful for any suggestions as to how I might resolve this?
I also think Microsoft have a long way to go when it comes to Hyper-V Management tools. Even under Windows 8.1, it seemed to me that setting up remote management was a nightmare compared with alternate products, such as the VMWare products. I wish they'd address this and provide automation for setting up remote management tools and prepping the server for use of said tools.

Many thanks in advance!
Simon.

I've been asked to move this topic here from the Windows Insiders forum HERE

After performing an in-place upgrade from Win8.1 Pro to the current Insider build I am having issues with the networking (both PC and Hyper-V switch management).

After the upgrade I had initially no networking enabled:

Both Wired and Wireless adapter settings, while still enabled:



This was the case for MOST of the network devices.

After a good amount of attempts I was able to get both Ethernet and Wireless connections finally working.  However, I still have issues with the VM's connectivity.

Also, I am now unable to delete any Hyper-V Network switch that was created while in Win8.1.  Each time I try to delete the switch I generate the following error:



Does someone please give me a starting point to resolve this error.  Otherwise, my VM's will not have connectivity.

Thanks.

Gus

Hello,

I recently enabled jumbo frames inside a virtual machine and enabled jumbo frames on the physical network adapter assigned to that virtual machine. When I try to setup the icsi initiator it becomes unresponsive . When I disable jumbo frames within the VM everything works fine. I enabled jumbo the switch and on the DAS device. 

Hi,

I have a VM on hyper -v on 2012 R2. This had a checkpoint and I tried to delete it manually, but the merge failed due to insufficient storage. I have created enough storage. When I check the hard drive on the VM setting, get a message as checkpoint exists for this VM and I cannot Edit. But when I try to run get-vmsnapshot.. it does not show any checkpoint. I ran the remove checkpoint command. But on the setting the hard drive still shows cannot edit.

Is there something I'm missing.

Regards

I am experiencing an interesting problem with our Windows Server 2012 R2 three node cluster. On one of the nodes network connectivity tends to drop randomly for the virtual machines network interface. The associated network card on the affected node indicates a connected as well as all the virtual machines on the affected node. This only happens for the network attached to the production virtual network. Live migration and the CSV virtual networks never lose connectivity.

Rebooting the virtual machines does not resolve the problem. Only physically unplugging the affected network cable and plugging it back in resuming network connectivity.

All host are up to date via Cluster Aware Updating and the network card drivers are all current.

The frequency is totally random sometimes in between two days to two months between incidents.

Any thoughts on a cause?

Hi everyone:

    my problem is, after I installed the Linux mint 17 in windows 10 hyper-v, the mouse was invisible in the guest OS (Linux Mint 17). While the mouse really works, I can click the buttons in the guest OS, it's just invisible. anyone know what happened? I've tried to download the Hyper-v Linux integration services and tried to install it in Linux Mint and failed to do it. The setting of hyper-v shows that all the "integration services" are offered except the "guest services".

Hi,

We have an 11 x node Hyper-V 2012 Cluster.  I am in the process of installing additional software updates and hotfixes on all Hyper-V hosts.

We have a 2012 SQL Failover guest cluster with SAN attached storage using virtual HBAs.

The guest cluster node live migrated successfully.  However after the live migration the guest failed to write to one of the disks presented through vhbas and this caused the SQL cluster resource to failover to the other cluster node.

In the event log of the guest cluster node we received the following error:

Log Name:      Application
Source:        MSSQLSERVER
Event ID:      17053
Task Category: Server
Level:         Error
Description:
SQLServerLogMgr::LogWriter: Operating system error 170(The requested resource is in use.) encountered.

And the on the Hyper-V host we were live migrating the virtual machine to received the following error:

Log Name:      Microsoft-Windows-Hyper-V-SynthFc-Admin
Source:        Microsoft-Windows-Hyper-V-SynthFcVdev
Event ID:      32214
Task Category: None
Level:         Error
Description:
Failed to reserve LUN with Instance Path '' to virtual machine '' with error: The data is invalid. (0x8007000D). (Virtual machine ID )

The source Hyper-V host has the following hotfixes installed:

KB2806542
KB2823643
KB2832478
KB2838043
KB2840681
KB2853422
KB2878635
KB2894032
KB2894464
KB2913695

The destination Hyper-V host had the following hotfixes installed:

KB2806542
KB2823643
KB2832478
KB2838043
KB2840681
KB2853422
KB2878635
KB2894032
KB2894464
KB2913695
KB2916993
KB2928439
KB2929078
KB2929869
KB2996928

The storage array used to present the disks to the guest cluster node does support 2012 and ODX.

We are using HP BL460c Gen8 v2 Blades and HP 3PAR 7400 if that helps.

We have experienced this issue previously but it was on a storage array that did not support 2012 and ODX.

Thanks for your help in advance.

Emma

Hi,

Various versions of this question have been asked on the forums and a bunch of different solutions suggested. I've tried all of them but so far with no luck, and that includes saving and running the PS script to increase the TCP port range.

What I really don't understand is how I've got to this point. Everything was running just fine, I could access my Server 2012 R2 machine running Hyper-V from my Windows 10 desktops no problem. Then suddenly one day it stops working. NOTHING CHANGED in my config!

Hyper-V manager works fine locally, so if I RDP to the Server 2012 R2 box I can then bring up Hyper-V manager and launch a VM console etc. The issue is specifically across the network, ie. some sort of firewall problem. My group policy prevents me from simply turning off the firewall although of course I could change it locally for the server machine.

Does anyone have any ideas or ideally a step-by-step to solve this? I've getting 14050 precisely every 2 minutes, and the 10016 DCOM permissions message each time I reboot. I also have event 516 from the DFSN-Server precisely every hour in the "warning" log which in some way relates to namespace but I don't know if that's relevant.

Thanks in advance for your help.

Jeremy

Hi There,

Ive got a task to migrate the infrastructure form Xensever(6.1) to Hyper-V(2012R2) which has both Windows and Linux vms. Majority of the vms are Linux Family, RedHat and Centos. Ive been trying to attempt to migrate one vm to test and have been unsuccessful. I found out that the vm needs to be exported from Xenserver and a new vm provisioned in Hyper-v with the exported VHD disk attached should work but it is not working in my environment. I have SCVMM running in my project environment but I read on MS site its no longer support to migrate from Xenserver to Hyper-V directly on SCVMM 2012R2.

The vm hangs on at curser blinking as soon as the vm boots. I also read the Kernel needed amendments and I did them as perthe link but to no success.

Any help would be appreciated.

Thanks

Vikash

Hello,

After Configuring Virtual Fibre Channel for a CentOS 6.5 Hyper-v VM, WWN of the virtual HBA is available in Hyper-v Manager and FC Switch. Storage LUN access can also be configured successfully.

How to find the WWN at CentOS Hyper-v VM. - 'cat /sys/class/fc_host/host?/port_name' command seems to be not working.

Upgraded to latest LIS 4.0(Linux Intergration Services ), but no luck.

[root@suscentos ~]# cat /sys/class/fc_host/host?/port_name
cat: /sys/class/fc_host/host?/port_name: No such file or directory
[root@suscentos ~]#

[root@suscentos ~]# /sbin/modinfo hv_vmbus
filename:       /lib/modules/2.6.32-431.el6.x86_64/extra/microsoft-hyper-v/hv_vmbus.ko
version:        4.0.11
license:        GPL
srcversion:     E208FA12A913A74A87CBF37
alias:          acpi*:VMBus:*
alias:          acpi*:VMBUS:*
depends:
vermagic:       2.6.32-431.el6.x86_64 SMP mod_unload modversions
[root@suscentos ~]# /sbin/lsmod | grep hv
hv_netvsc              31022  0
hv_utils               13880  0
hv_storvsc             12677  2
hv_vmbus              282441  6 hyperv_keyboard,hid_hyperv,hv_netvsc,hv_utils,hyperv_fb,hv_storvsc
[root@suscentos ~]#

Is it possible to use host's Bluetooth network connection (tethered to my smartphone) on a VM? If yes, how?

When I try to create an External virtual switch in Hyper-V Manager->Virtual Switch Manager->Create Virtual Switch button, I only see my wired and 802.11 connections offered in 'External network' dropdown list.

I had a question for everyone regarding hyper-v sizing for guests and allocating cores..

In the past i think the rule of thumb was to not put more vm's on a given hyper-v server than cores.. so if it had 8 cores, 8 vm's max.. and if a vm required say 4 cores, then you were left with only 4, so 5 max worst case..

In some reading online it sounds as if that thinking no longer applies?

Case example of our new Hyper-V server.. 

I have a xeon e5-2650 v3 2.3 ghz 10 core.. two of them.. so 20 physical cores, 40 Hyper threaded..

I'm assuming HT doesnt count for much.. that said..

Taking the example of say virtualizing exchange, which i think requires a minimum of 4 cores.. I would assign 4 cores to that VM as an example... leaving 36 cores..

In the past i'd only assign more than 1 core to a vm if it needed it.. IE: for instance new 2012 R2 file servers, i still have set to 1 single core and often they even get hammered by DPM agents running sync tasks..

I thought i read that basically you could give the vm's more cores than you might need and it would only utilize what it needed..

So say i had 10 vm's all using 4 cores.. effectively using all 40 of whats "available", old thinking would say no more VM's should be added or assigned more cores, but I would think that depends on loading.. in our environment only 20-30 concurrent hits a time occur, even with one single core assigned, often i never see the vm go above 15%..

So if you have maxed out the spread of cores, or nearly maxed them out, is it still ok to assign more vm's counts higher than the default of 1?

Perhaps assign each vm 4 to start no matter what, for performance increases?

Any help on clarifying this would be great, thanks in advance

Tech, the Universe, Everything: http://tech-stew.com Just Plane Crazy http://flight-stew.com

I wanted to perform some long overdue maintenance on a hyper-v host.  My setup is two Win2008 R2 Core Hyper-V machines with local disk storage (no san, no virus protection on the hosts).  I powered down the Guest OS's,  exported them from  Virtual1 and copied the to Virtual2.   The guest OS came up and worked no problem on Virtual2.   Later on in the day I powered down Virtual2.  When virtual2 came back up 2 of the 3 guest VM's have disappeared from the management console.

Some items of note...

• There is no virus protection running on the hosts (others seem to have been having an issue with virus scanning).
• Event logs show the orderly shutdown of the guest VM's,  event logs then show only 1 of the machines turning back on.
• I see no useful errors in the event logs related to starting the machines back up
• There is a single event log entry for "Hyper-v failed creating a new partition (status 11)".  Although, there is plenty of free RAM & Disk space

Anyone have any idea what's going on?  I'm kind of baffled as where to even begin looking.

Thanks for any help,

-eric

Hi!

We need to move a Win 2008 R2 VM from a Win 2008 R2 Hyper-V server to a Win 2012 Hyper-V server. The VM has a pass through disk assigned with almost 1.5 TB data on it and some application installed. What is the proper way to move the data from this disk with the VM. Should we just copy the disk through hyper-v?

Thanks.

We have renamed the volume folder as supported here:

The volume folder name can be renamed, but the ClusterStorage folder cannot be renamed. An example of a path with a volume folder with a changed name is as follows:

C:\ClusterStorage\VMGroupA

https://technet.microsoft.com/en-us/library/dd630633%28v=WS.10%29.aspx#BKMK_paths

Everything is working well, we can reboot without problem. The issue occur when the connection to our iSCSI storage is lost (Mainly caused by a NIC issue).

When the Host is up, the cluster service is started and we are able to resolve the problem on the NICs. After the NICs problem resolved, the connections to the iSCSI storage is restored.

At this time, the cluster service rename itself the volume folders to Volume1 and Volume2... As read in another post, it seems the order of Volume1, Volume2... can change. (https://social.technet.microsoft.com/forums/windowsserver/en-US/269cfac1-e72a-4e10-a6c5-07e94c1f1732/ws2012-csvs-changed-volume-name-mount-point-and-need-to-fix)

Then, the VMs are failing to start with the message "at least one file is missing".

Why this rename occur?

To allow our VMs to runs, we have to rename the Volume folder as it was named before the lost of connection and everything is getting back to normal.

Additionally, before we renamed the volume folders, we tried to import the VMs using the Hyper-V manager because the VMs hosted on the automatically renamed volumes were disappeared from the list of VMs. All VMs still visible in in the Failover Cluster Manager with the "Fail" Status.

In this case, the import failed because some paths are adequately changed to the volume folder, some are not. It seems:

- the path of the VM files is not changed and remains with the post NIC failure volume foder name

- The HD paths are changed adequately with the automatically renamed volume folder

- The checkpoint folder is changed

- The Smart Paging folder is changed