I'm running Server 2016 with S2D in a cluster to host Hyper-V VMs.  I get a ton of the following "Information" messages on my host servers running failover cluster, S2D, and Hyper-V.  It seems like the failover cluster has an error, but these are reported in the Application log as "Information" messages.  Anyone else seeing these or have any thoughts on them?  Are these just information or actually something to fix?

Application Event Log: Information 1001 Windows Error Reporting
-----------------------------------------------------------------------------------

WER contents <g class="gr_ gr_647 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar multiReplace" data-gr-id="647" id="647">in</g> the Report.<g class="gr_ gr_658 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="658" id="658">wer</g> file
-----------------------------------------------------------------------------------

Dear all:

Windows expects to have a Pagefile. So if I configure replication for a guest and I don't want to replicate the Pagefile, which is constantly changing, I will have to create the page file on a separate disk which is excluded from replication.

However, there is a problem: If you suspend that guest machine and resume it or you shut it down and restart it, sometimes it freezes. This happens from time to time, say one out of three times. It ONLY happens if the Pagefile is on a separate virtual disk.

Why would that happen? Well, according to https://www.altaro.com/hyper-v/excluding-paging-file-from-hyper-v-replication/"Relocating the paging file to a VHD connected SCSI controller is not supported" and that is what I did, since I had no other choice: this is a hyper-v generation2 guest, which does NOT SUPPORT or offer IDE-connected virtual disks.

Furthermore, https://www.altaro.com/hyper-v/hyper-v-page-file-settings/ explains: "you cannot place a virtual machine’s swap file on a VHD that is attached to the virtual SCSI chain. This is because the SCSI driver is synthetic, so it doesn’t load until after the virtual machine’s operating system has attempted to initialize its page file. You must place swap files for virtual machines on VHDs attached to the IDE chain."

If that is true, who can tell me what I can do to exclude the Pagefile from replication, if possible at all?

(Ah no, I don't want to run a gen1 machine :-)

One sees many posts against using snapshots on virtualized domain controllers. If the VM is running at the time the snapshot is taken, this makes a good amount of sense. But if the VM is off, how is this fundamentally different than any other means of backup???

In a larger sense, if ALL of the machines in a domain are cleanly shutdown, then snapshots taken, are there really any issues if the entire domain is restored back to the snapshots, even is significant (but less than tombstone) time/operations had occured in the mean time???

Microsoft MVP / ALM Ranger

Dear Sir/Madam, 

The Windows patches were failed to apply on the secondary Hyper-V host server yesterday. Tried 3 times but still fail. Please give advice to this issue. The patches list is stated as below. Thanks.

2019-04 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493446)            

2019-04 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4493467)

2019-04 Cumulative Security Update for Internet Explorer 11 for Windows Server 2012 R2 for x64-based systems (KB4493435)

Best Regards,

Hi all,

I would like to know if it is safe to change my host PC name while running Hyper-V

Will my VMs be affected by this change?

Thanks in advance

Hi, we have recently created a Hyper-V server but after a few days of use we can no longer take backups. If we restart the VM the checkpoint still fail but if we restart the host they begin to work again. Is there a way of releasing whatever process is using the file so we can take checkpoints for backup again? I've attached a screenshot of the error.

Is there an easy way to find out what process is using the avhdx checkpoint file and can this be deleted to allow the checkpoint process to run. Also the VM does not show it has any checkpoints in the HyperV manager so assume these are created as part of a backup process.



Hello,

Microsoft Admin Center states it supports Hyper-V Server 2012 R2 and I must upgrade to Powershell 5.0+.

Hyper-V Server 2012 R2 ships w/ 4.0 and fails to upgrade to 5.0 or above.

It state the OS is not supported.

Any ideas? I can't find anything about this searching online for the past 2 hours...

Thank you!

I part-time manage a branch office IT infrastructure. (More formally, I am developer who has unofficially assumed the IT role.) There are other sites within the company running a common domain. Originally we were not connected  via site-to-site VPN to other sites, so we created our own separate domain. After a number of years things have changed and we are now connected and are moving our IT infrastructure to the common domain. This has been progressing for a few months, generally fairly smoothly.

We also have two Hyper-V hosts, one running Windows Server 2008 R2 Datacenter. I set it up a number of years back and until now have not had any problems. Recently I noticed one of our VMs that I had moved from the old domain to the new domain a few weeks back had failed to register its IP in the DNS. Checking the event log indicated KMS failures. I naively tried to re-activate it: slmgr /ipk 74YFP-3QFB3-KQT8W-PMXWJ-7M648. The screen turned black and indicated that Windows is not genuine.

