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


[Xen-users] CentOS Xen Kernel 2.6.18-164 and Gitco Hypervisor 3.3.1 prob

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] CentOS Xen Kernel 2.6.18-164 and Gitco Hypervisor 3.3.1 problem
From: Ian Murray <murrayie@xxxxxxxxxxx>
Date: Thu, 17 Sep 2009 11:40:51 -0700 (PDT)
Delivery-date: Thu, 17 Sep 2009 11:41:39 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1253212851; bh=ldjul5XuXWtmerzGJqqrHpmHTsPsIMojdpUBCgT8WiA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=LEoxKktweXu/KydGmlCnjKB0/Bv0caUpGwozBzCKywadl0CEdwZr7PrQCd4QrIxCSc6xBejmhtyvzaXmIzZSvivnx0Do6lkXFjthcuaNhsN0NqaxbhFoYRuGneGLHleCOlYy29p65LNEiMuSt8g4RGOkSF7zgVPk9950nyGG8QE=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=s1e6kpoVcrOOfWs3Z/NanSMyXQyk9wRVBPIth4pBFA8uEyewejdQc7bGyV5aHTlzK4PejBodA693BMxRMS4dk4180wwr76D+2yADYNt1Sl/6DC/p2riWivnBgI/qwIstxCtuTkedMmi+6BmbIn+OjreUh2v5TWVRWcAiIxIXrvI=;
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
Hi All,

I upgraded my Dom0 kernel to the above version during a normal yum update. 
After reboot, I got some flashed message about not a proper root and then a 
cannot sync error followed by an (almost) immediate reboot. I have no clue 
where this is logged, if indeed it is. /var/log/messages has yielded nothing, 
but I suspect this is way early in the boot process for that. I will try to 
look for a start-up kernel switch to stop it rebooting immediately.

Running the kernel straight had no issues. I was more intent on just getting my 
server up so reverted to previous kernel and all was back to normal.

I have already asked on the CentOS list and apparently this kernel is not 
having any issues with the hypervisor provided under CentOS.

Whilst I try to get a few more details of exactly what those error messages 
were, I thought I would ask see if anybody has anything similar or if they have 
the above configuration without issue.

Thanks in advance,


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>