From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: boot failure in recent cset... dom0 compat issue?
Date: Fri, 30 Jan 2009 15:55:00 +0000
Message-ID: <C5A8D354.1FD6%keir.fraser@eu.citrix.com>
References: <9b34506b-01c3-4bb2-b940-3661c23e3c4e@default>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <9b34506b-01c3-4bb2-b940-3661c23e3c4e@default>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Dan Magenheimer <dan.magenheimer@oracle.com>, "Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 30/01/2009 15:51, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

>> Sorry, that was a typo, should have been 3.3(.0)-timeframe
>> 2.6.18.8-based dom0, built 2008 Sept 18, probably from whatever
>> was auto-hg-pull'ed by a Xen build on that day.  (Is there
>> a way similar to xm info to check the c/s of a dom0?)
> 
> In case it matters, it appears dom0 was c/s 664 from
> http://xenbits.xensource.com/linux-2.6.18-xen.hg
> (Found from code examination... is there a better way
> to find the c/s of a dom0?)

The cset doesn't get embedded in the kernel anywhere, unfortunately.

 -- Keir