[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Upgrading xen from CentOS 5.0 to 5.2


  • To: Xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Alain Barthe" <ab266061@xxxxxxxxx>
  • Date: Wed, 20 Aug 2008 10:19:21 +0200
  • Cc:
  • Delivery-date: Wed, 20 Aug 2008 01:19:58 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=aCfBblAhhdeGrJkVE23RKmAI6SCZc1Fc8w3dUVI3PuUPzxUKILLPQ4RaJBnzB9pAJc ColkdRvhoxZibvTgcq++FQXEFA0OfE8W0HargE4VDte9c4173wIzoVB00fL6ktMGNJY0 O7hNRuTvzfUXBSKV0fAmEVVvgazxJjBWcY3Us=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

We are planning to upgrade our dom0s from CentOS5.0 to CentOS 5.2, using the xen version shipped with the OS : the RPM versions are respectively 3.0.3-25.el5 and 3.0.3-64.el5_2.1, I don't know exactly to which version of Xen it corresponds (but it should be further than 3.0.3, right ?). Kernel versions are resp. 2.6.18-8.el5xen and 2.6.18-92.el5xen.

As we want to avoid any interruption of service, domUs must be live migrated from the old version to the newer one, and also back if something wrong happens.

Live migration from 5.0 to 5.2 is OK, but not 5.2 to 5.0. In this case, all looks like fine on the from dom0, but the domU never appears on the target dom0, with the following error in the logs:

[2008-08-20 09:40:57 xend 23799] INFO (XendCheckpoint:239) Reloading memory pages:   0%
[2008-08-20 09:41:02 xend 23799] INFO (XendCheckpoint:239) Error when reading region pfn types: 14
[2008-08-20 09:41:02 xend 23799] INFO (XendCheckpoint:239) Restore exit with rc=1
(...)

I tried with a CentOS5.0 domU and a CentOS5.2 one : same result.

My question is: is it normal, or do I miss something ? Is there a way to make this working ?

Thanks for your replies.

Alain.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.