From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: XENBUS: Waiting for devices to initialise Date: Mon, 28 Jun 2010 08:04:59 -0400 Message-ID: <20100628120459.GA3328@phenom.dumpdata.com> References: <345FEDE4-F5ED-4F63-AEF3-A074C1A98755@clustered.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <345FEDE4-F5ED-4F63-AEF3-A074C1A98755@clustered.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: John Morrison Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sun, Jun 27, 2010 at 03:31:31PM +0100, John Morrison wrote: > Hi, > > We have many dom0's working fine, but recently we are seeing a large number of cases when rebooting a domU results in:- > > XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... Look what are connected and which ones aren't. The ones that are not connected are the source of the fault. > > [2010-06-27 15:21:53 11418] DEBUG (XendDomainInfo:1709) XendDomainInfo.handleShutdownWatch > [2010-06-27 15:21:53 11418] DEBUG (DevController:139) Waiting for devices vif. > [2010-06-27 15:21:53 11418] DEBUG (DevController:144) Waiting for 0. > [2010-06-27 15:21:53 11418] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vif/142/0/hotplug-status. > [2010-06-27 15:22:30 11418] INFO (XendDomain:1182) Domain hub (142) unpaused. > [2010-06-27 15:27:32 11418] WARNING (XendDomainInfo:1886) Domain has crashed: name=hub id=142. > [2010-06-27 15:27:32 11418] DEBUG (XendDomainInfo:2732) XendDomainInfo.destroy: domid=142 > [2010-06-27 15:27:32 11418] DEBUG (XendDomainInfo:2207) Destroying device model > > xm create test results in the domU being started in a paused state, xm unpause test gives the above error. > > Rebooting dom0 fixes the issue - the problem being this brings down 15 domU's as well ! > These dom0's have been up for about 160 days without issues. > > Any pointers ? > > Thanks > > John > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel