From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Wright Subject: Re: phy disks and vifs timing out in DomU (only on certain hardware) Date: Fri, 29 Jul 2011 16:48:15 +0100 Message-ID: <4E32D63F.7000809@overnetdata.com> References: <29902981.10.1311837224851.JavaMail.root@zimbra.overnetdata.com> <24093349.14.1311837878822.JavaMail.root@zimbra.overnetdata.com> <4E31820C.5030200@overnetdata.com> <1311870512.24408.153.camel@cthulhu.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1311870512.24408.153.camel@cthulhu.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: Todd Deshane , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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. >