For the last month, something strange is happening with our new Hyper-V server. During the summer holidays we bought and installed a new physical server with Windows Server 2019 Essentials installed on it; on which we also enabled and configured the Hyper-V role. On that physical Hyper-V, we have three VM's running, which are:

1. Domain controller;
2. File sharing server, part of the domain;
3. App server, also part of the domain.

All of the three VM's also have Windows Server 2019 Essentials as OS. Each WS2K19 Essentials server has its own dedicated license.

Each monday between 9:30 am and 10:30 am the Hyper-V power downs both the File and App servers. When we look in the logs there isn't anything that explains the power down of the VM's. Updates are also disabled to make sure that isn't the culprit.

Does someone has any ideas of what might be wrong or where to look in what direction? I've been looking for over a month now and can't seem to find anything.

Thanks!

Hello, I have Hyper-V cluster 2016 2 node and after power drop out on both nodes are disk offline only whitnes quorum is online. All iSCSI connection are online on both nodes.If I try set to online:

Set-Disk 4 -isOffline $false
Set-Disk : The specified object is managed by the Microsoft Failover Clustering component. The disk must be in cluster
maintenance mode and the cluster resource status must be online to perform this operation.
Activity ID: {7cfaf3a0-f55a-48f8-966a-50d8c43752bc}
At line:1 char:2
+  Set-Disk 4 -isOffline $false
+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (StorageWMI:ROOT/Microsoft/..._StorageCmdlets) [Set-Disk], CimException
    + FullyQualifiedErrorId : StorageWMI 41018,Set-Disk

In Cluster Manager is both node in state paused and disk offline. Turn On and Turn Off maintenance mode are grayed. How to bring disks to online state?

Hi,

I would like to find out whether there is any way to create snapshots of VMs using a shared disk (vhdx or VHD Set) when these VMs exist in a Hyper-V cluster and managed by SCVMM?

I know you can create VMGroups but this does not appear to work in a cluster scenario as the VMGroup seems to be host specific.  I ran a test and once I added the VM to the group I could not perform a live migrate so a group does not work.

Kind regards

Hey guys,

I have a windows 10 pro machine that I use at work without an AD connection or any kind of volume licensing.

I used the quick-create button to create a VM, used it happily for 90 days, and now its license is expired. Its a "Windows 10 Enterprise Evaluation, 1809-14-1434"

Whats the easiest way for me to get a license to this thing? What I really want is simply to pay microsoft.com for a license the same way I would for windows 10 pro.

Many thanks,

-Geoff

First off, I come from a VMWare ESXi background and have little exposure to HyperV.

There is a small 2 node cluster I inherited on SCVMM 2012 R2.  On occasion one of the hypervisor nodes will flatline at 100% CPU utilization which eventually causes it to crash.  All the VM's will then migrate to node that's left standing.  With the new load in addition to th existing load the second node will then proceed to flatline at 100% CPU and crash.  On the next cycle, the VMs will all live on one hypervisor, and the ones with resources will be online, the ones without resources will be in a failed state.

In VMWare, if you over provisioned CPU's the VM performance would get sluggish but there would never be the case where VM usage would directly crash ESXi.  I realize HyperV is a different model in the sense that the Hypervisor is still running on top of Windows OS; but is there some control I can put into place that prevents above scenario?

I have been recently supporting IT teams in some environments where they misconfigured network cards on the physical machine (Host) and the virtual machine stated having weird communication problems.

I have checked several online articles talking about this issue they all asks you to check the AV, the firewall, the file and printer sharing or your cabling, but they never asks you to check the basics, the Hyper-V configuration and the virtual switch configuration; they are right you would never think of it until you face it in an environment.

Host cannot ping virtual machine or the virtual machine cannot ping the host.

Everything goes back to the planning as the say: “if you do not have a plan, you are planning to fail.”

All starts with the planning

1. identify the usage of the server host and virtual
2. plan communication and identify how you want to access and what you want to access
3. configure your physical network cards for the host and reserve the others for the virtual
4. when you configure the virtual switch make sure that you never enable the TCP/IP V4 or V6 after it is disabled by the configuration (if it needed to be enabled it would have been kept as default)
5. configure the TCP/IP settings to work in its proper subnets
6. Document all your configuration and IP settings you did on the Virtual switches, host and virtual machines.

After you have done this now starts the troubleshooting part if you have configured everything properly and you still cannot ping you will need to check the following:

If you still can access the server but you cannot ping this means you have something blocking the ICMP traffic between the machines.

1. Firewall rules to allow ICMP
2. AV Solutions with firewall features blocking ping

If you cannot access the machine in any other way check the cabling and they are configured and if plugged on the same switch / VLAN

If you still cannot access the servers check your file and print sharing settings.

Hope this was helpful.

Good luck.

Elie C. Salameh

Hello.

I have several standalone Hyper-V Server 2016 hosts. All hosts are configured for live migration using constrained delegation and Kerberos (as detailed here https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/set-up-hosts-for-live-migration-without-failover-clustering).

