From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Wright Subject: Re: phy disks and vifs timing out in DomU Date: Thu, 28 Jul 2011 17:00:13 +0100 Message-ID: <4E31878D.7020508@overnetdata.com> 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: multipart/mixed; boundary="------------070501040606060301010605" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Todd Deshane Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --------------070501040606060301010605 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 28/07/2011 16:46, Todd Deshane wrote: > On Thu, Jul 28, 2011 at 3:36 PM, Anthony Wright wrote: >> 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 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) >>>> [ 11.880079] XENBUS: Timeout connecting to device: device/vif/0 (state 0) >>>> [ 11.880146] md: Waiting for all devices to be available before autodetect >>>> >>>> The DomU VM runs linux version 2.6.30.1 and has worked perfectly on other 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've attached the startup config. I've tried more RAM, but that doesn't help, and I can't find anything useful in the xen logs. thanks, Anthony. --------------070501040606060301010605 Content-Type: text/plain; name="xen-startup" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xen-startup" name = '1-2' kernel = '/workspace/agent/appliances/XenFileServer-3.18/kernel' disk = [ 'tap:aio:/workspace/agent/appliances/XenFileServer-3.18/rootfs,xvda1,r' ,'tap:aio:/var/agent/running/1/sysconfig,xvda2,r' ,'phy:/dev/Master/Workspace-1,xvdb1,w' ,'phy:/dev/Master/Filesystem,xvdc1,w' ] pci = [ ] root = '/dev/xvda1' memory = 128 vif = [ 'bridge=br-internal,mac=02:95:8a:d7:d0:48' ] vcpus = 1 extras = '' on_poweroff = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' --------------070501040606060301010605 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --------------070501040606060301010605--