xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org, manish.jaggi@caviumnetworks.com,
	manish jaggi <manishjaggi.oss@gmail.com>
Subject: Re: domU hang in xenbus_scanf for /control/platform-feature-xs_reset_watches
Date: Thu, 21 Aug 2014 18:23:41 +0100	[thread overview]
Message-ID: <1408641821.5309.3.camel@citrix.com> (raw)
In-Reply-To: <20140821115408.GD10356@zion.uk.xensource.com>

On Thu, 2014-08-21 at 12:54 +0100, Wei Liu wrote:
> On Wed, Aug 20, 2014 at 06:54:26PM +0530, manish jaggi wrote:
> > In xenstore-ls I dont see this node (control node is not there as well)
> > What could be missing here.
> > 
> 
> It's libxl's resposibility to write that node. However libxl should fail
> if it fails to create that node. See libxl_create.c.
> 

But also the guest ought to be robust to that node not being present,
afterall that is the point of a feature-* node...

Ian.

> You can try to increase xl's verbosity to have an idea what went wrong.
> 
> Wei.
> 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2014-08-21 17:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 13:24 domU hang in xenbus_scanf for /control/platform-feature-xs_reset_watches manish jaggi
2014-08-21 11:54 ` Wei Liu
2014-08-21 17:23   ` Ian Campbell [this message]
2014-08-22 13:45     ` manish jaggi
2014-08-22 16:08       ` Ian Campbell
2014-08-25 11:42       ` Wei Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1408641821.5309.3.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=manish.jaggi@caviumnetworks.com \
    --cc=manishjaggi.oss@gmail.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).