Hello there,

We have Windows Server 2012 with Hyper-V virtual machine installed and we have a problem each time we need to shut down the VM, ie it stucks and when we have much lower network traffic (later at night), it shuts down in half an hour, but during the day it takes many many hours to shut down. The VM is connected to the host using virtual switch and it has static IP address (must have). I read that disabling the option "Allow management operating system to share this network adapter" fixes this issue, but on the other side, it shadows the VM in the network, and the VM needs to be connected to our LAN because we have devices connected to the service we're using in the VM, where we have installed CentOS. It's especially a problem when Windows need to make an update and it gets stuck during the process of closing the Hyper-V processes long time, so we always need to hard reset the server (which is unacceptable). I googled this problem and still haven't find a solution, so is there a proper fix to this problem?

Thanks.

Hi,

We are using HNS to support container Networking. The vSwitch Extension is Open vSwitch Extension. When I invoke HNS.psm1 to attach an existing HNS Endpoint to a container, the request doesn't return. The process never stops, even if I input ctrl+Z or ctrl+C, no response returns. The issue also happens in deleting HNS Endpoint or deleting HNS Network.

It is found in Windows Server 2019(1809), and all possible KBs are updated on March 16th, 2020.

Please help give some guidance on such issue.

Thanks,

Wenying

I have a Windows 2012 R2 Hyper-V environment, which replicates to another server.

Edit: Both the primary and replica server have all windows updates installed.

The replication works 100% UNTIL I make a backup with the Windows backup (full backup) to an attached USB disk (This backup completes successfully). As soon as the backup finished the following events are logged:

Information (ID 19070): 'Server01' background disk merge has been started. (Virtual machine ID 0C9506DC-333A-4D04-8274-428B693C3E40)
Error (ID 19100): 'Server01' background disk merge failed to complete: Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced. (0x8007052F). (Virtual machine ID 0C9506DC-333A-4D04-8274-428B693C3E40)
Error (ID 33676): Replication operation for virtual machine 'Server01' failed: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 0C9506DC-333A-4D04-8274-428B693C3E40) (Primary server: 'VmHost', Replica server: 'SERVER03')
Error (ID 32016): Hyper-V failed to generate delta for virtual machine 'Server01': The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 0C9506DC-333A-4D04-8274-428B693C3E40)
Error (ID 33680): Replication operation for virtual machine 'Server01' failed. (Virtual machine ID 0C9506DC-333A-4D04-8274-428B693C3E40) (Primary server: 'VmHost', Replica server: 'SERVER03')
Error (ID 32086): Hyper-V suspended replication for virtual machine 'Server01' due to a non-recoverable failure. Resume replication after correcting the failure. (Virtual machine ID 0C9506DC-333A-4D04-8274-428B693C3E40)
Information (ID 19070): 'Server01' background disk merge has been started. (Virtual machine ID 0C9506DC-333A-4D04-8274-428B693C3E40)
Error (ID 32510): Failed to delete the log file 'C:\VHD\Server01\Server01_E6713989-DDDD-400A-8B0C-6B0F0BF1F84C.hrl' for virtual machine 'Server01'. (Virtual machine ID 0C9506DC-333A-4D04-8274-428B693C3E40) (VHD C:\VHD\Server01\New Virtual Hard Disk_77946681-5D4D-410C-82A9-7285C5F692AE.avhdx) - Error: The process cannot access the file because it is being used by another process. (0x80070020)
Error (ID 19100): 'Server01' background disk merge failed to complete: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 0C9506DC-333A-4D04-8274-428B693C3E40)

After this, replication AND backup fails until I shutdown all virtual machines - at this point (turned off) the merge succeeds and after I start the machines again everything works fine until the next backup.

Please help.

Hello, 

I am experiencing an ongoing issue with Hyper-V 2016, when I try to expand a VHDX via Failover Cluster Manager or Hyper-V Manager the expansion does not complete. Furthermore, when I attempt to stop the virtual machine the machine hangs at stopping and becomes unmanageable, this is happening on Hyper-V 2016 and the virtual machine is running Windows Server 2016

