From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: phy disks and vifs timing out in DomU Date: Fri, 29 Jul 2011 11:55:02 -0400 Message-ID: <20110729155502.GJ5458@dumpdata.com> References: <29902981.10.1311837224851.JavaMail.root@zimbra.overnetdata.com> <24093349.14.1311837878822.JavaMail.root@zimbra.overnetdata.com> <4E31820C.5030200@overnetdata.com> <4E31878D.7020508@overnetdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4E31878D.7020508@overnetdata.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: Anthony Wright Cc: Todd Deshane , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, Jul 28, 2011 at 05:00:13PM +0100, Anthony Wright wrote: > On 28/07/2011 16:46, Todd Deshane wrote: > > On Thu, Jul 28, 2011 at 3:36 PM, Anthony Wright wrote: > >> On 28/07/2011 16:01, Todd Deshane wrote: > >>> On Thu, Jul 28, 2011 at 7:24 AM, Anthony Wright wrote: > >>>> I have a 32 bit 3.0 Dom0 kernel running Xen 4.1. I am trying to run a 32 bit PV DomU with two tap:aio disks, two phy disks & 1 vif. The two tap:aio disks are working fine, but the phy disks and the vif don't work and I get the following error messages from the DomU kernel during boot: > >>>> > >>>> [ 1.783658] Using IPI No-Shortcut mode > >>>> [ 11.880061] XENBUS: Timeout connecting to device: device/vbd/51729 (state 3) > >>>> [ 11.880072] XENBUS: Timeout connecting to device: device/vbd/51745 (state 3) What device does that correspond to (hint: run xl block-list or xm block-list)? > disk = [ > 'tap:aio:/workspace/agent/appliances/XenFileServer-3.18/rootfs,xvda1,r' > ,'tap:aio:/var/agent/running/1/sysconfig,xvda2,r' > ,'phy:/dev/Master/Workspace-1,xvdb1,w' > ,'phy:/dev/Master/Filesystem,xvdc1,w'