My Oracle Support Banner

OLVM: Solution for Intensive VM Live Migration Failure (Doc ID 2700914.1)

Last updated on AUGUST 15, 2020

Applies to:

Linux OS - Version Oracle Linux 7.7 with Unbreakable Enterprise Kernel [4.14.35] and later
Linux x86-64

Symptoms

The symptoms for intensive VM live migration failure is 'migration stalling' errors seen in vdsm.log:

2020-07-27 16:33:55,347+0900 WARN (migmon/960d5a81) [virt.vm] (vmId='xxxxxxxxx') Migration stalling: remaining (13253MiB) > lowmark (492MiB). (migration:854)
2020-07-27 16:34:05,349+0900 WARN (migmon/960d5a81) [virt.vm] (vmId='xxxxxxxxx') Migration stalling: remaining (12643MiB) > lowmark (492MiB). (migration:854)
2020-07-27 16:34:15,351+0900 WARN (migmon/960d5a81) [virt.vm] (vmId='xxxxxxxxx') Migration stalling: remaining (12032MiB) > lowmark (492MiB). (migration:854)
2020-07-27 16:34:25,354+0900 WARN (migmon/960d5a81) [virt.vm] (vmId='xxxxxxxxx') Migration stalling: remaining (11423MiB) > lowmark (492MiB).(migration:854)
2020-07-27 16:38:08,899+0900 WARN (migmon/e836013d) [virt.vm] (vmId='xxxxxxxxx') Migration stalling: remaining (237MiB) > lowmark (80MiB). (migration:854)
2020-07-27 16:38:08,899+0900 WARN (migmon/e836013d) [virt.vm] (vmId='xxxxxxxxx') Aborting migration (migration:916)

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
 Method 1: Use "suspend workload if needed" policy
 Method 2: Auto-convergence
 Method 3: Migration Compression
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.