The problem is despite these settings (LM enabled, LM network set, Kerberos protocol configured, constrained delegation configured), when I initiate the migration using Hyper-V manager or Powershell from a management computer, this fails with the dreaded error (below). However when I initiate migration directly from the source Hyper-V host (using Powershell as there's no GUI), the migration successfully proceeds.

The management server is in the same domain and I'm logged on as domain admin.

The error is:



There are events on the source hosts:

Event 20308, Hyper-V-VMMS: "Failed to authenticate the connection at the source host: no suitable credentials available."

Event 20306, Hyper-V-VMMS: "The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host '<destination_host_FQDN>': No credentials are available in the security package (0x8009030E)."

Event 21024, Hyper-V-VMMS: "Virtual machine migration operation for '<VM_name>' failed at migration source '<source_host_netbios_name>'. (Virtual machine ID 2CF6050E-A08A-4B0C-A321-648AF12517B4)"

Events on the destination host:

Event 22040, Hyper-V-VMMS: "Failed to receive data for a Virtual Machine migration: An existing connection was forcibly closed by the remote host. (0x80072746)."

Event 20402, Hyper-V-VMMS: "The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the destination host: An existing connection was forcibly closed by the remote host. (0x80072746)."

Event 20400, Hyper-V-VMMS: "The Virtual Machine Management Service blocked a connection request for a Virtual Machine migration from client address '192.168.30.7': An existing connection was forcibly closed by the remote host. (0x80072746)."

Here's a screenshot of constrained delegation configuration of one of the hosts, the configuration is identical on all hosts, ie. cifs and Microsoft Virtual System Migration Service allowed for all other Hyper-V hosts.

Any help is appreciated.

Hello all,

I have a fairly simple setup:  My source server has two VMs, one is one drive E: and the other is on drive F:.  I want to set up replication on a target server that is set up similarly (has a drive E: and F:).  When I try to configure replication,  I cannot figure out how to copy each to its own drive on the target server.  They won't both fit on either drive, so is there any way this can be done?  On the target server I tried:

1. selecting "Allow replication from specified servers" and defining the same server twice but it won't allow it.

2. selecting "Allow replication from any authenticated server" but it only gives me a single default location to store Replica files.

I'm fairly new to this, so please forgive me if I'm overlooking something that's obvious.

Hi Guys

            I have two brand new servers with 6 drives. 2 in Mirror, 3 Raid 5 with 1 hot spare. Both servers are identical and running Windows 2019 Datacenter. Both servers are running Hyper-V. I do not have any NAS/SAN devices being shared between these servers. I will call these servers server1 and server2 (for this example)

Is there a way to make it so that if a virtual machine on server1 dies and shuts off the replicated virtual machine on server2 will boot up automatically? The whole purpose of these servers is for virtual machine failover, I would like to do it per VM versus entire physical server. I can also format the Hyper-V partition since these servers are new and not running anything just yet.

Is Storage Spaces Direct (S2D) the answer I'm looking for? If so, how? Looks like Clustering needs as a requirement shared disks (SAN/NAS).

What do you guys think?

Thank You

Eddie

Hello there,

i have this situation

two identical server
Hp Proliant DL360 g 10
32 gb ram
3 x sas 2TB disk ( in raid 5 the volume for each server will be 4TB)
4nics

i need to build one domain controller (windows server 2016) for 40 users whit some programs and printers installed and one shared folder on it,
the customer would like to have the situation that if one of the two machine have an hardware problem the users can cntinue working,
the 2 server (or the vm on the 2 servers )should be syncronized in real time so im thinking to use 3 virtual machine on  HYper-V

1) Server1 Windows server 2016 standard license (hp license or normal one?)

on the Server1 i will install the hyper-v role and create a VM "DC01" that will be the frist domain controller

2)Server2 Windows server 2016 standard license (hp license or normal one?)

on the Server2 i will install the hyper-v role and create a VM "DC02" that will be the second domain controller

3)On both the 2 server i will install the failover and clustering funcion/role,

and i will use starwind software free for create the Virtual san (i dont have a phisical SAN)

on the clustered volume i will install a Virtual Machine added as role ,

and i will put all the VM files  so if one server go down the VM will be automatically live migrated on the other server,

so in in this scenario whit 2 winodws server 2016 (each server have one cpu 8 core)

whit 3 VM  i guess i will be covered just whit the 2 standard license couse every standard license comprend 2 VM license im right?

And another question, for testing im installing all whit windows server evaluation 180 days,

so now im not sure if buy the HPE branded Windows license or the normal "oem" windows license, what you reccomend ?

thank you in advance

Hi,

I have asked this question before however the same problem has occurred and is driving me crazy. Now we have a 2016 Hyper-V environment with Server 2016 VMs. We run daily backups using DPM 2016.

Now I came in after the weekend to find that all of my VM backups had failed and every VM that had failed had a .avhdx file left behind. I have tried shutting down the virtual machine but I get caught out with "Merge in Progress - Failed".

