Hello community,
we're planning an failover concept for a customer. The primary system is installed with Windows Server 2016 Datacenter. The failover server will be installed with Windows Server 2019. There is no problem zu migration / replicate virtual machines from Hyper-V 2016 to Hyper-V 2019. To this point: No problem!
Now we plan to replicate some virtual machines from Hyper-V 2019 to Hyper-V 2016. Is this possible and supported by Microsoft?
Thanks for your answers.
Hello,
yesterday i wanted to understand CPU-Usage-Display from VM's and Hypervisor-Hosts and i red a lot of regarding stuff.
First question:
A lot of posts say, that the display in the taskmanager does only show the usage of the host-OS vCPU, but not of the physical. While i checked the CPU-Usage, i got another picture! The Taskmanager of the HyperV-Host seems to show the exactly same values as here the "logical CPU of hypervisor" (i am not sure if microsoft made a mistake in the translation, was hard to find the counter because it's listed under L what i didnt expect), that you can see here with the fat red line.
So i am wandering if microsoft changed the behavier of the taskmanager in Server2016 (what is the System i made this tests on), or if i misunderstood something!
while i recorded this graphs, i started CPU-Burn.
within the first peak of 100% CPU-Usage, i ran CPU-Burn on the Hyper-V-Host, so the blue line goes to 100% and the fat red one aswell. okay, this seems to be logical.
within the second peak of 100% CPU-Usage, i ran CPU-Born on one of the HyperV-VMs, that has assigned 11 vCPU's (while the system has 12 logical cores), so it is limited to 95% what we can see within the fat line.
what i dont understand is: what does the thin red line shows? if it is the sum of all virtual cpu's it should show aswell almost 95% CPU-usage, but it just shows something like 35% which makes no sense at all to me. can somebody explain that?
last but not least, the HyperV-Manager has also a CPU-Usage display, which does not correspondent to the CPU-Usage-display inside the taskmanager of the VM, and also does not correspondent to the relative ammount of usage of the physical CPU - as far as i understand everything right and as far as i found the right counter to display the usage of the physical CPU.
i hope, someon can bring light into the dark!
Hello,
i am trying to do remote disk management from server-manager with this result:
Error is received from a hyper-v 2012R2 host.
Anybody who knows how to fix this?
Thx
We have a 4 node Hyper-V Cluster running under Windows Server 2019 and encounter a Problem in VMs DHCP (possibly PXE/TFTP) Reply in Hyper-V, if the vSwitch is connected to a NIC Teaming Adapter.
The exact same Constellation did work in Hyper-V 2016.
It does work, if we dissolve the NIC Team and bind the single Adapter to the vSwitch.
Currently the conclusion leads to the Multiplexor Adapter Driver in Windows Server 2019 or a combination of the Teaming Driver with the vSwitch Driver/Architecture/Security Features.
Did anybody see the same behavior?
Are there any issues known regarding the above mentioned problem?
Can somebody at MS please check, if there are any open issues on this? (Teaming Driver/Multiplexor Driver NdisImPlatform.sys (Version 10.0.17763.1)
(Windows Server DC 1809 Build 17763.194)
Hi,
Since upgrading my Hyper-V servers to Windows Server 2019, including KB4471332 from last night, my guest VM's do not power down on restart of the 2019 host.
I can confirm integration components are as up to date as possible, and each guest is configured to shutdown when the host restarts.
Each guest gets the "Why did I shutdown unexpectedly message".
The even viewer yields the following all within 30 seconds of restarting the host:
Shut down physical computer. Stopping/saving all virtual machines...
'ADFS' failed to perform the 'Shutting Down' operation. The virtual machine is currently performing the following operation: 'Shutting Down'. (Virtual machine ID 0CFDF648-EE9D-4141-9EBD-9A6D911C3442)
'ADFS' failed to shut down. (Virtual machine ID 0CFDF648-EE9D-4141-9EBD-9A6D911C3442)
The Update Orchestrator Service service terminated with the following error:
This operation returned because the timeout period expired.
Failed to restore configuration for port 59229EE2-C880-4BF2-9849-89A21EC17772 (Friendly Name: ) on switch 300C0E17-E123-4182-BE62-AAD1860BE841 (Friendly Name: ), status = Object Name not found..
Everything is configured as it was on the 2016 Hyper-V host.
The message ADFS failed to shut down because it is shutting down seems terribly odd to me. Of course its shutting down, just need the host to wait. (Yes the registry is set to 120 as the default time for the host....)
Fairly simple to recreate....just spin up a 2019 server, install Hyper-V role, throw in a VM and test.
Any help would be appreciated, but my money is on it being another bug.
Hi,
I have a Windows Server 2016 DC Hyper-v cluster.
On one node I receive strange error
"An arithmetic error has occurred while computing the aggregate value for metric definition 'Aggregated Normalized I/O Operations Completed'. This will occur when the result exceeds the maximum allowed value."
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 3/12/2019 4:29:05 PM
Event ID: 28007
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: test.test
Description:
An arithmetic error has occurred while computing the aggregate value for metric definition 'Aggregated Normalized I/O Operations Completed'. This will occur when the result exceeds the maximum allowed value.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>28007</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-03-12T14:29:05.816553000Z" />
<EventRecordID>14598</EventRecordID>
<Correlation />
<Execution ProcessID="3944" ThreadID="8732" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>test.test</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<Parameter0>Aggregated Normalized I/O Operations Completed</Parameter0>
</VmlEventLog>
</UserData>
</Event>
I can't find any reference to the event id 28007 in the documentation.
Any help would be greatly appreciated.
Hello,
I am boing to test hyper-v.
I noticed i cant connect from a workgroup(not AD pc) to a hyper-v server 2016. Anyone who knows decent tutorial that explains what i need to adjust/install?
Also, should i use the Hyper-V Gui or the Hyper-V core server? Are there differences in functionality?
Many thanks for any help and advice.
Hi,
I have a Windows Server 2016 DC Hyper-v cluster.
On one node I receive strange error
"An arithmetic error has occurred while computing the aggregate value for metric definition 'Aggregated Normalized I/O Operations Completed'. This will occur when the result exceeds the maximum allowed value."
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 3/12/2019 4:29:05 PM
Event ID: 28007
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: test.test
Description:
An arithmetic error has occurred while computing the aggregate value for metric definition 'Aggregated Normalized I/O Operations Completed'. This will occur when the result exceeds the maximum allowed value.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>28007</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2019-03-12T14:29:05.816553000Z" />
<EventRecordID>14598</EventRecordID>
<Correlation />
<Execution ProcessID="3944" ThreadID="8732" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>test.test</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<Parameter0>Aggregated Normalized I/O Operations Completed</Parameter0>
</VmlEventLog>
</UserData>
</Event>
I can't find any reference to the event id 28007 in the documentation.
Any help would be greatly appreciated.
Hi,
We have a Windows 2012 R2 VM with checkpoints which we are unable to delete and getting the below message. Now the only way to fix this is to export the VM to a different location and then import it again. Will it merge the VHDs with checkpoints or what is the proper way to get rid of check points without losing the data?
I have an issue trying to pull up a console session to Hyper-V guest systems in either Hyper-V Manager or within Failover Cluster Manager on Windows 10 1803 systems using the latest RSAT install. The Hyper-V hosts are Windows 2016 and up to date. This seems to have happened after the 1803 update came out. On a Windows 10 client with the latest RSAT tools installed you can connect the Failover Cluster just fine, but when you click the VM guest thumbnail to bring up the console, nothing happens. You pull up task manager and Virtual Machine Connection is running in the background and taking up resources.
I can use the vmconnect.exe program by directly accessing it in c:\windows\system32\vmconnect.exe and pull up a Hyper-V console session from one of our hosts without issue. The ability to do so within Failover Cluster or Hyper-V manager has been lost. Has anyone else experienced this issue?
Cannot live migrate 2 of 12 VM's in FCM, when trying to live migrate these 2 VM's they get to around 48% and then the live migration stops. We've tried many things to resolve this, I'm just wondering if we've missed something.
Troubleshooting steps taken:
1. Settings > Management > Name, check for Notes in the properties
Notes existed, but after removing, did not make a difference. Cannot live migrate.
2. Files or lock folder in C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines
No folder exists with .lock files in it
3. VM migration timeout using HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\LiveMigrationTimeoutSecs
Reg path does not exist, stops at HKLM\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Agent
4. In the screenshot, it says "the operation was canceled". Is there something else that pops up before it is canceled, or is it being canceled by another user?
No. "The operation fails at source." is another error, however no user is actually cancelling the live migration.
5. Do the cluster nodes have identical hardware?
Yes
6. Is the error happening when trying to migrate to a different node?
Yes
7. Have you tried running the Cluster Validation Wizard within the FCM to test the cluster?
"Ran Cluster Validation test (excluding Storage). There was only 1 warning about an erroneous network resource that has never been connected. Error is below; however, I removed that resource form the cluster and then tried another Live Migration with no luck."
8. Does the underlying issue appear to be not with the cluster itself, but the VM?
Yes
9. Have you guys been able to live migrate VM's to all 4 of the clusters?
Yes
10. Uninstalling Veeam
No change, cannot live migrate.
11. Attempting to live migrate VM with PowerShell
Did not work
12. gwmi win32_bios
BIOS revision is same on all 4 nodes
13. Jumbo frame sizes?
Jumbo packets are disabled on all NICs.
14. VHD being written to file or a folder? If folder - are folder permissions correct?
Folder, Read/Write/Modify for System account. Permissions are OK.
16. Migrate node to node other VM's.
Other VM’s will live migrate OK
17. Migrating attached storage by itself
Storage only will live migrate OK
18. Moved MRT & RCD files and attempted to migrate again.
"Shut down VM, moved the RCT & MRT files, re-started VM - live migration did not work.
Shut down VM1 & VM2, started a quick migration - quick migration took about 10 minutes and VMs went into 'saved' state for quite a while before finally moving to other nodes.
Ran Cluster Validation test (excluding Storage). There was only 1 warning about an erroneous network resource that has never been connected. Error is below; however, I removed that resource form the cluster and then tried another Live Migration with no luck.
Re-ran a quick migration while VMs were still off. This moved the VMs fairly quickly.
Started VMs and attempted live migration of VM2; live migration did not work
Attempted live migration of VM1 while Wireshark ran and generated a capture - live migration did not work. I have capture file we can investigate. Please let me know how you want to review this capture."
19. Processor compatibility mode not enabled
Enabled, no change. 2 VM's still do not live migrate
20. Check patch level
Windows and BIOS patch level is identical between nodes
21. Check for XML file cache at C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines Cache
Copying (if it did not already exist) or removing (if it did already exist) made no change either way. On one VM, it was not there; on another VM, it was there already.
22. Edit Registry for NetworkBufferCount at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Migration
Adjusting this made no change
23. Disabling Hyperthreading
Client cannot disable Hyperthreading
24. Do VM's use shared VHD Sets?
No, they do not.
25. vCPU and vRAM differences?
No difference among the VM's. 8 vCPU, 32768 MB vRAM for each.
26. Processor > NUMA, does "Maximum amount of memory (MB)" match the same setting under Memory > RAM or Memory > Maximum RAM?
Memory settings are identical
We recently had a network traffic / virtual switch issue crop up, due to VMQ being enabled and improperly configured on Broadcom 10GbE adapters. While that failure occurred, our backup appliances were taking backups of VMs. Because of lost network connectivity, the Hyper-V checkpoints used for those backups remain on some of our VMs.
These checkpoints do not have the usual "Delete Checkpoint" / "Delete Checkpoint Subtree" options available to them. How do I remove them so the virtual disks are merged and back to a single VHDX per virtual disk?
Hello,
I tend to have a few VM's with "leftovers" from Veeam Backup Jobs - and the only way to delete them is by doing this :
https://blog.workinghardinit.work/2015/10/15/remove-lingering-backup-checkpoints-from-a-hyper-v-virtual-machine
Get-VMSnapshot -ComputerName "MyHyperVHost" -VMName "VMWithLingeringBackupCheckpoint" | Remove-VMSnapshot
Hyper-V is running on Server 2016 Datacenter with Veeam Backup and Replication 9.5 Update 3
https://www.veeam.com/kb2353
So - anyone else experiencing this?
Platform
Hyper V Server 2016
Management platform: Server Manager and native Powershell
In the the image below you will notice spare space on a local drive where I wish to add another volume or partition. UsingComputer Management via Server Manager, the option is not available. How can I do this with HyperV?
Thanks
MIS5000
Hi All,
I am trying to create a Vitual Network adaptor, but its giving the below error message.
New-VMSwitch -Name "BCD" -EnableEmbeddedTeaming $True -AllowManagementOS $False -NetAdapterName $lmnetwork (10/25 gig adaptor)
Add-VMNetworkAdapter -ManagementOS -Name "ABC" -SwitchName "BCD" | Set-NetIPInterface -Dhcp Disabled
"Internal miniport create failed, name = 'FE72DA3D-6B16-465E-8E32-549BCC60E8FE', friendly name = 'LM-vNIC01', MAC = 'DYNAMIC': Not found (0x80041002)."
I've attached a physical disk on a hyper-v guest with success. The guest boots, but there is no disk visible in Windows. Does anyone have a clue, why not?
'diskpart', 'list disk' command, does not show the disk, but it is attached on the guest:
Regards,
Allan Kjær
blog