Hello,

    I am trying to troubleshoot a slow network access to the outside world.  My Sophos UTM machine sits in a VM on a Windows Server 2012 R2 Server Core Hyper-V host with 3 NICs.  One NIC is for the host administration on the 192.168.1.x LAN switch along with all the other Hyper-V hosts.  The other two NICs are for the guest VMs, one connected to the ISP WAN, and the other connected to the internal network switch.  Prior to installing the VM with Sophos UTM I could use the Server Manager from one of the other servers to manage all the Hyper-V hosts.  After I installed the Sophos UTM software, Server Manager is unable to connect to the Hyper-V host that the VM is on.  I am able to RDP into the host, and have run Enable-NetFirewallRule -DisplayGroup "Windows Remote Management" and Enable-PSRemoting.  Server Manager has refreshed multiple times and shows Manageability as Online-Cannot get event data.  Trying to remote connect into the Hyper-V host with Event Viewer does not work either.  If I delete the VM, everything comes back to working fine, minus the internet connectivity.  This has not only happened to me with Sophos, I had the same issue with Windows Server 2008 and a TMG VM.  I would like to look over the logs to see if the network issues are related to Hyper-V or the hardware.

Michael R. Mastro II

Hi guys 

My Virtual Machine has stopped at 6% When i make Updates ...I do it Restart ..It's the same Action .

I can't login in my Virtual , Please tell me how we can solve this a big problem because this virtual machine is my DC .

Thank you . 

Hi all.

We are planning to configure a Hyper-v cluster with two nodes and use CSV on one SAN. This solution supposes that SAN will be a single point of failure. Only one CPD. We don´t want Hyper-V Replica

The solution should be purchase a second SAN and configure some mirroring type or SAN-to-SAN in order to replicate CSV. In this scenario:

1. Should each node in the Hyper-V cluster to be connected to each SAN? (HV1-SAN1, HV1-SAN2, HV2-SAN1, HV2-SAN2)

2. How would be the behavior in case of SAN failure? Would it be necessary to perform some administration task procedure?

Thanks.

Dear all,

Could any one provide Technet blog/articles for clear understanding on Windows sever memory parameters (key terms) definition and Hyper V dynamic memory allocation.

Regards,

Auditya N

Auditya N

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 All

Apologies if this is a long one but I thought the more information I can provide the better.

We have recently designed and built a new Hyper-V environment for a client, utilising Windows Server R2 / System Centre 2012 R2 however since putting it into production, we are now seeing problems with Virtual Machine Queues. These manifest themselves as either very high latency inside virtual machines (we’re talking 200 – 400 mSec round trip times), packet loss or complete connectivity loss for VMs. Not all VMs are affected however the problem does manifest itself on all hosts. I am aware of these issues having cropped up in the past with Broadcom NICs.

I'll give you a little bit of background into the problem...

Frist, the environment is based entirely on Dell hardware (Equallogic Storage, PowerConnect Switching and PE R720 VM Hosts). this environment was based on Server 2012 and a decision was taken to bring this up to speed to R2. This was due to a number of quite compelling reasons, mainly surrounding reliability. The core virtualisation infrastructure consists of four VM hosts in a Hyper-V Cluster.

Prior to the redesign, each VM host had 12 NICs installed:

• Quad port on-board Broadcom 5720 daughter card: Two NICs assigned to a host management team whilst the other two NICs in the same adapter formed a Live Migration / Cluster heartbeat team, to which a VM switch was connected with two vNICs exposed to the management OS. Latest drivers and firmware installed. The Converged Fabric team here was configured in LACP Address Hash (Min Queues mode), each NIC having the same two processor cores assigned. The management team is identically configured.

• Two additional Intel i350 quad port NICs: 4 NICs teamed for the production VM Switch uplink and 4 for iSCSI MPIO. Latest drivers and firmware. The VM Switch team spans both physical NICs to provide some level of NIC level fault tolerance, whilst the remaining 4 NICs for ISCSI MPIO are also balanced across the two NICs for the same reasons.

The initial driver for upgrading was that we were once again seeing issues with VMQ in the old design with the converged fabric design. The two vNics in the management OS for each of these networks were tagged to specific VLANs (that were obviously accessible to the same designated NICs in each of the VM hosts).

