Oracle VM : Live Migration Failed with 'Error: Acquire running lock failed: 256'

(Doc ID 2373652.1)

Last updated on APRIL 02, 2018

Applies to:

Oracle VM - Version 3.2.11 and later
Information in this document applies to any platform.

Symptoms

[1] Live Migration process is not completed due to a lock status job on source server so in AdminServer.log (Manager server) is seen the following error:

<Feb 27, 2018 9:00:46PM GMT> <Info> <ovm.mgr.event.ovs.Command> <Async operation failed on server: support20.cr.oracle.com
Object: ol7-LXC-srv,
PID: 18515,
Server error message: Command: ['xm', 'migrate', '--live', '0004fb000006000006d962a277989f8d', 'support21.cr.oracle.com'] failed (1): stderr: Error: Acquire running lock failed: 256 (from support20.cr.oracle.com)
stdout: Usage: xm migrate <Domain> <Host>
<Feb 27, 2018 9:00:46PM GMT> <Info> <ovm.mgr.api.job.InternalJob> <Job: 1519765244241, Time: 1519765244241, Internal Error (Operation) OVMAPI_5001E Job: 1,519,765,244,2
41/1519765244241/Migrate VM ol7-LXC-srv to Server support21.cr.oracle.com, failed. The job has a Job Failure Event: 1,519,765,246,372/Job Error: Server Async Command Failed/(02/27/2018 09:00:46:444 PM)
Async operation failed on server: support21.cr.oracle,com.
Object: ol7-LXC-srv,
PID: 18515,
Server error message: Command: ['xm', 'migrate', '--live', '0004fb000006000006d962a277989f8d', 'xx.xxx.xxx.x'] failed (1): stderr: Error: Acquire running lock failed: 256 (from support20.cr.oracle.com)
stdout: Usage: xm migrate <Domain> <Host>
<Feb 27, 2018 9:00:47PM GMT> <Info> <ovm.mgr.task.AutoDiscoverTask> <Ignoring discover request for server: support20.cr.oracle.com. It is locked>


[2] Due to a lock job on source server after failed live-migration the error "Acquire running lock failed: 256" is seen in ovs-agent.log, on the other hand on target server attempted live-migrate VM is not found either.

On Source Server:
[2018-02-27 21:00:45 18515] DEBUG (base:269) async call complete: func: migrate_vm pid: 18515 status: 1 output: Command: ['xm', 'migrate', '--live', '0004fb000006000006d962a277989f8d', 'xx.xxx.xxx.x'] failed (1): stderr: Error: Acquire running lock failed: 256 (from yy.yyyy.yyy.yy)
stdout: Usage: xm migrate <Domain> <Host>

Migrate a domain to another machine.

Options:

-h, --help Print this help.
-l, --live Use live migration.
-p=portnum, --port=portnum
Use specified port for migration.
-n=nodenum, --node=nodenum
Use specified NUMA node on target.
-s, --ssl Use ssl connection for migration.
-c, --change_home_server
Change home server for managed domains.

[2018-02-27 21:00:45 18515] INFO (notification:47) Notification sent: {ASYNC_PROC} exit PID 18515
[2018-02-27 21:00:46 26481] INFO (notificationserver:139) Sending notification: {ASYNC_PROC} exit PID 18515
[2018-02-27 21:01:17 18629] DEBUG (service:74) call start: list_vm('0004fb0000030000c829f0155620a28e', '0004fb000006000006d962a277989f8d')

 

[3] On Target Server:

[2018-02-27 21:01:18 5098] ERROR (service:96) catch_error: Command: ['xm', 'list', '--long', '0004fb000006000006d962a277989f8d'] failed (3): stderr: Error: Domain '0004fb000006000006d962a277989f8d' does not exist.
stdout:
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/agent/lib/service.py", line 94, in wrapper
return func(*args)
File "/usr/lib64/python2.4/site-packages/agent/api/hypervisor/xenxm.py", line 237, in list_vm
return get_vm(vm_name)
File "/usr/lib64/python2.4/site-packages/agent/lib/xenxm.py", line 114, in get_vm
info = run_cmd(['xm', 'list', '--long', domain])
File "/usr/lib64/python2.4/site-packages/agent/lib/linux.py", line 49, in run_cmd
raise RuntimeError('Command: %s failed (%s): stderr: %s stdout: %s'
RuntimeError: Command: ['xm', 'list', '--long', '0004fb000006000006d962a277989f8d'] failed (3): stderr: Error: Domain '0004fb000006000006d962a277989f8d' does not exist.
stdout:

Live-migration does not work anymore until the lock job is released on source server using command bellow:
# /usr/sbin/ovs-agent-dlm --unlock --uuid 0004fb000006000006d962a277989f8d

This workaround is described in KM article: Oracle VM 3.0: Error: Acquire running lock failed: 256 (Doc ID 1380333.1) .
BUT this is only a workaround not the final fix.

 

Changes

 No changes.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms