Re: [Xen-users] CentOS Xen Kernel 2.6.18-164 and Gitco Hyperviso

To:	Ian Murray <murrayie@xxxxxxxxxxx>, Boris Derzhavets <bderzhavets@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject:	Re: [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 16:21:36 -0700 (PDT)
Cc:
Delivery-date:	Thu, 17 Sep 2009 16:22:17 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1253229696; bh=xnRP4eSlYaFqH1wutLeZ3AiQoGeOoylVkLTgLVLZgoo=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=VW2mgqtCrT4KmG9eNz/sa6nYWnuuN43uqakV0FGCYCEWqFWjZahTp6vsuQkWYQhdYfBfcVdte82VmpaM4pFVZgt0TGiWsb3PggsLyiKV7Xy8aGKff39RrGTGuX+iQR5+uV+bpGLjGSIn4m6dDgpqhRNYR3vjZ/RnhBMmSsA7MR0=
Domainkey-signature:	a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=eYG8Lgqq9cp30+JzZnRbm4Sxm+zWWLP6lHj2hgPBBNfnFbPBhVB1dO1kglEvXlvAGWt/3iSocv5OprBFddj2QCw7XBKSM6OE6ifOfH7+Z84xuadR3+NRmeGuCcNUJkAp++HvPhyNwYOoD4wxybXY6ca3KzYnsqm1fD1aOCJN+6U=;
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<107990.33701.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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:	<913649.71071.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <107990.33701.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

Turned out I have an extra initrd image file for the problematic kernel with 
the suffix ".dup_orig" on it. I removed a few old kernels and removed and 
re-added the 2.6.18-164 xen kernel and then all was fine.

Thanks anyway.



----- Original Message ----
> From: Ian Murray <murrayie@xxxxxxxxxxx>
> To: Boris Derzhavets <bderzhavets@xxxxxxxxx>; xen-users@xxxxxxxxxxxxxxxxxxx
> Sent: Thursday, 17 September, 2009 22:15:26
> Subject: Re: [Xen-users] CentOS Xen Kernel 2.6.18-164 and Gitco Hypervisor 
> 3.3.1 problem
> 
> 
> >>I upgraded my Dom0 kernel to the above version during a normal yum >update
> >
> >Are you saying that CentOS Xen Hypervisor is 3.3.1 in meantime ?
> >I guess normal yum update goes only to CentOS Repo.
> >I believe that yum install Gitco's rpms along with gitco's repo activated
> >may bring your hypervisor to 3.3.1
> 
> Sorry, I may not have been explicit. I am currently using the Xen hypervisor 
> from Gitco, which is 3.3.1 and the xen kernel from normal CentOS repos. Xen 
> hypervisor hasn't changed, nor did I want it to.
> 
> Thanks.
> 
> 
> Send instant messages to your online friends http://uk.messenger.yahoo.com
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users





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

WARNING - OLD ARCHIVES

xen-users

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