From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: Unstableness in grant table block drivers Date: Thu, 14 Apr 2005 10:00:52 -0500 Message-ID: <20050414150052.GE27571@us.ibm.com> References: <425DCAC4.6030407@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: cwc22@cam.ac.uk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org * Christopher Clark [2005-04-13 21:04]: Hi, > The machines you can't get to start domUs, and symptom of not finding > the root filesystem is exactly what you'd see if your dom0 and domU > configs don't match; either both or neither need to be using grant > tables for transport. Your other issues will need more investigation, I build xen-unstable nightly and install it completely to my test box. My configs between dom0 and domU are always identicle except for priviledged domain. > and a reproducable scenario would be extremely helpful indeed. My scenario is building the default configs either as UP or with adding in CONFIG_SMP. The resule is always, dom0 will boot, domU will not. domU fails with not finding /dev/console and no root device. I use loopback device mounts exported as /dev/sda1. As soon as I turn off CONFIG_XEN_BLKDEV_GRANT in dom0/U configs, the domU boots properly. I build with debug=y and I can generate any sort of dump or information you need to track this down. Let me know what you need. -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx (512) 838-9253 T/L: 678-9253 ryanh@us.ibm.com