WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] phy disks and vifs timing out in DomU

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 <anthony@xxxxxxxxxxxxxxx> 
> > wrote:
> >> On 28/07/2011 16:01, Todd Deshane wrote:
> >>> On Thu, Jul 28, 2011 at 7:24 AM, Anthony Wright <anthony@xxxxxxxxxxxxxxx> 
> >>> 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'

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel