Re: phy disks and vifs timing out in DomU (only on certain hardware)

[Anthony Wright <anthony@overnetdata.com>]

Ok, the plot thickens...

I have installed virtually identical systems on two physical machines -
identical (and I mean identical) xen, dom0, domU with possibly a
slightly different configuration for the domU. They're as close as I can
get without imaging the disk. On both machines Dom0 starts normally, but
on one physical machine the DomU starts correctly seeing the two tap:aio
disks, the two phy disks and the vif, while on the other physical
machine the DomU only sees the two tap:aio disks.

The two pieces of hardware are quite different one is a 32 bit processor
from 2000/2001 (this is the one that works), the other is a much more
modern 64 bit processor about a year old.



On 28/07/2011 17:28, Ian Campbell wrote:
> On Thu, 2011-07-28 at 11:36 -0400, Anthony Wright wrote:
>> 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? 
> The domU ABI is stable so this should never be necessary (of course bugs
> do happen).
>
> Ian.
>