I have 2 Para and 1 Full vm hosted in CentOS 5.2 host with xen 3.0.3 running. If i live migrate to another node it works. But sometimes (2 out of 10) migration fails and I get new instances (newly started) xen guests in another node.
xen log tells something like this (though some time it reports about XC_SAVE issue)
2008-10-09 15:27:57 xend.XendDomainInfo 10762] DEBUG (XendDomainInfo:791) Storing domain details: {\047console/ring-ref\047: \047399336\047, \047console/port\047: \0472\047, \047name\047: \047migrating-guest03\047, \047console/limit\047: \0471048576\047, \047vm\047: \047/vm/8be732a5-44b4-bf92-d237-91d55ed6db31\047, \047domid\047: \0479\047, \047cpu/0/availability\047: \047online\047, \047memory/target\047: \047524288\047, \047store/ring-ref\047: \047205070\047, \047store/port\047: \0471\047}
[2008-10-09 15:27:57 xend.XendDomainInfo 10762] ERROR (XendDomainInfo:1631) XendDomainInfo.resume: xc.domain_resume failed on domain 9.
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1625, in resumeDomain
self.createDevices()
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1682, in createDevices
self.createDevice(n, c)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1155, in createDevice
return self.getDeviceController(deviceClass).createDevice(devconfig)
File "/usr/lib64/python2.4/site-packages/xen/xend/server/DevController.py", line 106, in createDevice
raise VmError("Device %s is already connected." % dev_str)
VmError: Device 0 (vkbd) is already connected.
[2008-10-09 15:27:57 xend 10762] DEBUG (XendCheckpoint:136) XendCheckpoint.save: resumeDomain
--------
What should be the proper measures to avoid this issue?
Thanks
Paras.