Hi,

Has anyone had luck running the Capacity Planner(https://www.microsoft.com/en-us/download/details.aspx?id=39057) on Server 2016?  

thanks!

Hi,

What is the recommended practice for Daily/Weekly checklist on the Hyper V 2012 r2.

Thank you!

Regards,

farhan508

Hi, I am charles

I am now attempting to enable SR-IOV with NVMe SSDs on Windows Server 2019.

I already enabled SVMs for AMD CPUs and IOMMU and ACS and ARI in the BIOS.

Then, although Hyper-V was installed on Windows, only the SR-IOV Enable button for Network Adapter was found.

How do I enable SR-IOV for SSDs?

When I checked Device's PCIe Register, Host set up almost all of the SR-IOV related Registers.

Only except VF enable and Memory Space Enable.

If I set them manually, I can access the device inside through the VF BAR.

However, the device manager does not recognize it as a new device.

What should I do to solve this problem?

Hi all,

I am having a nightmare with a DC upgrade. We currently have a 2012 R2 Standard running hypervisor services. To get more out of the box we ordered a DC licence. I have access to the Microsoft licencing site and have got a copy of what I believe to be our key but I cannot get the OS to accept this and upgrade to DC.

So – several questions…

Can I upgrade from standard to DC with the appropriate key? I did specifically ask for this when we went through the quote process and was informed that the keys we would be provided with will be suitable to do an upgrade without rebuilding our hpervisor.

The error I am getting is

Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid

The key I am using is from the micorsoft site – the section is

“Windows  Server 2012 Datacenter”

I have used the KMS key and in the web site it does show our company name as the organisation so I guess that means we are all paid etc.

I did check in the KMS server and nothing seems to have been registered in there (not sure what I was expecting but it wasn’t nothing) As an extra bit of fun out network is largly behind a firewall with no internet access but I do know that the KMS server is allowed thorough and this is working – last contact reported was only a few days ago.

So – can anyone point me in the direction of installing the key and getting this OS upgraded if

cscript c:\windows\system32\slmgr.vbs –ipk xxxxx-xxxxx-xxxxx-xxxxx

is not going to work?

Thank you

Kevin.

Good day, we have configured S2D cluster on Windows Server 2019 1809 (17763.1039) cluster successly pass tests via Test-Cluster and working with no problem, but if we moving virtual machive using live migration from other S2D cluster ( Windows Server 2016 ). After migration, vm working some time ( random 1 - 8 hours ) and rebooting with errors. 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System><Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>4</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2020-02-14T18:43:25.917237000Z" /> <EventRecordID>352436</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>vm.example.com</Computer> <Security UserID="S-1-5-18" /> </System>
- <EventData><Data Name="BugcheckCode">265</Data> <Data Name="BugcheckParameter1">0xa39ff768722a4831</Data> <Data Name="BugcheckParameter2">0xb3b703eec4ab58f9</Data> <Data Name="BugcheckParameter3">0x2000001a0</Data> <Data Name="BugcheckParameter4">0x7</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> </EventData></Event>

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System><Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-02-14T18:43:29.303375100Z" /> <EventRecordID>352517</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>vm.example.com</Computer> <Security /> </System>
- <EventData><Data Name="param1">0x00000109 (0xa39ff768722a4831, 0xb3b703eec4ab58f9, 0x00000002000001a0, 0x0000000000000007)</Data> <Data Name="param2">C:\Windows\MEMORY.DMP</Data> <Data Name="param3">681c7c75-c8ec-42ae-ad15-008309d23974</Data> </EventData></Event>

If stop vm on one cluster manually move files and start vm works correctly.

Hello everybody,

I am running Hyper-V 2016 on Windows Server 2016 with the latest updates and I get this error when trying to make a checkpoint.

- I tried to move the data to another ClusterShared Volumen, but this wasn´t the solution.

- I also tried to check and renew all permissions for the files but also without any success.

- Restart the VM

- Disabled Checkpoints / Enable Checkpoints

- Remove from Failovercluster / add to Failovercluster

-Check the Status for the VSS --> all ok.

Does anybody have another idea? I tried so many things and I used Google :-) now for the last 4 Hours, but this is a really special problem I guess.

Checkpoint-VM : Checkpoint operation failed.
Checkpoint operation was cancelled.
'AZS00001' could not initiate a checkpoint operation.
Could not create auto virtual hard disk
C:\ClusterStorage\Volume03\AZS00001\AZS00001-DISK2_EDD4EDD1-855D-4ED4-B693-4131232B666D.avhd: Th
cannot be created..
Checkpoint operation for 'AZS00001' failed. (Virtual machine ID CDA47693-7962-4086-8283-2A0655D5
Checkpoint operation for 'AZS00001' was cancelled. (Virtual machine ID CDA47693-7962-4086-8283-2
'AZS00001' could not initiate a checkpoint operation: The directory or file cannot be created. (
machine ID CDA47693-7962-4086-8283-2A0655D53146)
'AZS00001' could not create auto virtual hard disk
C:\ClusterStorage\Volume03\AZS00001\AZS00001-DISK2_EDD4EDD1-855D-4ED4-B693-4131232B666D.avhd: Th
cannot be created. (0x80070052). (Virtual machine ID CDA47693-7962-4086-8283-2A0655D53146)
At line:1 char:1
+ Checkpoint-VM -Name AZS00001 -SnapshotName "test"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Checkpoint-VM], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.CheckpointVM

Kind regards, Andreas

Greetings,

Since December 2018, Hyper-v on Windows Server 2019 users have been reporting this issue.  I am posting a new thread because the original thread on the topic had a potentially misleading headline.  And most of the ensuing thread consisted of repeated requests for more information when in fact that information had already been provided.  And yet, even after an MS representative confirmed through his own testing that the (serious) problem exists, no further information has been provided for over five months.

The problem, in a nut-shell is this:  Guest VMs do not shut down gracefully when the Hyper-v host is shut down or restarted, regardless of guest VM settings.

Even when a guest VM is set to "shut down the guest operating system" as its default behavior for the "Automatic Stop Action",  the Hyper-v host doesnot actually shut down the guest VM(s) as it shuts itself down.  Rather, the VMs are just terminated as though power is cut.  Upon rebooting, the guest VMs will report no attempt to be shut down, and instead report that the prior shutdown was unplanned.

This behavior is easily reproduced.  Merely. . .

• Build a Hyper-v 2019 host server
• Install a guest VM.
• Set the guest VM to "shut down the guest operating system" under "Automatic Stop Action."
• Reboot the Hyper-v host while the guest VM is running.

. . .you will find that the guest VM was merely switched off ungracefully.

Microsoft, please acknowledge this issue and give us an ETR.  I'm sure I'm not the only person putting their server upgrades on hold after running into this issue.  Various work-arounds (using "save state" instead of "shut down") are not a viable option for me.  Please, give us some news and hope (after an inexplicably long period of waiting) that a fix is imminent.

Best Regards,

Brian

 Hi Techies,

We have server 2016 vm which hosted on server 2016 data center (Server Model: Dell R 540), that VM network disconnecting in 10 to 15mins

We have checked event logs and find that "Miniport NIC 'Microsoft Hyper-v network Adapter #4 is halting" and Miniport NIC 'Microsoft Hyper-v network Adapter #4 is paused"

recently we have updated below patches.

KB4516044

KB4512574

KB4509091

Any one have idea on this, please help us.

Early reply will be highly appreciated.

Regards

Vajram Gajengi 

I have a problem. Changes were done to the content of a vhdx by the guest os and important files are damaged. Can I undo the latest changes using the .rct file?

In other words: Does A .rct file only consist of "Off new_data" or does it contain "Offset new_data old_data" ?

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

Good morning!

I'm running into a problem with Hyper-V and I don't have a lot of information to troubleshoot off of. I'm hoping the experience and knowledge here will help me zero in on a solve for this.

Basics:
I'm trying to enable replication of a single VM'd server from my client's office in Dothan to their office in Auburn (War Eagle!). I'm also trying tore-enable replication of two user VMs from Auburn to Dothan. Dothan's hypervisor is MS Hyper-V running in Windows Server 2019 DE. Auburn's hypervisor is MS Hyper-V running in WS2016 DE. The VM to be replicated from Dothan is WS2019 DE acting as a DC and an file server. The VMs being replicated from Auburn are Win10 Pro workstations. The purpose of all replication is simple redundancy; offsite backup of each VM in case of catastrophe. The WAN infrastructure is VPN over broadband. The organization uses ADDS with all users and machines in one domain.

History:
I'd successfully set up replication of the two VMs from Auburn to Dothan a few weeks ago. I ran into issues with Kerberos that were solved by editing the registry on each hypervisor so that Kerberos had to use TCP, and eliminating packet fragmentation at the VPN routers. Those VMs were replicating consistently until this past weekend. 

During the weekend, I had to reformat the volume where the VMs are stored in Dothan. The Auburn server is a mess that I inherited from the last IT guy, nothing is virtualized on this machine and I want some redundancy, so I was going to use DFS to replicate critical files from this server to Dothan. However, when I built Dothan I used ReFS for the storage volume, and since DFS won't run on ReFS, I decided to back up Dothan, burn down the storage volume, reformat with NTFS and restore. I used Win Server Backup in WS2019 to perform a bare metal (full) backup to an external disk. Before running the backups, I merged all checkpoints back into each VHD and created new thin-provisioned VHDs from my thick-provisioned VHDs. I successfully tested each VM with the thin-prov VHDs attached before shutting all VMs down and running the backup set.

Problem:
After formatting the storage volume NTFS, I ran into issues restoring Hyper-V directly from WSB. Instead, I restored the VHDs, built new VMs for my 1 server VM and 2 replicated user VMs, and reconnected the VHDs. Everything boots up in Hyper-V and the machines run normally. The server VM is up and running with no issues. All the data is there and I can remote into each machine. Once the dust had settled, I attempted to enable replication of the server VM from Dothan to Auburn but received the following error: https://1drv.ms/u/s!Av-G2MTFk-0ZgupOcDu6lQhOgOmLUQ?e=52vnr2

This is proving to be maddening for me because there's no data associated with the error. No code or whatnot. I'm not receiving any errors from the replication wizard in terms of "unable to determine configuration", authentication errors, or anything during the process to make me think these two servers can't talk to each other. They're talking about this replication, they're just not kicking it off. 

In an attempt to control for other variables, I decided to re-enable replication of the two VMs from Auburn to Dothan. When I tried, I got this error: https://1drv.ms/u/s!Av-G2MTFk-0ZgupPTJzbNDNF_oiPgw?e=hWtNbE

Unspecified errors are a joy...

I've done my rounds on search engines and tried everything I can think of, but I just keep running into this wall. These VMs were replicating fine before all of this. 

Misc:
The Dothan server uses two volumes for Hyper-V. Hyper-V configuration files and small VHDs are stored on E:, which is SSD-based. The Dothan server VM uses a small VHD on E: for it's operating system, and it's smart paging file is parked there too.

Large VHDs and all Hyper-V Replica (inbound-replicated VMs) is stored on D:. The Dothan server VM uses a VHD stored on D: for data storage in its role as a file server. Both my Auburn VMs are stored on D: when they replicate to Dothan, which is exactly how they were before I made all these changes over the weekend.

I've rebooted both hypervisors and I've checked all the VSS writers. No errors there. I can create standard and production checkpoints for each VM, the two VMs in Auburn and the server VM in Dothan. 

If anybody can help point me in the right direction on this, I would greatly appreciate it, and I'd be happy to take you for a beer anytime you're in this part of the American south!

-MB

We have a project with a customer to create a Hyper-V Cluster with 3 hosts.

They are all prepped with one 4 port copper network card and one 2 port fiber card.

The idea is to have Cluster heartbeat and Live migration traffic on the fiber cables and all other traffic on the copper cables.
We have no fiber switch available so the fiber is connected directly between the hosts, one cable between each host in a triangle.

My initial thought was to create a SET team on the 2 fiber ports on each host and attach 2 virtual cards on each, one for Cluster and one for Live Migration.

But now I have realized this might not work at all.
You'll have to correct me if I'm wrong here but both fiber ports won't be active at the same time on the SET team, leading to connection issues to the host with the not active connection connected.

Another thought I had was to maybe not have a SET team at all and instead create 2 Vnet adapters for each function (Cluster and Live Migration). And then have 1 of them to one of the fiber ports and the other to the second fiber port.
This will create more Virtual adapters on the host, allocate more IP addresses and create a bit more complex setup to maintain. But might be needed to solve this issue?

How would we design this in the best way when we have no fibre switch to use?
On this link is a visio diagram showing the setup: https://imgur.com/egTOgBx

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.

I have a problem with multiple VMs and hyper-V replication, primarily on VMs with large files hosting backups or database servers with drives that see many changes like SQL Server TempDB. If the VM has hard drives I know are too large or get too many changes to support replication I do NOT include them (including VHDXs hosting paging files). However it appears Hyper-V STILL creates AVHDX differencing files on these VHDX files that are NOT part of replication and if the expected great number of changes take place, AVHDX files get large, and my host hard drives run out of space. 

How do I get Windows to NOT create AVHDX files on VHDX files NOT included in replication to avoid this?

Hi

I have a problem where i would like to recover from an avhdx file. the parent is not there in the chain and my avhdx file is about 50GB. Any help on how this can be done or is there any software that i can use to recover the data on that file.

I have a Hyper V cluster setup which includes 5 servers running Windows 2012.  When i try to live migrate between nodes, it errors out with the below message: 

Live migration of 'Virtual Machine testVM failed.

Virtual machine migration operation for 'testVM' failed at migration destination 'Server2'. (Virtual machine ID 038EDA6A-1B58-4B40-A840-D256C1C83B4E)
'testVM' Failed to create Planned Virtual Machine at migration destination: The object already exists. (0x80071392). (Virtual machine ID 038EDA6A-1B58-4B40-A840-D256C1C83B4E)The operation failed because a virtual machine with the same identifier already exists. Select a new identifier and try the operation again.

Any idea, how to resolve this ?  

I have created a Windows 2016 hyper-v failover cluster with 2 no hypervisors (soon to be 3) and a NAS for storage. 

Each hypervisor has 4 NICs so I used 2 of the NICs for MPIO iSCSI and the other 2 NICs I created an LACP team to our Cisco switches.  I have one external vswitch that is configured with the team logical adapter. 

The team is also a trunk link so I can pass mutiple vlans on it and it currently has a management vlan for the hypervisor physical IPs and a client traffic vlan,  see pics below - 

So my questions are - 

1) Is what I have enough for it to work properly or should I be looking to have additional networks for live migration, cluster communication etc. 