Sometimes when I shutdown the virtual machine it will fail to start and say that there is an issue with the virtual hard disk chain and it needs to be reconnected.

The only way I have found to fix it is to manually merge the virtual hard disks and then re-create the virtual machine. This works and then I can take another backup however a few days later the same issue will happen again.

I don't have time to constantly merge virtual machines every other day and of course it affects the production environment. There have been changes to our group policy and as it is affecting all of our hosts I wonder if this is the problem however I am not sure what to look at. I heard about the "Logon as a service" causing an issue however this made no change for me.

If anyone has any ideas I would love to hear them, currently going through it with Microsoft Support however they don't listen to the issue.

Hello!

We have Dell server which was purchased with Windows Server 2012 Standard OEM license. Server runs VM with Windows Server 2008R2. Host and Guest servers are activated. We need to move to other Hypervisor (eg ESXI or Proxmox) on the same host, but we want to preserves product license!

Could we read product key inside the VM and use it on the other Hypervisor? other suggestions?

Thanks in advance!

Is there a way of preventing user from changing or adding settings on Hyper-V vSwitch?
Or perhaps some script or settings of some sort, that can be run on 20+ machines for making changes quicker?

User should be allowed to use the psysical server for lab remotely, with creating VMs etc. But not allowed to change the vSwitch or nic settings, due to modifying settings would terminate the remote connection and the physical machines are located elsewhere. So that would mean the administrator would need to travel to location and login locally to change the settings back to default.
And no, just telling them not to change vSwitch or nic settings is not working.

Not sure what best practice would be, if it's possible with some script and policy to prevent, or some script to restore if prevention is not possible.

Any help is much appreciated!

Thanks

Hello,

Currently I'm using a Dell PowerEdge R730 server in my lab as host for my Hyper-V on Windows Server 2019. I am trying to install Citrix Hypervisor and VMware on it for nested virtualization. But im having trouble setting these up, when installing these i get the message that the VM's have no network adapter connected. I have a virtual switch configured throu Hyper-V Manager and connected to my VM's.

My Virtual Switch Management is as followed:

I have an External network configuration using my Broadcom NetXtreme Gigabit Ethernet adapter.

I already tried attaching a legacy Network adapter but this gave no result.

Can you guys help me solving this issue? 

Thanks in advance,

Koen

Hello,

For some time now, I have been wondering whether and how powerful the "private virtual switch" in HYPER-V is.

Here I have a HYPER-V server configuration (SM Server H11DSU, AMD EPYC  2x 16 Core, 256 GB RAM, VM all on NVMe) with VMs in file/print server, MS SQL Server and RDS structure.

All external users should access only via RDP to the RDS structure from an external LAN (1 GBE LAN).

So my idea is only connect the RDS server with the external LAN (HYPER-V switch external) and all other VMs connect via HYPER-V private switch (only internal in the VMs needed). 

The HYPER-V privat virtual switch should be a 10GBE switch - right?

If so - the LAN speed test with the privat virtual switch are disastrous (tested with ipfer3). My privat virtual switch only achieves a throughput of 500-600 Mbps from VM to VM. So miles away from 10 GB/s.

What can be the cause of this?

Does anything still need to be optimized on the privat virtual switch? Or is the privat virtual switch always so bad in performance? Or is it better to use an external physical 10 GBE switch, even if I don't need it?

Thanks for your helps!

Danke und liebe Grüße Oliver Richter

I am having an issue with hyper v that has been occurring for about a week now.

A Couple of time throughout the day our servers become very sluggish, especially the file server.  When i look at the Hyper V manager, all the vm's are in a backup status.

There are no replications running, and once the backups are done, everything returns to normal. My challenge is that when this happens, it is almost impossible to open files on the file server.  And when i try to remote to the file server, it takes a long time to log in.

Interesting problem... ok, annoying problem

Here's what I have: 2019 Hyper-V. Some new machines (Gen2, Config 9.0) and some old ones (imported from 2012 R2, Gen1, Config 5.0). When the server shuts down, we save the state of the machines and restore it after the restart of the host.

Now, here's the problem:

After one of those restarts, 2 old hyper-v machines didn't restart. Why? Well, they told me, that they cannot remove something form the configuration of this computer, because it belongs to another virtual computer (whatever this means). Then it also told me, that there was an access denied to the vsc file.

Ok... so... I checked the rights for "NT VIRTUAL MACHINE\<guid of wm>" ... they were there. Next step ... sure, always... ProcMon ! ... who wants to access this file? it was the vmms running as SYSTEM ... ok... checked the rights for SYSTEM -> all there. ... still no access while trying to do FSCTL_SET_COMPRESSION (?? hmm?) ...

Then I thought -> I don't have time for this... reset everything and restart the machines. I did that and they came back. But, those vsc and bin files are still there. What happens when the machine state is stored the next time? Will I have the same problem again? What can I do against it? Why does this problem exist at all? And where is the access denied that the system talk of that ProcMon cannot see??

Rudolf