From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Hanquez Subject: Re: why xenstore-* hangs if xenstored is not started Date: Tue, 22 Jun 2010 09:26:59 +0100 Message-ID: <4C2073D3.1060101@eu.citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit 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: Keir Fraser Cc: "xen-devel@lists.xensource.com" , Yu Zhiguo List-Id: xen-devel@lists.xenproject.org On 22/06/10 09:06, Keir Fraser wrote: > On 22/06/2010 08:56, "Vincent Hanquez" > wrote: > >> On 22/06/10 08:45, Keir Fraser wrote: >>> Does the xenstore driver in the dom0 kernel put the process into >>> uninterruptible sleep? The 2.6.18 kernel simply returns -ENODEV in this case >>> I think. So perhaps pv_ops has different and inferior behaviour. >> >> the behavior was the same in 2.6.18. > > Ah, I just see 'if (!is_xenstored_ready()) return -ENODEV' in 2.6.18's > xenbus_dev.c. I assumed that would have an effect on this case. hm, maybe it does afterall, and I'm confuse this with a more general case; the D state would happens if xenstored doesn't want to reply or is dead. This behavior has been there as long as I can remember. I'm pretty sure though that a while ago (relatively old XenServer kernel) starting a xenstore-* without starting xenstored would make it stuck until xenstored start. -- Vincent