I have 2 virtual machines that are replicating to another Hyper-V host.  One machine works and starts up fine and seems to run fine, but if I try to start my other VM it immediately come up with the error "the application encountered an error while attempting to change the state of 'server'.  'Server' failed to start.  'Server' could not initialize.  The key protector could not be unwrapped. Details are included in the HostGuardianService-Client event log.

In the details section it does say local certificates not found : signing Count = 0, encrypt = 0

I am not encrypting the drives of the hyper visor or the VMs that are running below it and I am not using shielded machines.  Any help would  be great.  Thanks

Hi guys, 

On Hyper-V 2016 I'm getting this for just one of the virtual machines. 

If someone ever had the similar issue please let me know how to resolve it. 

Thanks. 

Hi guys, 

I accidentally found out some AVHDX files for one of the virtual machine drives. 

I inspected SQL-CPH2-OS.vhdx and got this. 

So as you can see it is not referring to any of AVHDX files.

I also checked whether a snapshot or snapshots exist for this server but found nothing.

If someone ever had the similar situation please advise if it is safe to delete those AVHDX files.

Regards,  

Hi I have 2 servers running 2012R2 that replicate a VM with three VHDs. I started getting this event :

Pending log file size is more than (694493 MB). Change tracking for virtual machine 'COMPUTERNAME' will be disabled since the pending log file size has exceeded its limit. (Virtual machine ID xxxxxxxxxxxx)

The replication never completes it gets to 100% and then starts over. I get an error saying background disk merge has been interrupted.

I removed the replication and set it up from scratch exporting initially to USB Media and then importing again. It was successful however I am still getting the same error. Has anyone seen this before ? I can not see any system event or application log errors both HyperV servers have enough disk space. I have run a diagnostic on the hardware as I suspected a disk issue however this is not the case and I did open a support ticket with the vendor.

Update: ok so replication is now successful and the replication health states normal however when I see changes replicate the replication completes and it then says Merge - cancelled.

Thanks

Bob

Reno Nevada

Hi.

I have windows 2019 Datacenter, and I configure SET Teaming with 2  embedded network card (dell server).  Everything works fine until i must replace motherboard, after replacement to this same model, my SET Teaming doesn't work, I see that 2 embedded NIC as normal unconfigured NIC. When I want to add this NIC to that SET VM Switch using command :

$vmswitch = Get-VMSwitch -Name SET-TrunkTeam2
Add-VMSwitchTeamMember -VMSwitch $vmswitch -NetAdapterName NIC1

Add-VMSwitchTeamMember : Value cannot be null.
Parameter name: source

Hi,

I have been managing my Hyper-V Server from the same machine for several months.  Today I cannot connect to my server.  When I try to connect, I get an error that says my User ID is not valid.  I can connect with my user id and password no problem through RDP or on the server directly.  I did not change anything other than apply updates this week.  Why can't I connect to my server like I always have??  My User ID and password IS correct and my ID has full admin rights.

Not sure what to do here.

I have a guest VM (Windows Server 2019) set to shut down when the host (Also Server 2019) shuts down, however when the host is turned off the guest fails to shut down.

The error message is "'(VM Name)' failed to perform the 'Shutting Down' operation. The virtual machine is currently performing the following operation: 'Shutting Down'."

I am able to successfully power off the guest from the Hyper-V toolbar, which I assume confirms that the shutdown integration service is working correctly.

Is there anything I can do about this?

Hi guys, 

Server OS: Windows Server 2012 R2

I have a VM Gen2 with following settings: 

I can boot fine from the same .iso from a Gen1 VM so the .iso is bootable. 

I know that the Gen2 VM uses SCSI instead of IDE, but I have no clue regarding how to boot from the .iso..

Any ideas?

Thanks in advance!

Best regards,

Kenny

I am attempting to access a Hyper-V Management Console from a Windows 10 Pro Version 10.0.18362 Build 18362. The Hyper-V Server is running on a Window Server 2012R2. I am getting the following message when I attempt to access the Hyper-V Server from my Windows 10 Pro workstation.

The workstation and the Server are on the same domain and the Server is a domain controller. I have the domain user as a local user on the workstation and in the Hyper-V administrator group and the user is on the Server in the Hyper-V administrator group. 

Looking at the Microsoft FAQ on Hyper-V the Windows 10 Pro Hyper-V MMC is backward compatable to Windows Server 2012R2.  

Can anyone help with this issue or did Microsoft break this with the latest version of Windows 10 Pro.

Hi,

Presumably because WS2019 just came out, I can only find 1 YouTube video which explains from A-Z how to install and configure Hyper-V on WS2019. Unfortunately, that video is without sound and is very blurry, so I can't really see what the demonstrator is doing.

I am a total newbie at virtualization. I would greatly appreciate it if someone could point to a video or written tutorial on how to do this.

TIA,

mlavie

Hi All,

We have a Cent OS installed on a Hyper-V server and I would like to know if there is a way to check on how much of system resources are reserved via CLI of the Cent OS for this specific guest OS.

