From mboxrd@z Thu Jan  1 00:00:00 1970
From: Patrick O'Rourke <porourke@egenera.com>
Subject: Re: domU crash
Date: Fri, 19 Aug 2005 14:56:32 -0400
Message-ID: <43062B60.2090701@egenera.com>
References: <4304F114.2080103@egenera.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4304F114.2080103@egenera.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/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/cgi-bin/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: Patrick O'Rourke <porourke@egenera.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Patrick O'Rourke wrote:

> I compared the domU .config with my previous working version from 8/11 
> and noticed that CONFIG_XEN_NETDEV_GRANT_{TX,RX} options are now turned 
> on (the only domU config changes).  So I rebuilt the domU and it booted 
> fine, network came up, etc.

Just to follow up, the reason is for the crash was that I had built my 
dom0 kernel with an older config (one I've been using for this machine) 
and as a result the dom0 kernel was still being built with these options 
off.  Once I enabled the options in both dom0 and domU, the issue went away.

Pat

-- 
Patrick O'Rourke
porourke@egenera.com