Has anyone else experienced a similar issue with Hyper-V 2016?

Thanks!

Hi

I'm unable to connect to my new Hyper-V Server 2016 using HyperV Manager from my Windows 10 client.

Both computers are fresh installations and they are in workgroup.

When I launch the HyperV Manager I type the ip address of the HyperV Server and the administrator credentials. Clicking on the Connect button it asks me if I want to Enable credentials delegation and I allow. Then it returns the error:

"Delegation of credentials to the server 192.168.1.XXX could not be enabled.  CredSSP authentication is currently disabled on the local client.  You must be running with administrator priviledges in order to enable CredSSP"

This is exactly what I did from the beginning:

- on server side I installed HyperV Server 2016, ran powershell commands "Enable-PSRemoting" and "Enable-WSManCredSSP -ROle Server"

- on client side I installed Windows 10 1909, ran powershell commands "Start-Service WinRM" and "Set-Item WSMan:\localhost\Client\TrustedHosts -Value "SERVER IP ADDRESS"", then enable local group policy on the computer:Computer Configuration > Administrative Templates > System > Credentials Delegation > Allow delegating fresh credentials with NTLM-only server authentication and add "wsman/SERVERIPADDRESS" in the Show tab, then installed the HyperV feature and disabled the W10 firewall

Any help?

This is my first time on HyperV and I didn't figure it so difficult to connect after a fresh installation....compared to Vmware it looks excessively intricate 

Thanks in advance

Thanks

Hi,

We are having som network issues regarding our Nested Virtualization setup.

* The Physical host have no problem regarding retransmission of TCP packages to the network
* The Nested Virtualization host have no problem regarding retransmission of TCP packages to the network
* The VM on the Nested Virtualization host have problem regarding retransmission of TCP packages to the network (3-6% retransmission - the rest of the packages is behaving just fine).

Do any of you guys know why this is and how to fix it?

Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Hi,

I have a 2008R2 guest server hosted on the 2012R2 hypervisor. Until now version 6.3.9600.16384 of Integration Services was installed on it. Then I installed updates on the hypervisor (2012R2). After that I installed the new version of Integration Services on guest systems (6.3.9600.19456), but after restart the error 0xc0000428 vmbus.sys "Windows cannot verify the digital signature for this file" occur and the server did not start. Of course I had a snapshot so I did a revert. Since the guest server (2008R2) did not have all updates installed, I installed them with Windows Update. After that I reinstalled the latest Integration Services again and this time there were no problems - 2008R2 starts up properly.

My question is: which update may be necessary before installing the latest Integration Services? I am asking because I have other servers on which I cannot install all updates and I would like to install only those that will allow me to upgrade Integration Services.

When I create a private network on Server 2008 r2 with the Hyper V role (hotfix for 2012 guest vms installed). I then install server 2012 as a guest and install the dhcp,wds roles. Then MDT 2012 u1. When I perform a deployment using multicast, booting into a vm pxe boot, the performance is about 600-700kbps. The network utilization is at 1-10%. A 13Gb image takes ages. If I put the legacy nic into the mdt server and of course the client as it pxe boots the performance is 10000kbps.

This is the same on a external network. At first I thought it was a physical switch issue. When I created a MDT server on a physical server (1gbps port) and turned on flow control the multicast performance is great 10000kbps.

There seems to be a bottleneck in the hyper v switch as the mdt server as its conenction is 10gbps or a lot higher than 100mbps.

Can I configure the hyper v switch for flow control (or some other way)? When using the hyper v vm nic their are a lot of NACK errors and repair packets. Their are hardly any errors when all adapters are at 100mbps. 

Just wondered if anyone else had encountered this issue.

I'm currently testing with a server 2008 r2 mdt vm guest.

We just put up a new Server 2016 Hyper-V host and moved roughly 10 VMs to it from several Server 2012 R2 Hosts.

We are running Veeam B&R and have had no issues until this point.  We can not successfully create checkpoints manually, and Veeam backups are failing for this same reason.

Error messages and logs are below.

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          4/18/2018 2:16:20 PM
Event ID:      18014
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      Server
Description:
Checkpoint operation for 'VM' was cancelled. (Virtual machine ID 81998206-704D-4303-88D0-EE956C499142)
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-ABC-4418-85FD-36E3F9C0600C}" /><EventID>18014</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime="2018-04-18T21:16:20.207168700Z" /><EventRecordID>1305</EventRecordID><Correlation /><Execution ProcessID="3676" ThreadID="12192" /><Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel><Computer>Server</Computer><Security UserID="S-1-5-18" /></System><UserData><VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events"><VmName>VM</VmName><VmId>81998206-704D-4303-88D0-EE956C499142</VmId></VmlEventLog></UserData></Event>



Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          4/18/2018 2:16:20 PM
Event ID:      18012
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      Server
Description:
Checkpoint operation for 'VM' failed. (Virtual machine ID 81998206-704D-4303-88D0-EE956C499142)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7ABC-4418-85FD-36E3F9C0600C}" /><EventID>18012</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime="2018-04-18T21:16:20.207202300Z" /><EventRecordID>1306</EventRecordID><Correlation /><Execution ProcessID="3676" ThreadID="12192" /><Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel><Computer>Server</Computer><Security UserID="S-1-5-18" /></System><UserData><VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events"><VmName>VM</VmName><VmId>81998206-704D-4303-88D0-EE956C499142</VmId></VmlEventLog></UserData></Event>

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          4/18/2018 2:16:20 PM
Event ID:      19100
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      Server
Description:
'VM' background disk merge failed to complete: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID 81998206-704D-4303-88D0-EE956C499142)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7ABC-4418-85FD-36E3F9C0600C}" /><EventID>19100</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime="2018-04-18T21:16:20.232904700Z" /><EventRecordID>1308</EventRecordID><Correlation /><Execution ProcessID="3676" ThreadID="12192" /><Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel><Computer>Server</Computer><Security UserID="S-1-5-18" /></System><UserData><VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events"><VmName>VM</VmName><VmId>81998206-704D-4303-88D0-EE956C499142</VmId><ErrorMessage>%%2147942432</ErrorMessage><ErrorCode>0x80070020</ErrorCode></VmlEventLog></UserData></Event>

Brian Modlin

We have a two clustered W2016 Hyper-V hosts, every couple of days one of the hosts gets stuck when the backup kicks off. In Hyper-V manager the VMs all say 'Creating checkpoint 9%' It's always the same percentage 9%. You can't cancel the operation and the VMMS service refuses to stop, the only way to get out of the mess is to shutdown the VMs, and hard reset the effected node. The backup works for a few days then it all starts again.

The only events I can see on the effected node is:

Event ID: 19060 source: Hyper-V-VMMS

'VMName' failed to perform the 'Creating Checkpoint' operation. The virtual machine is currently performing the following operation: 'Creating Checkpoint'.

Can anybody help please? Cluster validation is clean. Hosts and guests are patched up.

We have just setup a new Hyper-V cluster based on 2012 R2 in a completely new AD Domain. We have two physical hosts (nodes) running 2012 R2 (domain members). A 2008 R2 (Swedish version) DC running on a physical machine. A virtual DC running on the cluster (2008 R2 English version). We have also setup two virtual member servers running 2012 R2 Swedish version. One of them a WSUS server. Everything was at this point working flawlessly.

Later we did two things; enabling CAU and adding a custom security group to the “Allow logon through Terminal Services” setting in Default Domain Policy.

Symptom 1 – Unable to RDP to DC:s:

Next, no one (not even Domain Admins) was able to logon remotely. We removed the group from the GPO setting (hence back to its orginal setting – unset). We verified using rsop on all servers that the change back had taken effect. However, we (Domain Admins) could still not RDP to the DC:s, only to member servers.

Symptom 2 – Differences in firewall policies.

Next, we added two virtual member servers and added them to the domain. First thing we noticed was that we were not able to ping those new servers because the Windows firewall did not allow ping. Further investigation showed that the new servers had in general a lot less active firewall exceptions compared to other member servers, although they are in the same OU, have the same GPO:s and we have not did any manual configuration of firewall rules. Why is there a difference in active firewall exceptions?

Symptom 3 – Weird CAU log entries  in cluster Log.

See log entries further down. The CAU role “CAUcorp-qhc) is not visible under “Roles” in Cluster Manager but a computer object is created in Active Directory.

 -----logs---

Cluster network name resource 'corp-wsus' failed to create its associated computer object in domain 'domain.se' for the following reason: Resource online.

Cluster resource 'corp-wsus' of type 'Distributed Network Name' in clustered role 'CAUcorp-qhc' failed.

Cluster network name resource 'corp-wsus' failed to create its associated computer object in domain 'domain.se' for the following reason: Resource online.

Cluster resource 'corp-wsus' of type 'Distributed Network Name' in clustered role 'CAUcorp-qhc' failed.

Clustered role 'CAUcorp-qhc' has exceeded its failover threshold.  It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state.

Hello,

Just a 'simple' question.

I know the Hyper-V OS Supports n+1 as a guest VM so
HV Windows Server 2012 R2 supports Windows Server 2016 as a Virtual Machine

But if the physical Hyper-V host server only supports Windows Server 2012 R2, is a Windows Server 2016 as a GUEST still supported by the guest n+1 rule?

Please only Microsoft official links only :)

Regards,

Arian!

*yes Gen7 is old .. but just to know what if :)

Hello!

I am using Hyper-V on a 2016 Server and trying to expand one of the VMs. I shut it down and then went to settings, Hard Drive, Edit, Expand. This seemed to have worked fine and I turned back on the VM. However, the C drive was not any larger.

After some research I noticed I needed to expand the partition in Disk Manager to an unallocated part that was created in step one, but there is no unallocated part. There is plenty of room on the partition with the VHDX VMs. And actually recently I added a new VM and gave it a few GBs and that all worked within Hyper-V.

Right now when I inspect the expanded VM the Maximum Disk Size is corrected to the expanded size.

Not sure what else to do.

Thanks for any help.

When we import an exported VM with the import wizard, there are steps before actually import the system (= realize the planned system) such as importing the definition, modify system settings. In those steps, .vmcx and .vmrs are located in "C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Virtual Machines".

Can we change the path or volume to the "Planned Virtual Machines" folder where is located .vmcx and vmrs before we actually import the system (= realize the planned system) ?

--- below is the original description before rewording to the above question ---

When we call ImportSystemDefinition method of the Msvm_VirtualSystemManagementService class, .vmcx and .vmrs are created in the planned virtual machines folder under C: drive. 

Do we have any way to change the volume where it is located ?

.vmcx and .vmrs are created under this path : 

"C:\ProgramData\Microsoft\Windows\Hyper-V\Planned Virtual Machines"

.vmrs is sometimes as large as some GBs, and the room in C: becomes tight with it.

I would like to change it to other volume like E: .

Hi

We have inherited a pretty poor situation where we have a couple of Hyper-V VMs that were being replicated via ASR to a tenancy in one Azure Region but due to a change in policy the company was required to use another region so all our infrastructure was migrated across - all except the Recovery Service Vault and the replicas. By the time this was noticed access to the previous tenancy, and thus replicas, was no longer available.

So we are now left with these on premises VMs that have replication set to a non-existent ASR environment, replication that can't be removed because it needs to be done from the 9non-existent) ASR end - meaning we have VMs that now have no current disaster recovery provision and that we are seemingly unable to easily provide a new one.

I have been looking online for possibilities but have found nothing so far, my only thoughts so far are either to try and force a new ASR replication policy from our current Region and hope it takes over or shut the VMs down and build new VMs from the existing disks. I would love to be able to test both of these options but creating some test VMs with the exact same predicament may not be possible.

Love to hear any advice, plans or similar situations that were successfully resolved.

Thank you