In this setup, a similar issue was being experienced to our present issue. Once again, the Converged Fabric vNICs in the Host OS would on occasion, either lose connectivity or exhibit very high round trip times and packet loss. This seemed to correlate with a significant increase in bandwidth through the converged fabric, such as when initiating a Live Migration and would then affect both vNICS connectivity. This would cause packet loss / connectivity loss for both the Live Migration and Cluster Heartbeat vNICs which in turn would trigger all sorts of horrid goings on in the cluster. If we disabled VMQ on the physical adapters and the team multiplex adapter, the problem went away. Obviously disabling VMQ is something that we really don’t want to resort to.

So…. The decision to refresh the environment with 2012 R2 across the board (which was also driven by other factors and not just this issue alone) was accelerated.

In the new environment, we replaced the Quad Port Broadcom 5720 Daughter Cards in the hosts with new Intel i350 QP Daughter cards to keep the NICs identical across the board. The Cluster heartbeat / Live Migration networks now use an SMB Multichannel configuration, utilising the same two NICs as in the old design in two isolated untagged port VLANs. This part of the re-design is now working very well (Live Migrations now complete much faster I hasten to add!!)

However…. The same VMQ issues that we witnessed previously have now arisen on the production VM Switch which is used to uplink the virtual machines on each host to the outside world.

The Production VM Switch is configured as follows:

• Same configuration as the original infrastructure: 4 Intel 1GbE i350 NICs, two of which are in one physical quad port NIC, whilst the other two are in an identical NIC, directly below it. The remaining 2 ports from each card function as iSCSI MPIO interfaces to the SAN. We did this to try and achieve NIC level fault tolerance. The latest Firmware and Drivers have been installed for all hardware (including the NICs) fresh from the latest Dell Server Updates DVD (V14.10).

• In each host, the above 4 VM Switch NICs are formed into a Switch independent, Dynamic team (Sum of Queues mode), each physical NIC hasRSS disabled and VMQ enabled and the Team Multiplex adapter also has RSS disabled an VMQ enabled. Secondly, each NIC is configured to use a single processor core for VMQ. As this is a Sum of Queues team, cores do not overlap and as the host processors have Hyper Threading enabled, only cores (not logical execution units) are assigned to RSS or VMQ. The configuration of the VM Switch NICs looks as follows when running Get-NetAdapterVMQ on the hosts:

Name                           InterfaceDescription              Enabled BaseVmqProcessor MaxProcessors NumberOfReceive
                                                                                                        Queues
----                           --------------------              ------- ---------------- ------------- ---------------
VM_SWITCH_ETH01                Intel(R) Gigabit 4P I350-t A...#8 True    0:10             1             7
VM_SWITCH_ETH03                Intel(R) Gigabit 4P I350-t A...#7 True    0:14             1             7
VM_SWITCH_ETH02                Intel(R) Gigabit 4P I350-t Ada... True    0:12             1             7
VM_SWITCH_ETH04                Intel(R) Gigabit 4P I350-t A...#2 True    0:16             1             7
Production VM Switch           Microsoft Network Adapter Mult... True    0:0                            28

Load is hardly an issue on these NICs and a single core seems to have sufficed in the old design, so this was carried forward into the new.

The loss of connectivity / high latency (200 – 400 mSec as before) only seems to arise when a VM is moved via Live Migration from host to host. If I setup a constant ping to a test candidate VM and move it to another host, I get about 5 dropped pings at the point where the remaining memory pages / CPU state are transferred, followed by an dramatic increase in latency once the VM is up and running on the destination host. It seems as though the destination host is struggling to allocate the VM NIC to a queue. I can then move the VM back and forth between hosts and the problem may or may not occur again. It is very intermittent. There is always a lengthy pause in VM network connectivity during the live migration process however, longer than I have seen in the past (usually only a ping or two are lost, however we are now seeing 5 or more before VM Nework connectivity is restored on the destination host, this being enough to cause a disruption to the workload).

If we disable VMQ entirely on the VM NICs and VM Switch Team Multiplex adapter on one of the hosts as a test, things behave as expected. A migration completes within the time of a standard TCP timeout.

VMQ looks to be working, as if I run Get-NetAdapterVMQQueue on one of the hosts, I can see that Queues are being allocated to VM NICs accordingly. I can also see that VM NICs are appearing in Hyper-V manager with “VMQ Active”.

It goes without saying that we really don’t want to disable VMQ, however given the nature of our clients business, we really cannot afford for these issues to crop up. If I can’t find a resolution here, I will be left with no choice as ironically, we see less issues with VMQ disabled compared to it being enabled.

