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

[Anthony Wright <anthony@xxxxxxxxxxxxxxx>]

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 2.6.30.1 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 2.6.30.1.

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?

thanks,

Anthony.

Attachment: dom0-config
Description: Text document

Attachment: domU-config
Description: Text document

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