I have checked several of the other VMs, but there does not seem to be any significant issues so far. Please note that the VM host is still in the original domain. Googling around I found this, I found this indicating to check the SRV record for _vlmcs._tcp. The domain had changed, so this was pointing to the old domain. (Still available if necessary.) I updated it in the new domain DNS. I have also verified that the VM host server is available over port 1688 via telnet.

I then ran the above slmgr /ipk again. It indicates that the key was successfully applied, but Windows still indicates that the environment is not genuine. I'd appreciate some help in resolving this.

Here is the output for slmgr /dlv on the Hyper-V VM host.

(Please let me know if this contains any keys that I should not post here and I will gladly edit it.)

---------------------------

And here is the same output for the problematic VM client.

====================

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

Hello,

I have a server 2016 STD with role Hyper V, and a virtual machine SRV2019 STD

I have on my physical server an "Ethernet" card with ip as a public IP of my provider
Internet works perfectly

In the Hyper V Manager I created an "External Network" virtual switch using my Intel physical adapter

in the configuration of the virtual machine, I assigned him the virtual card "VSwitch"

When I start the VM, it does not have internet.

note: Hyper-V Extensible Virtual Switch is checked on the "Ethernet" card and not "vEthernet", I do not know if it's good

OnPhysical Machine :

Carte Ethernet vEthernet (VSwitch) :

   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
   Adresse physique . . . . . . . . . . . : 00-25-90-D5-xx-xx
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::6961:b193:bc21:xxxxx(préféré)
   Adresse IPv4. . . . . . . . . . . . . .: 37.187.xx.xx(préféré)
   Masque de sous-réseau. . . . . . . . . : 255.255.255.0
   Passerelle par défaut. . . . . . . . . : fe80::205:73ff:fea0:xxxx
                                       37.187.xx.xx
   IAID DHCPv6 . . . . . . . . . . . : 385885584
   DUID de client DHCPv6. . . . . . . . : 00-01-00-01-24-58-E9-A2-00-25-90-D5-FE-xx
   Serveurs DNS. . .  . . . . . . . . . . : 213.186.xx.xx
   NetBIOS sur Tcpip. . . . . . . . . . . : Activé

On the virtual machine

Carte Ethernet Ethernet:

   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
   Adresse physique . . . . . . . . . . . : 00-25-90-D5-xx-xx
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::6961:b193:bc21:xxxxx(préféré)
   Adresse IPv4. . . . . . . . . . . . . .: 169.254.178.75(préféré)
   Masque de sous-réseau. . . . . . . . . : 255.255.0.0
   Passerelle par défaut. . . . . . . . . : fe80::205:73ff:fea0:xxxx

I understand that in 169 it can not work but I do not understand what I have to do

Can you helping me ?

Thanks

I setup a new windows 2019 Standard sever with HyperV.  I can create the Windows 2012R2 VM with no problems.  I can Start the VM with no problems.  I can see the VM started in the bottom window.  I can't connect to the VM to do the Windows install.  When I double click or right click-->Connect, I just get a spinning circle for a few seconds and it disappears.

All of a sudden now I noticed on my windows 10 PC version 1809 using HyperV, I can't connect to any VMs anymore...?

I just noticed using a different windows server 2018R2 and Hypervisor, I can connect to the newly created VM on the new 2019 server.

Any thoughts on how to connect to a VM using a windows v1809 Hypervisor...?

Thanks,

Tom....

Tom Karpowski...

Dear all,

I'm running VMs on my Hyper-V 2016 server connected via iSCSI to a Huawei Storage. The problem is that all the times I find the servers (VMs) in StateSaved-Critical. It says that cannot to virtual machine configuration stoarge.

Can someone help me understand what's wrong?

1. I do can read and write to the volume on the storage,

2. previously, there ware a 2-NODEs FailOver Cluster installation on the servers and then rolled back.

Now I facing this errors all the time,

Here are some eventview logs for more details:

##### EVENT VIEW - START #####

The description for Event ID 16410 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Gestao_13

2BB3240B-3EFD-4BE1-934B-B8E84E54EDAB

%%2147942455

0x80070037

The description for Event ID 20410 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Hypervisor configured mitigations for CVE-2018-3646 for virtual machines.

Processor not affected: false

Processor family not affected: false

Processor supports cache flush: false

HyperThreading enabled: true

Parent hypervisor applies mitigations: false

Mitigations disabled by bcdedit: false

