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/
Home Products Support Community News


Re: [Xen-users] New and Current Xen Systems no longer fully boot and pa

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] New and Current Xen Systems no longer fully boot and pause themselves
From: Ricky Burgin <ricky@xxxxxxx>
Date: Thu, 29 Oct 2009 02:40:43 +0000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 28 Oct 2009 19:41:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f0910281936w4bfd978dk5de8389de47681a5@xxxxxxxxxxxxxx>
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>
References: <4AE7192B.5050407@xxxxxxx> <20091028120649.GB1434@xxxxxxxxxxx> <4AE83481.6000203@xxxxxxx> <7207d96f0910281936w4bfd978dk5de8389de47681a5@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20090715 Lightning/1.0pre Thunderbird/3.0b3
Actually I believe the kernel wasn't updated as it was one from the openvz repositories which allowed me to run Xen instances and OpenVZ containers simultaneously on the same system. This did not update during the 5.3 to 5.4 update.

On 29/10/2009 02:36, Fajar A. Nugraha wrote:
On Wed, Oct 28, 2009 at 7:09 PM, Ricky Burgin <ricky@xxxxxxx> wrote:
Hi Pasi,

Thanks for the response. This seems to have been caused by an update from
CentOS 5.3 to 5.4. I'm not exactly sure what packages were specifically
affected during the update, but after reluctantly rebooting the server, it
came back up and Xen started functioning completely normally. Could quite
easily have been xenconsoled, I suppose.
Xen userland must match the version of hypervisor you're running.
Since upgrading to Centos 5.4 should've include kernel-xen (which also
contain the hypervisor) and xen (the userland), it makes sense that
you have to reboot to have it function properly.

I usually exclude these packages from normal update, and only update
them just before I reboot the server:
kernel kernel-devel kernel-xen kernel-xen-devel xen xen-libs glibc
glibc-common glibc-devel glibc-headers glibc-utils


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Xen-users mailing list