From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dave McCracken <dcm@mccr.org>
Subject: Problem running latest Xen unstable hypervisor with
	latest Linux kernels
Date: Fri, 21 May 2010 08:55:31 -0500
Message-ID: <201005210855.31396.dcm@mccr.org>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
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: Keir Fraser <Keir.Fraser@eu.citrix.com>, Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen Developers List <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org


I have a test box set up to run mainline Xen unstable hypervisor and a guest 
running the latest Linux builds from Jeremy.  Last week it all worked fine.  
This week when I pulled the latest unstable it stopped working.

Specifically I can boot up dom0 just fine.  When I try to start the guest Linux 
gets as far as "blkfront: xvdb1: barriers enabled", then hangs.  This happens 
with the xen/master branch as well as xen/core.  Returning to last week's 
hypervisor lets me boot the guest just fine.

I assume I have some combination of config options set/not set that no longer 
works with the new hypervisor code.  Is there something simple I need to 
change?

Thanks,
Dave McCracken