I hope this is enough information to go on and if you need any more, please do let me know. Any help here would be most appreciated.

I have gone over the configuration again and again and everything appears to have been configured correctly, however I am struggling with this one.

Many thanks

Matt

Good evening,

I am hoping someone will be able to assist me with a couple of issues I've come across with moving a physical server to a hyper-v guest on a 2012 R2 host. I'm running into two different issues that have seem to make it impossible to work with the guest. Here is the background:

Had a 2008 R2 server that I used P2V to create a VHDX. Reformatted the server with 2012 R2 and installed the Hyper-V role. From there I created a new Hyper-v and used the VHDX I had created earlier. I created a NIC team with 2 NICS and have a 3rd one sitting by itself. When I created the Virtual switch I created an external network connected to the single NIC (here I am just duplicating settings for other servers that had the same role) and then configure the guest machine to connect to that external network.

Booted up the virtual machine and was able to login. Attempted to install integration services and reboot but kept getting BSOD and it just kept rebooting. Shutdown the VM and deleted it. Went back to my copy of the VHDX and recreated it with the thought that I would just RDP into it to finish the setup. However, when the server gets into windows, there is no network connection. Previously, this had the same NIC teaming configuration but the only NIC I see is the Virtual adapter, no "physical" nics appear in networking.

So, right now I have a VM with no network connection and I can't use the mouse to troubleshoot anything within the OS. Anyone have any suggestions on how to solve this problem?

Thank you in advance!

Krubb

I'm trying to use the Capacity Planner for Hyper-V replica tool to estimate requirements for a replica site.

It keeps getting stuck "Getting the VM and VHD from primary site, this can take upto several minutes...". I've waited over an hour, and it still sits there.

The primary site is a 3 node Hyper-V 2012R2 cluster. I have installed and configured the Hyper-V Replication Broker role on the cluster. For now, it's set to use HTTP without any certificates.

I don't have a replica site yet, so I've selected "Skip tests involving Replica site". For the primary site, I've tried pointing it at both the replication broker, and at one of the individual nodes. It gets stuck in the same place.

Other things I've tried:

• Disabled windows firewall on all 3 nodes
• Running the tool from one of the nodes, logged in as a domain admin account
• Moving all the VMs off of one node, and pointing the tool at that now empty node
• Let it run for longer - left it alone overnight.
• Downloaded the tool again in case it was corrupt
• Rebooted my computer

In all cases, it gets stuck at the exact same spot.

Any idea how to figure out why it is freezing? Have I missed configuring something important for the tool to run?

I am trying to create a DNS Server in a windows 2012 R2 Hyper-V Guest.

There is nothing else installed yet; only DNS Server.

I cannot get it to work! 

- Simple Query to this DNS Server passes

- Recursive Query to other DNS Servers fails.

I have other DNS servers, in physical servers or Hyper-V hosts and it has never been a problem.

Is there a limitation on running DNS Server on running DNS server of Hyper-V Guest?

Your help is very much appreciated.

Eduardo Macias 

I have this server on which I have installed Hyper-V Server 2008 R2. On this I have a VM with WDS, I've managed to create an image but when I am trying to connect more than 1 client to the server to create or restore an image, I lose connection to the main server, I can't see it in the Hyper-V manager or access any shared drives on it plus sometimes it disconnects the previous computer that already started to create/restore image. If I just play with the virtual machine created (WDS) I don't have any problems, even when I have multiple VMs on it works.

Any ideas?

Hi

This is all rather new to me so I apologise in advance if it appears stupid but I am really confused by this.

Guided by this link:

http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/general/diagnosing-live-migration-failures-part2.html

The source and destination servers are 2 different physical servers but are within the same domain.  The source server uses Hyper-V server 2012 R2 - i.e. there is no GUI, the destination server is Windows Server 2012 R2 which of course does have a GUI.  I am looking to migrate (preferably live migrate but migrating in off-state would be acceptable if needed.)

Within hyper-v manager I have enabled live migration and set the source and destination server "live migration" settings to use kerberos for authentication.

Using active directory, I set the source server using the delegation tab to "trust this computer for delegation to specificed services only" with kerberos only and then gave it delegated credentials for the destination server to use the "CIFS" service.

Then on the destination server  > delegation tab - I set it to trust this computer using kerberos only for the "CIFS" and "Microsoft Virtual System Migration Service".

