From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kyler Laird Subject: Re: Xen error report (as requested) Date: Thu, 15 Dec 2005 09:31:29 -0500 Message-ID: <20051215143129.GB2772@snout> References: <20051214182500.GC24517@snout> <20051215120533.GA11024@leeni.uk.xensource.com> <20051215134230.GZ2772@snout> <20051215135241.GD11024@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20051215135241.GD11024@leeni.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, Dec 15, 2005 at 01:52:41PM +0000, Ewan Mellor wrote: > Could you run xen-bugtool then, and please post your logs so I can have a look > around. It might fail, since yours is quite a low level problem, in which > case please send /var/log/{xend,xend-debug}.log at the least, but hopefully it > will be able to run and create a tarball of stuff for you to send. This was at a time when I was having trouble starting a domU. That turned out to be an issue with my AoE initialization. (Not all partitions are recognized at first.) I just tried switching back to changeset 8365 and was not able to duplicate the problem. I suspect that you already know that Xen breaks apart if one of the domUs fails to start because of a bad root filesystem. I'd chalk this up to a result of my attempt to start a domU using a root filesystem that wasn't available. Thank you for your attention. Sorry I wasn't able to give you something more helpful. --kyler