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


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

To: Todd Deshane <todd.deshane@xxxxxxx>
Subject: Re: [Xen-devel] phy disks and vifs timing out in DomU
From: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
Date: Thu, 28 Jul 2011 16:36:44 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 28 Jul 2011 08:38:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAMrPLWKGtozo6YK5FXdJzR4duzsxvR6F7Fuj4_0b4x6GkLateA@xxxxxxxxxxxxxx>
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>
References: <29902981.10.1311837224851.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxx> <24093349.14.1311837878822.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxx> <CAMrPLWKGtozo6YK5FXdJzR4duzsxvR6F7Fuj4_0b4x6GkLateA@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv: Gecko/20110616 Thunderbird/3.1.11
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)
>> [   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?
> You should post your domU config file. Maybe the problem is some
> syntax change from Xen 3.4 to Xen 4.1 or from 2.6.18 kernel to 3.0
> kernel.
> Thanks,
> Todd
I've attached the Dom0 & the DomU kernel configs. Dom0 is running linux
3.0, DomU is running linux

I'm somewhat surprised that the DomU kernel should be important since I
know it runs under Xen 3.4. Does this mean that to upgrade from Xen 3.4
to 4.1 I've also got to upgrade all my VMs?



Attachment: dom0-config
Description: Text document

Attachment: domU-config
Description: Text document

Xen-devel mailing list