Following on from this I go back in to the source server in hyper-v and right click on the virtual machine and select "move", then "move the virtual machine" - give it the destination server and then select move virtual machine's data to a single location and select a folder on the destination server for it to move to.

Any time I do this it fails, I get an error message which reads:

"virtual machine migration operation failed at migration source.

failed to establish a connection with host "x": no crdentials 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: no suitable credentials available..."

Any help would be very much appreciated!

Hi I'm not very familiar with Hyper-V but after setting up a Hyper-V server and then removing the Hyper-V Role from my Windows 2012 R2 server, it seems like one Network adapter has stopped working. I have a good switchport and cable (verified) and when I plug into this port, I see the network adapter in Control panel showing as cable is unplugged.  I then moved to another Windows 2012 server and installed Hyper-V role and setup a virtual server, then removed the server and the role and ended up with the same problem on the second server. it seems like Hyper-V's virtual switch is still holding on to this NIC port. Anyone knows how to free up this port?

Thank you

Created a VM with OS but need to add a virtual HD over 2 TB.

Also and wondering how to change the name of folder if I accidently misnamed the VM.

(I have changed the VM name but the folders for the VDH are named differently.)

dsk

Can we convert a windows 2012 R2 VM (on hyper-v running 2012 R2) to a linux VM on the same hyper-v host?

Is there such a tool?

dsk

Howdy Y'all

A question...

I've completed an install of Windows 2012 R2 with all available updates.  I installed the Hyper-V role and created a Windows 2012 virtual machine.  Everything was going well.  Then, I changed the Administrator user account name and the server name.  Now, the existing VM that was previously working and all new VMs do not initialize.  The previously working VM works fine on other Hyper-V servers.

Hyper-V-Worker Error 3040 "VMname" could not initialize

Thanks in advance for your help/advice

Jamie

I have been toying around with Hyper-V replica on 2012 and have run into an odd issue recently...

When I initially setup replication between 2 servers all seemed normal.  The path that was created on the replica server for replicated disks looked something like F:\VM\REPLICATED_VMs\Hyper-V Replica\Virtual hard disks\90D38095-0292-437C-88C0-75763446D8F9\MyServer.vhdx

Now all of a sudden the path that gets created on the replica server for replicated disks looks something like F:\VM\REPLICATED_VMs\Hyper-V Replica\Virtual hard disks\90D38095-0292-437C-88C0-75763446D8F9\F78BB460-823F-44B2-8AF7-583C30EB21E3.vhdx

The original disk on the primary server has the standard MyServer.vhdx notation.

I have no idea was has caused this to happen, has anyone else seen this before?  Did anyone get to the root cause?  I can rename this stuff manually but was hoping to get to the root cause.

Thanks in advance for any help!

I have found that the latest version of the Dell MD Storage has ODX on by default. When using the storage migration with this turned on the VHDX files transfer instantly between the LUN's but the VHDX is corrupt and causes the Virtual Server to blue screen and then to never boot again.  I have yet to find a way to recover any data. 

My current work around is to disable ODX on the array itself which means that the data is transferred by the hosts, but does not corrupt the VHDX files.

show storageArray odxsetting;

set storageArray odxEnabled=false;

Hi Everyone,

Can anyone advise what is causing the below .avhd files if there are NO snapshots?

I'm assuming it could be our ARCSERVE Hyper-V Backup software using the VSS Hyper-V writer.

SERVER Data_hex-GUID.avhd 6Mb

SERVER Data_hex-GUID.avhd 12Mb

SERVERe Data-AutoRecovery.avhd 33Mb

SERVER OS_hex-GUID.avhd 8Gb

OS-AutoRecovery.avhd

Thoughts and comments from the community would be appreciated.

Thank you

Hi All,

Scenario & Problem:

We have Primary Site ConfiguredHyper-V Cluster also enabled Hyper-V Replica feature successfully with all its required configurations. (Hyper-V Replica Broker, Firewall, Allow Replica on Replica Server)

It was all going fine and machines are properly replicated.

From few Days back replication stopped and going in critical stage I just removed replication and try to re-replicate again these VM’s, Enable VM Replication Wizard successfully completed in which you mentioned the required settings but after that on final step an error comes (Screen Shot Attached).

Troubleshooting:

• I just check the basic connectivity between Primary and Replica Servers (Proper Ping Response)
• Restart Replica Server
• Change to Replicate VM’s on another Server (But Same Error Comes)
• Checked firewall Hyper-V settings on Replica Server
• We Use Port 80 for Replication of VM’s