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:51:49 +0000
Message-ID: <C5A8D295.1FD2%keir.fraser@eu.citrix.com>
References: <1938a110-71c6-4d49-b011-d34e2a9f4bc0@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: <1938a110-71c6-4d49-b011-d34e2a9f4bc0@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:39, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

> I can confirm that c/s 19064 boots my dom0 fine and
> c/s 19065 fails to boot.
> 
>>> 3.1-timeframe 2.6.18.8-based dom0.
> 
> 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?)
> 
> My machine is a standard Intel Weybridge box (though
> its possible the firmware is old).

Do you yet know whether an up-to-date dom0 kernel works for you?

 -- Keir