Mitigations enabled: false

The description for Event ID 12240 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

F:\Hyper-V\Virtual Hard Disks\srvphcprd\BK\srvphcprd_data_B0BB85A2-1B11-4B24-9D7D-A4770638172D.vhdx

%%2147942402

0x80070002

The description for Event ID 20848 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

F:\Hyper-V\Virtual Machines\Virtual Machines\775EE935-9331-4CFC-BA28-8BF5A15204FE.vmcx

%%2147942455

0x80070037

##### EVENT VIEW - END #######

Please can someone help me understand whats wrong with this.

Best regards,

Nelson Chamba

nelson chamba

Hi,

I have a small server running at my home (16GB DDR3 RAM, Intel Xeon E3 1245v2, 1TB sata3 HDD, Windows Server 2008 R2 x64) running a few virtual machines mainly Windows Server 2008 R2 X64 and Ubuntu Server. The windows VMs are shutting down as if someone has done a normal OS shutdown from within the VM, you know start > shutdown, or right clicking on the VM within the Hyper V management GUI and clicking shutdown. I checked all the Hyper V sections within the event viewer on the node and it doesn't show any warning or errors.

I tried searching Google and have found no one else with this error.

Kind regards,

Jazzy.

VM snapshot deletion Job is stuck at 50% for windows server 2012R2 VM. Snapshot size is only 110GB and it has been 5hr still job is running. VM is running fine, any suggestion how to fix this without downtime. 

Abhishek

Hi all,

Hope this is not some weird question...

I have a role <<test>> configured in WSFC with 2 x hyper-V VMs inside.
They sit on the same cluster disk 1.

The role and cluster disk 1 are now on node1.  When i try to a live migrate of role <<test>> to  node2, i am prompted with the below error

Failed to initiate the migration of a clustered VM: Only one instance of this resource type is allowed per resource group

Is this working as intended ? or i have configured something wrongly ?  (Can a role holds more then 1 VM ?)

Regards,
Noob

This is a very basic question but just slightly confused as to what does and does not need a virtual switch with a failover cluster setup. 

So we have 4 x 1Gbps NICs and we want to use 2 for host management/VM traffic (teamed) and 2 for storage traffic. We obviously need to create an external vswitch for the vm traffic which is fine but it is the storage I am not sure of. 

We are going to use iSCSI for the storage on a remote NAS so do I need another vswitch for the storage ? 

I think I am just confusing myself in that because the storage is accessed via the network I am thinking you need a virtual switch but is this actually the case or not ? 

Many thanks 

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,

Over the last week or so I've been trying to get Windows VMs migrated from XenServer 7.0 to Hyper-V 2016 Server.

I have tried so many different methods such as:

• Exporting to XVA format, then converting to OVF and extracting the VHD for attaching to a Hyper-V VM
• Using disk2vhd on the live VM for the same
• Running VMware vCenter Converter on the live VM
• Starwind and other tools for converting exported VM formats to Hyper-V formats
• And finally, Microsoft Virtual Machine Converter 3.1

I'm sure there are other methods I've tried, too, but without success. Usually, what happens with basic disk conversions is that Windows starts to boot (the logo displays), and then blue-screens with 'SYSTEM_THREAD_EXCEPTION_NOT_HANDLED'

Microsoft Virtual Machine Converter 3.1 gets to 100% on the 'Convert disk(s)' stage, then fails with 'The object invoked has disconnected from its clients. (Exception from HRESULT: 0x80010108 (RPC_E_DISCONNECTED))'. The firewall is completely disabled on the client and server as I had earlier issues, and BITS is installed on the server.

In terms of the versions of Windows I've tried to migrate, I've used Windows Server 2012 and Windows 10 Pro, both with the same results.

Any ideas? Thanks.

I have successfully replicated all VM's, but 1 VM failed due to the following error:

Cannot enable replication for 'VM02' because one or mor iSCSI disks are attached to the virtual machine.

What doesn't make sense is I am able to do a Live-Migration between Hyper-V host without a single issue, but you can't replicate!

Here is the VM / Host configuration:

The VM has a SAN connected via iSCSI Initiator.  I am not using a Virtual Target or VHD's.  There are 2 Volumes on the SAN and the Volumes are bound as drives E & G.  The SAN is connected to a dedicated switch and BOTH of my Hyper-V hosts have 2 NIC's each connected to the dedicated switch.  BOTH Hyper-V hosts have identical Virtual Switches named SAN1 & SAN2 so no matter what host the VM resides on it can connect to the physical SAN.