Xen domain migration locking problem

Posted by brodie on Server Fault See other posts from Server Fault or by brodie
Published on 2010-06-10T18:04:00Z Indexed on 2010/06/10 18:13 UTC
Read the original article Hit count: 347

Filed under:
|
|

I am trying to live migrate a VM (domain) between two Xen servers.

I have xen locking (xend-domain-lock = yes) configured with a ocfs2 shared storage between them. This locking is working fine. If I try to start up the VM on the secondary server it refuses to start (which is correct).

The problem I am having is when trying to do live migration, it seems like it is trying to remove the lock twice. The first lock it removes is for "domain test", the second is for "migrating-test" which does not exist. Should their be a lock for this "migrating-test" VM?

These are the relevant options in the xen config file:

(xend-relocation-server yes)
(xend-relocation-port 8002)
(xend-relocation-address '')
(xend-relocation-hosts-allow '')
(xend-domain-lock yes)
(xend-domain-lock-path /var/lib/xen/lock)

This is the section of the log:

[2010-06-10 10:45:57 14488] DEBUG (XendDomainInfo:4054) Releasing lock for domain test
[2010-06-10 10:45:57 14488] INFO (XendCheckpoint:474) SUSPEND shinfo 000c6ceb
[2010-06-10 10:45:57 14488] INFO (XendCheckpoint:474) delta 21ms, dom0 95%, target 0%, sent 57Mb/s, dirtied 173Mb/s 111 pages
 4: sent 111, skipped 0, delta 6ms, dom0 100%, target 0%, sent 606Mb/s, dirtied 606Mb/s 111 pages
[2010-06-10 10:45:57 14488] INFO (XendCheckpoint:474) Total pages sent= 131295 (0.99x)
[2010-06-10 10:45:57 14488] INFO (XendCheckpoint:474) (of which 0 were fixups)
[2010-06-10 10:45:57 14488] INFO (XendCheckpoint:474) All memory is saved
[2010-06-10 10:45:57 14488] INFO (XendCheckpoint:474) Save exit rc=0
[2010-06-10 10:45:57 14488] INFO (XendCheckpoint:123) Domain 22 suspended.
[2010-06-10 10:45:57 14488] DEBUG (XendDomainInfo:2757) XendDomainInfo.destroy: domid=22
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:2227) Destroying device model
[2010-06-10 10:45:58 14488] INFO (image:567) migrating-test device model terminated
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:2234) Releasing devices
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:2247) Removing vif/0
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:1137) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:2247) Removing vkbd/0
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:1137) XendDomainInfo.destroyDevice: deviceClass = vkbd, device = vkbd/0
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:2247) Removing console/0
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:1137) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:2247) Removing vbd/51712
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:1137) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51712
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:2247) Removing vfb/0
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:1137) XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2010-06-10 10:45:58 14488] DEBUG (XendDomainInfo:4054) Releasing lock for domain migrating-test
[2010-06-10 10:45:59 14488] ERROR (XendDomainInfo:4070) Failed to remove unmanaged directory /var/lib/xen/lock/b01515ae-9173-03cb-0cb7-06f3dfbede8b.

© Server Fault or respective owner

Related posts about linux

Related posts about xen