On 29/07/2011 16:55, Konrad Rzeszutek Wilk wrote:
> 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)?
>
The output from block-list is:
Vdev BE handle state evt-ch ring-ref BE-path
51729 0 764 3 10 10 /local/domain/0/backend/vbd/764/51729
51745 0 764 3 11 11 /local/domain/0/backend/vbd/764/51745
51713 0 764 4 8 8
/local/domain/0/backend/qdisk/764/51713
51714 0 764 4 9 9
/local/domain/0/backend/qdisk/764/51714
The two vbds map to two LVM logical volumes in two different volume groups.
On 29/07/2011 17:06, Konrad Rzeszutek Wilk wrote:
>> > I have installed virtually identical systems on two physical machines -
>> > identical (and I mean identical) xen, dom0, domU with possibly a
> md5sum match?
Yes - md5sum match on all the key components, i.e. xen, dom0 kernel,
99.9% of the root filesystem, the domU kernel & 99.9% of the domU
filesystem. Where there isn't a precise match is on some of the config
files. I don't think these should have any effect, but I will have a go
at mirroring the disks (I can't swap disks since one is SATA & the other
IDE).
I also was having problems with the vif device, and got a kernel bug
report that could potentially relate to it. I've attached two syslogs.
Anthony.
messages.1
Description: Text document
messages.2
Description: Text document
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home