Windows 10: Live migrate from HyperV 2016 to HyperV 2025 cluster fails with 0x8009030D

A 2016 HyperV cluster and a 2025 HyperV cluster in same AD. Trying to Live migrate using shared nothing CredSSP, but fails with 0x8009030DTried to disable Credential Guard... But Regardless hos I tried, I always ended up with:VirtualizationBasedSecurityStatus : 2Has anyone done a successful Live Shared Nothing migration who wants to share how they did?

:)

 

HYPERV live migration between 2 differents intel processor failed

Hello,

I have a cluster with 4 hyper V.

I have 2 servers with a GenuineIntel Intel64 Family 6 Model 85 Stepping 4 processor,

and the 2 others with GenuineIntel Intel64 Family 6 Model 85 Stepping 7 processor.

Since i migrated my hyperV servers from 2016 to 2019, the live migration between the servers with differents processors failed. (error 21502).

The compatibility box is checked.

I would like some help.

Thanks.

 

HYPERV live migration between 2 differents intel processor failed

Ok,

It's done.

HYPERV live migration between 2 differents intel processor failed - Microsoft Q&A

Thanks

 

Failover Cluster VM did not migrated to another HyperV cluster host server

Hi All,

I am having issues a few times that one of the failover Cluster HyperV host server01 got one physical network port disconnected ( don't know how as the switch was showing connecting and up) and all VMs on that Host server got down. we have four network ports teaming together and only one physical network port was saying as disconnected. however, with network teaming, server01 was on the network and provided all information to our monitoring tool but all VMs went offline. we have another 7 servers part of this failover cluster and somehow no VMs migrated to another host.

in addition, I try to live to migrate all VMs another server but waited for about 15-20 minutes but nothing happen. last I have to turn off server01 and then all VMs migrated to another failover cluster host servers.

check Cluster logs and can't see any errors there. on server01 systems event log saying only

"Member Nic {0bb58341-0b32-4595-8769-2fdee0818e26} Disconnected."

then all VMs went down.

on the server only one network teaming port and all physical connected network ports part of this one Teaming port like to know how come all VMs went down from only one network port status ? what other logs should I know.

I am after more specific failover cluster storage communication status information and error when this happens but can't find any error so where should I check?

Thanks,

Prakash