Live migration of 'Virtual Machine TESTVM' failed.
Virtual machine migration operation for 'TESTVM' failed at migration source 'TESTVM'. (Virtual machine ID)
Planned virtual machine creation failed for virtual machine 'TESTVM': An unexpected network error occurred. (0x8007003B). (Virtual Machine ID).
Live migration of a guest VM can fail for a variety of reasons: CPU incompatiblity, storage path access restriction, offline caching, virtual machine queuing (VMQ), or live migration protocol incompatibilities. Following are some steps to attempt to resolve these issue.
3. VMQ=Disabled on all hosts
4. win32_offlinefilescache=Disabled on all hosts (2019 servers have this setting disabled by default)
6. Spectre Patching=same version on all hosts (Get-WmiObject -ClassName Win32_BIOS).SMBIOSBIOSVersion
7. NTFS / File Share permissions: grant ‘Windows NT\Network Service’, ‘Windows NT\Virtual Servers’, ClusterService, Hyper-V Hosts Group read/write permissions
8. Entity ‘Windows NT\Virtual Servers’ to have runas-service permissions on all Hyper-V Hosts – this should be set in a GP that is applied toward all Hyper-V hosts in the domain
Set-VMProcessor$vmName -CompatibilityForMigrationEnabled 1
$performanceOption='TCPIP' # TCP is most compatible, and the other options are SMB and Compression
Set-VMHost -VirtualMachineMigrationPerformanceOption $performanceOption
Try to disable CSC (offline file cache):
wmic path win32_offlinefilescache call enable false
Method execution successful.
instance of __PARAMETERS
RebootRequired = FALSE;
Enable CPU virtualization. There are many variants of computer BIOS; thus, we’ll just generalize the approach as, ‘set Intel/AMD Virtualization Technology to Enabled.’
To be continued…