From mboxrd@z Thu Jan 1 00:00:00 1970 From: Todd Deshane Subject: Re: phy disks and vifs timing out in DomU Date: Thu, 28 Jul 2011 15:46:49 +0000 Message-ID: References: <29902981.10.1311837224851.JavaMail.root@zimbra.overnetdata.com> <24093349.14.1311837878822.JavaMail.root@zimbra.overnetdata.com> <4E31820C.5030200@overnetdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4E31820C.5030200@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: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, Jul 28, 2011 at 3:36 PM, Anthony Wright w= rote: > On 28/07/2011 16:01, Todd Deshane wrote: >> On Thu, Jul 28, 2011 at 7:24 AM, Anthony Wright wrote: >>> I have a 32 bit 3.0 Dom0 kernel running Xen 4.1. I am trying to run a 3= 2 bit PV DomU with two tap:aio disks, two phy disks & 1 vif. The two tap:ai= o disks are working fine, but the phy disks and the vif don't work and I ge= t the following error messages from the DomU kernel during boot: >>> >>> [ =A0 =A01.783658] Using IPI No-Shortcut mode >>> [ =A0 11.880061] XENBUS: Timeout connecting to device: device/vbd/51729= (state 3) >>> [ =A0 11.880072] XENBUS: Timeout connecting to device: device/vbd/51745= (state 3) >>> [ =A0 11.880079] XENBUS: Timeout connecting to device: device/vif/0 (st= ate 0) >>> [ =A0 11.880146] md: Waiting for all devices to be available before aut= odetect >>> >>> The DomU VM runs linux version 2.6.30.1 and has worked perfectly on oth= er 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 meant the domU guest configuration file (the xm/xl one). I meant that you might be specifying the disk line incorrectly. > > 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? --=20 Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/