Re: [Xen-devel] why xenstore-* hangs if xenstored is not started

[Yu Zhiguo <yuzg@xxxxxxxxxxxxxx>]

Hi,

Vincent Hanquez wrote:

> That's the common behavior of task stuck in a kernel operation (ps aux
> will show the task at D, and /proc/<pid>/wchan will tell you exactly
> where it's blocked in the kernel).
> 
> the write is going to wait for a xenstored reply in kernel mode since by
> default the xenstore-* tools use the kernel xenstore page to communicate
> with xenstored.
> 
> The unix socket operations doesn't have this "problems" (xenstore-* -s)
> 

Thanks~~
I confirmed the task is at D+ and there are no this "problem" if use option -s.
But I think S+ is better than D+...


Yu


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel