Unable migrate VM from Hyper-V 2019 to Hyper-V 2022 (error 32784)

Semen Anikin (Finstek) 47 Reputation points
2021-09-10T01:41:05.897+00:00

Hi there, I have issue with Live migration between two hosts. One server is Windows Server 2019 Datacenter (Core). another one is Windows Server 2022 Datacenter (Core)
Both servers belong same domain and located in same VLAN (actually, they share one rack).
Kerberos delegation is configured for both servers. When I am trying move VM from server 2019 to 2022, I am getting error

130926-image.png

It seems new hyper-v server does not accept live migration from old one. Is it bug? How can I avoid it?

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,538 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 39,351 Reputation points
    2021-09-10T13:38:22.89+00:00

    Hello Sunnykey,

    You have received the following error message

    " Hyper-V did not find virtual machines to import from the location <folder location>.
    The operation failed with error code '32784'. "

    This usually happens when you try to import a VM that is exported from a Windows Server 2012 R2 Hyper-V host into a Windows Server 2012 Hyper-V host.

    In order to overcome the above error you must execute the below steps,

    1. Create a new NIC Team on a host computer or VM
    2. Use live migration without Failover Clustering to move a virtual machine
    3. Configure Multipath I/O for your StorSimple device

    If Problem doesn't resolve, do follow the below link for detailed understanding,

    https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/importing-a-virtual-machine

    Hope this answers all your queries, if not please do repost back.
    If an Answer is helpful, please click "Accept Answer" and upvote it : )

  2. Christian Reichhoff 1 Reputation point
    2021-11-04T13:41:40.37+00:00

    I can confirm that this seems to be a bug in HyperV 2022 component.

    We even cannot livemigrate via VMM 2019:

    "The virtual machine "YYYY" cannot be migrated or cloned by VMM because the version "10.0.20348.320" of the virtualization software on the target host "xyz.XXX.de" is not compatible with the version of the virtualization software on the source host "10.0.14393.1358".

    How can we avoid shutting down all the machines?

    Edit:
    source host 2016 server:
    Get-VMHostSupportedVersion

    Name Version IsDefau

    Microsoft Windows 8.1/Server 2012 R2 5.0 False
    Microsoft Windows 10 1507/Server 2016 Technical Preview 3 6.2 False
    Microsoft Windows 10 1511/Server 2016 Technical Preview 4 7.0 False
    Microsoft Windows Server 2016 Technical Preview 5 7.1 False
    Microsoft Windows 10 Anniversary Update/Server 2016 8.0 True

    target host 2022 server:
    Get-VMHostSupportedVersion

    Name Version IsDefault

    Microsoft Windows 10 Anniversary Update/Server 2016 8.0 False
    Microsoft Windows 10 Creators Update 8.1 False
    Microsoft Windows 10 Fall Creators Update/Server 1709 8.2 False
    Microsoft Windows 10 April 2018 Update/Server 1803 8.3 False
    Microsoft Windows 10 October 2018 Update/Server 2019 9.0 False
    Microsoft Windows 10 May 2019 Update/Server 1903 9.1 False
    Microsoft Windows 10 May 2020 Update/Server 2004 9.2 False
    Microsoft Windows 10 (Manganese) 9.3 False
    Microsoft Windows Server 2022 10.0 True

    All source VMs are hardwarelevel 8.0

    0 comments