From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: phy disks and vifs timing out in DomU (only on certain hardware) Date: Fri, 29 Jul 2011 12:06:05 -0400 Message-ID: <20110729160604.GK5458@dumpdata.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> <4E32D63F.7000809@overnetdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4E32D63F.7000809@overnetdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Anthony Wright Cc: Todd Deshane , "xen-devel@lists.xensource.com" , Ian Campbell List-Id: xen-devel@lists.xenproject.org On Fri, Jul 29, 2011 at 04:48:15PM +0100, Anthony Wright wrote: > Ok, the plot thickens... Please don't top post. > > I have installed virtually identical systems on two physical machines - > identical (and I mean identical) xen, dom0, domU with possibly a md5sum match? > 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.