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.

Background:  I host a windows 10 Enterprise for Development on my Windows 10 pro computer.  Both are updated to latest patches using windows update. Configuration version 9.0.  I have 32GB on my physical computer, about half reserved for the virtual computer.

The purpose is so that my development environment for my client is separate from my personal computer.

Problem:  After a windows update a few months ago the Enhanced Session that can be chosen on the View from the Hyper-V Manager's Virtual Machine Connection started not functioning. I can view my computer, but not in enhanced mode.

Attempts to correct: I have waited a few additional windows updates, but nothing yet.  Tried to uninstall and reinstall the GUI Management Tools.  I've made sure to keep the configuration version to the latest.

Workarounds: The reason I want the enhanced mode is so that printing, copy/paste, and other things to work while connected, so I can use a remote desktop. However, this can be problematic as I'm also using a vpn from the vm, so opening the computer up so I can remote desktop from outside the network can at times be a pain. Also, when I use a remote desktop, and something happens that I cannot re-connect, the machine gets into a state where the Hyper V Virtual Machine Connection won't be able to see the computer.  So, a shut-down, restart is required to again gain access.

Summary:  I'm looking for suggestions on what I could try to easily resolve.  My guess is that if I rebuilt the computer the problem would go away, but that is a large task for something I can work around.

Would someone please turn on the LIGHT?

Hello,

i can not manage my hyper-v 2012 R2 server with a hyper-v manager on 2019 server (gui). (VM on this hyper-v core server)

With a 2012 R2 gui server i could manage my hyper-v 2012 R2 server without a problem.

using a new 2019 gui server i can not connect to my hyper-v server.

then i update the working 2012 R2 gui server to 2019 gui server, and the hyper-v manager has no the same problem when connecting to the hyper-v 2012 R2 core server.

if i connect to server i get the error: (can not insert picture.. )

Hyper-v Manger popup message with red cross.

"An error occurrd while attempting to connect to server

'fqdn.ofthe.server'. Check that the Virtual Machine Management service is running and that you are authorized to connect to the server.

Hyper- encounterd an error trying to access an object on computer 'fqdn.ofthe.server' because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management services on the computer is running."

I have disabled the firewall on the 2012 R2 core server, i can open RDP the the server without any problem ..

is there a compatibility issue ?? between hyper-v 2012 R2 and server 2019 gui with hyper-v manager ??

thanks for helping..

Today is the third time in five months I've had this issue, and any help is appreciated.

Hyper-V Host HV1 has two VMs, DC1 and APP1.  DC1 and APP1 use a Hyper-V switch to connect to the LAN.  Host and VMs are on the same subnet.  

Sporadically, the guests lose the connection, cannot ping each other, or the host, or their default gateway.  

The only solution I have found that works is to shut down the VMs, remove the virtual network adapter, delete the Hyper-V Switch, then build a new Hyper-V Switch using the same NIC on the host (the host only has two on board NICs, plus iDrac.)  Then assign that to each VM and boot the guests to their OS.  That works, but it then crumps again a few weeks later.  

Tidbits: DC1 is Gen1 VM, while APP1 is Gen2 (DC1 is Server 2003, if that matters... Don't ask why, it's a long story... and APP1 is Server 2012 R2 Standard).  
Host is Server 2012 R2 Standard
HV Manager is 6.3.9600.16384
Host is up to date on firmware from vendor website
Host is fully patched with OS updates
Dell's built in hardware diagnostics show no problems.

I can get log files, if you wish.  

Any help or ideas is _greatly_ appreciated.

Best, 

Jeff

Hi,

I'm migrating from VMware to Hyper-V and have a question regarding the storage for our SQL 2012 Cluster VM's. We would like to do a side-by-side SQL migration to retain the current SQL Failover Cluster config.

Current setup:
- 3x VMWare ESXi 5.5 hosts
- 2x Windows Server 2012 VM's with SQL 2012 Standard
- Failover Cluster for 6x SQL 2012 Clustered Instances
- HP 3PAR Fibre Channel SAN with 17x RDM's for Cluster Storage