In VMware ESx, I can run the below commandd to know the reserved values for CPU and memory reservation.

vmware-toolbox-cmd stat cpures
16000 MHz

vmware-toolbox-cmd stat memres
8192 MB

I understand that I can go to Resource Control section of the guest OS to view/modify these value but I would like to know if this can checked from a guest OS's CLI?

Hi Team 

I have created a new cluster of 6 hosts DL380 G10 with Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz processors in them, they are on same ROM update as well. 

if I try to Live migrate via SCVMM following message occurs in Select host tab. 

"The Virtual Machine (VM Name) is not compatible with the virtualization host (Host name). the virtual Machine may not start or operate correctly on the Host. This may be due to inconsistent processor combability information. "

When I Try with the Failover Cluster Manager it gives me following error 

Live migration of 'SCVMM DCUTL01' failed.Virtual machine migration operation for 'VMNAME' failed at migration destination 'HOSTNAME'. (Virtual machine ID xxxxxxxxxxxxxxxxxxx)The processor settings for virtual machine 'VMNAME' are not compatible with physical computer 'HOSTNAME'. To migrate this virtual machine, you must first shut it down. After shutdown, you can migrate this virtual machine or export it and then import it on the destination physical computer with the correct processor settings. (Virtual machine ID xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)

I have not tried it with allow from compatibility mode on as that will not be a resolution. all my processors are the same.

Thanks

Saqib Ahmed

When we run Hyper-V, is there any guidelines on deploying antivirus, white-listing, device control etc on Host OS?

What is the recommended practice?

I need to run 3 guest OS on Windows 2016 Standard Server which is a 2 physical Processor each with 16 cores each. (total 32 cores)

In this case what is my Windows 2016 license part number/description?

Hi,

I bought a new server with a new win 2016 server standard installed and activated (I have valid a license key).On this server I Added the Hyper-V role, and I have rights to create 2 VM with win server 2016 each.

As I didn't receive any ISO, I downloaded from download.microsoft.com the win 22016 standard evaluation ISO (14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_FR-FR.iso).

I created 2 vm's, both activated automatically but limited to 180 days (it is displayed on the screen). I would like to type the product key to convert the evaluation license into a permanent license.Problem: The license key used on the server not accepted.

Do I have to install win server 2016 from another .iso (where can I download it?)? POr do I receive other licese keys? The server reseller doesn't know.

Please help!!!!!

Alain Bourgeois

I have two Win2k8R2 SP1 x64 hyper-v VM's

They reside on a dedicated physical server at a hosting company.

The hosting company provided the VHD files that I used to create the VM's years ago.

As the VM's are in production, I would like to download backups of the VHD files (there are no snapshots) and perform in-place upgrades to Server 2012 and then to 2016.  Due to the complexity of what's on these VM's, migrating the content to a fresh OS is not an option.

The hosting company no longer supports Hyper-V, so they likely will not provide me with media to do the in-place upgrades.  For clarity: The hosting company will allow me to use Hyper-V, but they won't provide support for it.

My goal is to perform the in-place upgrades and then stand up the upgraded VM's on a fresh dedicated Server Datacenter 2016 hypervisor back at the hosting company. As I understand it the hosting company's Datacenter volume license will cover the guest VM's.

I tried performing the 2008 to 2012 upgrade using a Server 2102 R2 Evaluation ISO from Microsoft but it resulted in an error. Apparently a licensed Win2k8R2 VM cannot be upgraded to Win2012R2 using an Evaluation ISO.  I don't know if this is true.

My question is: How can I get the Server 2012R2 and 2016 media to perform the in-place upgrades?  And what if anything do I need to know about licensing as it pertains to the above scenario?

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 new win 2016 server standard, installed full gui, 1 cpu, 14 cores, 64 Gb RAM.

I created 2 vm's in hyperv (generation 2), each having win server 2016 standard (first one for active directory and wsus - 4Gb RAM, second one for exchange, file sharing, databases - 50Gb RAM).

For each VM I can set the number of "virtual processors". Can someone explain what a "virtual processor" means: a core, a thread, or something else? How much can I allocate if I have 14 cores and 2 vm's? 1 seems much too low: when fetching update, hyperv tells 3% cpu is used but inside vm, 99% cpu is used according to task manager.

Thanks for the hint.

Alain Bourgeois

Hi,

I noticed that the IP range of the default switch is changing a lot without my doing. I installed Ubuntu set up static ip and set gateway manually, which worked perfectly. But then after some update the default network switch's ip range changed and so did the ip of my host computer + gateway's ip so nothing worked within Linux. I had to change everything again.

Even if I change to DHCP it is quite annoying because still the IP address of the Ubuntu machine changed so I have to figure it out again and change it in ssh config etc.

How can I tell hyper-v to not change the network range?

Thank you in advance.

Kind Regards.

Andreas

Hi all,

I've spent days at this point trying to diagnose this one, so I'm opening it up for discussion/a bug report.

