From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Wright Subject: phy disks and vifs timing out in DomU Date: Thu, 28 Jul 2011 08:24:38 +0100 (BST) Message-ID: <24093349.14.1311837878822.JavaMail.root@zimbra.overnetdata.com> References: <29902981.10.1311837224851.JavaMail.root@zimbra.overnetdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <29902981.10.1311837224851.JavaMail.root@zimbra.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: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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 2.6.30.1 and has worked perfectly on other systems running a 2.6.18 kernel under Xen 3.4. Any ideas? thanks, Anthony Wright.