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/
Home Products Support Community News


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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] phy disks and vifs timing out in DomU
From: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
Date: Thu, 28 Jul 2011 08:24:38 +0100 (BST)
Delivery-date: Thu, 28 Jul 2011 00:25:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <29902981.10.1311837224851.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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)
[   11.880079] XENBUS: Timeout connecting to device: device/vif/0 (state 0)
[   11.880146] md: Waiting for all devices to be available before autodetect

The DomU VM runs linux version and has worked perfectly on other 
systems running a 2.6.18 kernel under Xen 3.4.

Any ideas?


Anthony Wright.

Xen-devel mailing list