2) If I do need extra networks how exactly do I go about creating them ie. I can add any number of vlans I want to the team/virtual switch but how do I then get FCM to see and use them. 

3) If 2) can I add additional networks without any downtime or at least one hypervisor at a time so I can drain roles to the other etc. 

I have a horrible feeling I may need to rebuild the cluster to get this setup optimally. 

Any pointers would be much appreciated. 

Hi all,

I am having a nightmare with a DC upgrade. We currently have a 2012 R2 Standard running hypervisor services. To get more out of the box we ordered a DC licence. I have access to the Microsoft licencing site and have got a copy of what I believe to be our key but I cannot get the OS to accept this and upgrade to DC.

So – several questions…

Can I upgrade from standard to DC with the appropriate key? I did specifically ask for this when we went through the quote process and was informed that the keys we would be provided with will be suitable to do an upgrade without rebuilding our hpervisor.

The error I am getting is

Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid

The key I am using is from the micorsoft site – the section is

“Windows  Server 2012 Datacenter”

I have used the KMS key and in the web site it does show our company name as the organisation so I guess that means we are all paid etc.

I did check in the KMS server and nothing seems to have been registered in there (not sure what I was expecting but it wasn’t nothing) As an extra bit of fun out network is largly behind a firewall with no internet access but I do know that the KMS server is allowed thorough and this is working – last contact reported was only a few days ago.

So – can anyone point me in the direction of installing the key and getting this OS upgraded if

cscript c:\windows\system32\slmgr.vbs –ipk xxxxx-xxxxx-xxxxx-xxxxx

is not going to work?

Thank you

Kevin.

Hi All,

Good day.

Will need some help on this, recently had converted my domain controller from VM ESxi5 to Hyper-v 2012 R2 host.

My domain controller runs in window 2008 R2.

The server is able to power on after the conversion, but only issue is i am unable to run disk management. Also the Virtual Disk Services (VDS) and volume shadow copy services (VSS), is no long listed on services.msc and i am not able to turn it on.

Is there anyway or how could i fix this issue? As my backup required VSS and VDS to work.