Windows Server 2019 / Hyper-V Server 2019 is ignoring the "Performance options" selection on hosts and using SMB regardless of any other administrative choice. This is using Kerberos authentication.

2 hosts, non-clustered, local storage. Hyper-V Server 2019 (I've installed 2019 Standard as well, with the same behavior)

I originally assumed that I must have a config problem. I blew two hosts away, clean installs of 2019, no configuration scripts. Just the LBFO network config and a a converged fabric network design. Same problem.

Next I assumed it had to be networking. So drop the teaming, drop the config scripts, drop the VLAN configs, drop the LAGs. 1 physical NIC with access to domain controllers for non-migration traffic. Another single physical NIC - on a crossover cable - for live migration. Same problem.

After this, I have tried clean installs with all group policy being blocked from application on the hypervisors. I've tried clean installs with Microsoft Intel NIC drivers and Intel's v23 and v24 release NIC drivers. Same problem. I've tried the June 2019 re-release of Hyper-V Server 2019 and even a direct from DVD install (no language packs etc), so a 100% vanilla source.

Here is the problem in its simplest form (the two physical 1GbE NIC setup):

Live Migration: Kerberos & Compression
A test VM with a VHDX with a couple of GB of junk data in it to push back and forwards
All configs are verified
Windows Firewall modes are domain/private - and it makes no difference if Windows Firewall is off
Windows Defender is uninstalled and no other software (let alone security software) is installed, period. These are fresh installs
The ONLY live migration network in the Incoming Live Migration networks list is 10.0.1.1/32 on HV1 and 10.0.1.2/32 on HV2

Migration LAN: 10.0.1.0/24 (point to point via a crossover cable)
All other traffic: 192.168.1.0/24 (via a flat LAN configured switch i.e. it's in dumb mode)

VMMS listens ON THE CORRECT LAN

netstat -an | findstr 6600
  TCP    10.0.1.2:6600       0.0.0.0:0              LISTENING

When performing an online/offline migration VMMS connects correctly over the >correct< LAN

netstat -an | findstr 6600
  TCP    10.0.1.2:6600       0.0.0.0:0              LISTENING
  TCP    10.0.1.2:54397      10.23.103.1:6600       ESTABLISHED

All fine!

Using Packet Capture on the 10.0.1.0/24 migration LAN there is plenty of chatter to/from TCP 6600. You can see the VMCX configuration state being transmitted in XML over TCP 6600 and lots of successful back and forth activity for 0.35 seconds. Then traffic on TCP 6600 stops.

Traffic now starts up on the non-Migration network, the 192.168.1.0 network - that is NOT in the Migration networks list. A large block transfer occurs. Packet monitoring this connection shows an SMB transfer occurring. This block transfer is of course, the VHDX file.

As soon as the block transfer completes on the 192.168.1.0 network (~16 seconds) traffic picks-up again over TCP 6600 on the 10.0.1.0 network for about 0.5 seconds and the Live Migration completes.

The only way that I can get the hosts to transfer over the 10.0.1.0 network is to add their respective FQDN entries to the local server Hosts files.

Re-doing the transfer now uses the correct 10.0.1.0 network. You can clearly see the VMCX transfer over TCP 6600, then a SMB 2.0 session is established using the value from the hosts file between source and destination over 10.0.1.0. An SMB transfer of the VHDX occurs on the forced 10.0.1.0 network before finally the process is concluded via traffic on TCP 6600 (still on the 10.0.1.0 network) and the transfer completes successfully.

Without the Hosts file entries, Hyper-V seems to be using NetBIOS to find the migration target, it can't so it defaults to whatever network it can find a SMB connection on. However, I say again, the 192.168.1.0 network is not in the Live Migration networks list - Hyper-V should be failing the transfer, not unilaterally deciding to "use any available network for live migration". PowerShell on both hosts confirm that this is correctly configured:

get-vmhost | fl *

....
MaximumStorageMigrations                  : 2
MaximumVirtualMachineMigrations           : 2
UseAnyNetworkForMigration                 : False
VirtualMachineMigrationAuthenticationType : Kerberos
VirtualMachineMigrationEnabled            : True
VirtualMachineMigrationPerformanceOption  : Compression
...

Get-VMMigrationNetwork

Subnet       : 10.0.1.1/32
Priority     : 0
CimSession   : CimSession: .
ComputerName : HV2
IsDeleted    : False

Something is causing it to ignore the Compression setting, but only for VHDX transfers. Other VM data is being sent correctly over TCP 6600. As the 10.0.1.0 network isn't registered in DNS, Hyper-V isn't "aware" that it can find the destination host over that link. Of course, in this test I do not want it to use SMB to perform this transfer, so it should not be using SMB in the first place. What I want is migration traffic to occur over a private 9K Jumbo Frame network - as I've always used - and not bother the 1.5K frame management network.

I've clean installed Windows Server so many times to diagnose down on this I've gone dizzy! Does anyone have any bright ideas?

Thanks