New Setup:
- 3x Windows Server 2016 Hyper-V hosts
- 2x Windows Server 2012 VM's with SQL 2012 Standard (converted from VMware)
- Failover Cluster for 6x SQL 2012 Clustered Instances (existing)
- HP 3PAR Fibre Channel SAN (1x 5TB Disk or multiple smaller disks)

Would it be supported to setup the new environment as,
- Failover Cluster for 3x Hyper-V hosts
- Add shared storage from the SAN to the Hyper-V Cluster (either 1x 5TB disk or multiple smaller disks)
- Convert disks to Cluster Shared Storage (CSV's) ***is this supported for SQL 2012 workload??
- Convert SQL VM's from VMware to Hyper-V (retaining existing failover cluster config for SQL)
- Attached new disks to mirror previous setup in VMWare

I've found this link that has good info but it mentions "CSVs don't support the Microsoft SQL Server clustered workload in SQL Server 2012 and earlier versions of SQL Server".
- https://docs.microsoft.com/en-us/windows-server/failover-clustering/failover-cluster-csvs

Are we able to use CSV's on the Hyper-V failover cluster?

Thanks!

Pretty much what the title describes. 

Commands like Get-VMHost fail when just using "Get-VMHost", but are successful when using "Get-VMHost -ComputerName -localhost". However, the documentation of these functions say that omitting the -ComputerName parameter should mean using localhost by default.

This is apparently not the case on my machine. 

What can I do to fix this? The program I use (Docker) is using these commands without the -ComputerName parameter, and hence not working.

Hoping to hear from you, thanks in advance!

Re-posting from this thread:
https://answers.microsoft.com/en-us/windows/forum/windows_other-performance/connecting-to-virtual-machine-management-service/f1c6c189-7937-4bac-b800-0400292ada7c

ORIGINAL POST from itr88:

Overview of environment

Hyper-V host 1 - Server 2016 - not domain bound - static IP - 4 nics (1 mgmt 2 guests and 1 spare)

- software additional to OS (webroot / labtech / veeam backup & replication)

- Runs two guests

--guest1 = DC / FS / DNS / DHCP / Backup server

--guest2 = WEBSERVER

Situation

This morning at 4am, the host reboot because of monthly patches (was not suppose to but a different story altogether), issue since then.

Can connect to host, but cannot connect to hyper-v manager, stuck on this: "connecting to hyper v management service"

We have done the following in troubleshooting

-Setup DHCP and DNS (as this is running on the DC that is not running atm)

-Run MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof

-Uninstall webroot and labtech and patches.

-Ran DCOM fixes and various other attempts to fix this

We have then booted from OS disc, reinstalled OS, after reinstall could access Hyper-V manager, imported VM's, one failed, one succeeded, rebooted server and back to square one, unable to connect to hyper-v manager service.

Hyper-V still runs as we have the webserver running, and we can do some management via powershell, but that's it.

Anyone encounter this or a similar issue, we've searched the internet and we can't find anything closely related to this issue.

RESPONSE:

Did you end-up figuring out what happened, or find a fix?

We experienced the exact same issue on June 17th (the day after your post).

We have two VM host servers. After scheduled Windows patches in the middle-of-the-night, both rebooted.  One came up normal.  But when the other host rebooted, it came up, but none of the VMs were online.

Same thing - It was stuck on "connecting to hyper v management service".

We tried the following, but had no luck
- Reviewed Error logs - (nothing useful, other than the service was not able to change the states of the VMs)
- Tried running MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof
- Uninstalled the recent Windows patches, rebooted

We're running a Lenovo System X server.  We initially thought perhaps it was a firmware issue / incompatibility issue with the latest patch, but uninstalling the patch didn't help.

We ended up re-installing Window Server 2016, after updating all system firmware.  Ran all Windows Updates, then reinstalled Hyper-V role.

With no VMs added, we started Hyper-V manager and it came up.

We did not restore any of the prior VMs. Instead we created a new one. Started it. Rebooted the host, it all came up.

We added two more VMs, rebooted the host, all came up.

Since then, we added the rest of our VMs but have not rebooted the server.  We are definitely concerned about not having yet determined the root cause of this issue, troubleshooting (besides reinstalling everything from scratch) or a fix.  Nothing we did brought the service back, so this is still of great concern.

Any new information you may have on this issue would be highly appreciated.

Hi all,

I'm having a strange issue converting a 2008 R2 server installed on IBM BladeCenter HS22 using disk2vhd and launching a VM

on ProLiant DL380 Gen10 Server 2016 Hyper-V production host that has currently 6 VMs running on it without any issues. 

With GEN 1 the VM stops with a blank screen and a blinking cursor right after pressing the start button.

With GEN 2 I get the following error: 

Virtual Machine Boot Summary

1. SCSI Disk  (0,0)                             NO x64-based UEFI boot loader was found.

2. Network Adapter (00155DFE171C)   The network media is disconnected

I'm not connecting this VM to the network because I currently have a physical production server on the same network and just

testing to see if I could convert it to a VM.

Thank you!

Hi Support,

I have just installed a new server Windows 2019 as a host and as a VM.  This is a new HP DL380, 32 GB ram and raid 5, 15k drives, server and everything is updated. everything looks good in the VM, I have dynamic memory and 10 core cpu in the settings.  the issue is any file transferred between the vm and other machines is extremely slow.  the issue does not exist for the host.  The server does not use the Broadcom network card. There are no applications only an RMM agent, Bit Defender antivirus and Datto backup agent.  The size of the VM is 800 GB.   I appreciate any help. 

thanks,

Jamshid

Hi Support,

I have Winodws server 2019 standard as a host with one VM guests.  Anytime the Host server is rebooted for updates or any other reason (even if I shutdown the VM guest) I getthe unexpected shutdown message on the VM when it comes up or started.  I have been told that this is a know issue and Microsoft will fix it with is update.  but as of now all my hosts are up to date and I am still experiencing this issue.  please advise.

thank you for your help.

Jamshid

Hi. We have three Hyper-V hypervisor running on old USB thumb drives. We need to replace USB drives.

1. Which new device will be better for running hypervisor? SSD or USB thumb drives. 

2. What is best way to clone hypervisor or copy configuration of it?

Hi everyone,

I have a Hyper-V 2019 Core installed. Remote Dekstop on virtual machines works fine when i use Windows 10, but using Remote Deskop app on Macos Mojave with same rdp file giving me an error (0x004) . I have tried several solutions and nothing helps. Can someone mayde help me on this one??

Thanks

Good afternoon,

I am having an issue on our two node cluster where any machine on the second node cannot be pinged and so cannot be accessed - the network cannot see the vm.

Live migration works between Node 1 and Node 2. When the VM is on Node 1 - I can ping and access the VM.

Weirdly - if I live migrate back from Node 2 to Node 1 - the VM cannot be pinged until it is restarted.

Does this make sense? Why would Node 2 not allow connection to the main network? Everything is validating fine, the vSwitch is the same. Firewall has been tested on and off.

It's grinding on me now.

Gareth

Hi all,

I have the same issue on two different Hyper-V host : one with Windows Server 2012 R2 Std, the other one on Windows Server 2016 Std.

The fist symptom that we found is that we cannot connect to the virtual machine via the Hyper-V Manager.
It gives an error message that says : "Cannot connect to the virtual machine. Try to connect again. If the problem persist, contact your system administrator"
There's two buttons, Connect and Exit, if I click connect, the same message will come back.

After digging a bit in the issue, if found out that I was not able to browse on the internet, neither with Internet Explorer, nor Firefox. If I try a bing search to anything, it sends an error message that says :"unable to open the search page". If I try to enter a direct http address, it's just doing nothing with written "This Page can't be displayed" on the tab name.
With Firefox, it's just doing nothing, load for a sec then blank page.

After digging a little bit more, I found out that I was not able to remote desktop the VM that are hosted on the Hyper-V, it gives me an error message that says "An internal error has occured". Thou, I can access these VM with remote desktop from another computer in the network.

More than that, it seems that even searching for Windows Update is not possible : Error code 80070008 - Windows Update ran into a problem.

The two server (2012R2 and 2016)  where it happens are in totally different networks, they have no common point (application installed, ips, ...). The 2012 R2 is not connected to a domain, but host a D.C. and the 2016 is member of an existing domain, but only host a Windows 10 VM.

Best part is that when I reboot the physical server (Hyper-V host), it'll work fine for a day or two, then the issue will come back from nowhere. I tried to look at the Event viewer, I haven't found anything specific or that could be accurate.

If any of you have an idea or anything cause i'm running out of idea now.

The server are in a production state, reinstalling them is not really an option.

Thanks a lot,

Mathieu Rousseaux

i want to Know how to connect USB device like fingerprint reader / Digital Signature in Virtul machine which are hosted in hyper -V host.

pls someone guide.

Rahi Padariya

Edit:  I was able to work around this.  From what I've read, a bare metal restore from a physical to virtual machine is not supported, but that's what I tried and it worked beautifully.  The only thing that went right today.

So, disk2vhd isn't needed (and as we've seen, didn't work).  Instead I took these steps:

1. Control Panel -> File History.  After it finishes searching for drives, at the bottom left of the page is a link to System Image Backup.  Run it, and select a target drive for the backup.  I used a 64Gb key drive.  Next, it will show you the volumes that will be backed up.  It automatically selects (and you cannot deselect) the volumes required for a bare metal restore.  Any additional volumes are optional.  You'll probably want to deselect the target drive for the backup.

2. After the backup is complete, either move the drive over to the Hyper-V host or access it over the network.

3. In Hyper-V Manager, create a VHDX virtual disk from the backup drive.  Then create a blank VHDX that is at least the size of the original machine's system disk (which may have multiple volumes).  In my case, this was a 2Tb disk, to which I added an extra 128Gb just to be sure.  This isn't the size of the image backup, it's the size of the disk from which the image backup was taken.  I made my disks fixed size.  I don't know if it would work otherwise.

4. Create a Gen 2 virtual machine (this was necessary for me since my original machine used EFI boot).  On the SCSI host adapter, attach the blank disk that will take the image restore, and attach a second disk containing the image backup (this can be deleted later). 

5. Create a second SCSI host adapter and attach a DVD drive to it (also may be deleted later).  Not sure if you really need the second adapter but I was just being cautious.  Assign the ISO image for your original machine's install disc (Windows 8.1 Pro Update 1, in my case) to the DVD.  Set the DVD to boot.

6. Run the VM and press a key when prompted to run from the DVD.  Select the Repair option, and drill down until you get to a page with the option for a System Image Restore.  Click on that and then select the drive containing your backup when prompted.  It will inform you that drive C: (your blank drive) will be wiped out and resized to match the original system drive that was backed up.  Then let it run.  In my case it took maybe three or four minutes, but it was a very sparsely populated 2Tb drive.

7. After the restore completes, you should be good to go.  After testing the new VM, I deleted the second SCSI disk with the backup image, as well as the DVD and its host adapter.

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

I ran disk2vhd on a recently built Windows 8.1 x64 machine.  The conversion completed successfully, but I'm having no luck finding the right recipe to booting it in Hyper-V on a Server 2012 R2 machine.  I've tried both Gen 1 and Gen 2 (with and without Secure Boot enabled).  In both cases it apparently fails to find a boot loader.  The virtual disk is VHDX.

I ran disk2vhd twice.  Once including the additional volumes Windows creates for EFI, and once without.  The result is the same either way.

Any help much appreciated.