WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Migration fails

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Migration fails
From: "Paras pradhan" <pradhanparas@xxxxxxxxx>
Date: Thu, 9 Oct 2008 16:48:11 -0500
Delivery-date: Thu, 09 Oct 2008 14:48:53 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=oYb7tekXsTaD+N4nYvp8+hCwasToLm9Ta58kytKt3aE=; b=ilvh5ZC7kuEi23B5/pJEBsVfz0cIWEuavs7dbuqXscrG/6yqRVLslk2GHb8qN/KMCS 479yGtzsaryzPuGb/cUII/zl6XVnLyvuIWElWPgYlaPDYNvChilSxpPzCknSXKqbH5qi gHjlteIQ3ZlJp+UOyQRdGw+ARp54KHYT8M9Jk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=e0dIlg4jziL9DQKivVIkxDmj+REVqF6xhZSY5mCtjj+LIVg5OuDwTJQuU3pbYWagDw DbUnxIZEjgkOY9yay8heRB/HenxB5ae5e8+0v3mc/nkm1fx312BbyB6pEh8ikP8Cygcb AIjk1Nsb7hOvGBWvzFuT+p11DctIOQbDjqgDU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
List,

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.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Migration fails, Paras pradhan <=