From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Sharma Subject: Re: Re: Timeout connecting to device Date: Wed, 24 Aug 2005 17:31:27 -0700 Message-ID: <430D115F.5030407@intel.com> References: <430A387C.2030108@intel.com> <430BCF14.2040409@intel.com> <1124858620.17004.96.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1124858620.17004.96.camel@localhost.localdomain> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Rusty Russell Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Rusty Russell wrote: > The trace file is actually better in my experience. Also look for > "error" nodes in the store (although Christian removed some of those > paths in the merge). Thanks, this works for me now: losetup -o 16384 /dev/loop1 /var/images/min-el3-i386.img disk = [ 'phy:loop1,hda1,w' ] But this doesn't work: disk = [ 'file:/var/images/min-el3-i386.img,hda,w' ] xen_blk: Initialising virtual block device driver Registering block device major 3 hda: -Arun