xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Issues with latest staging tree starting PV guest.
Date: Wed, 5 Mar 2014 15:59:55 -0800	[thread overview]
Message-ID: <20140305155955.48db4e48@mantra.us.oracle.com> (raw)
In-Reply-To: <5316EA47.7010205@citrix.com>

On Wed, 5 Mar 2014 10:11:35 +0100
Roger Pau Monné <roger.pau@citrix.com> wrote:

> On 05/03/14 02:49, Mukesh Rathor wrote:
> > On Mon, 3 Mar 2014 18:52:39 -0800
> > Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
> > 
....
> > then it calls:
> > ...
> > ds->callback(egc, ds, rc); --> device_backend_callback -->
> > device_hotplug which does:
> > ...
> >     rc = libxl__get_domid(gc, &domid);  ---> libxl__xs_read_checked
> >      --> libxl__xs_read (, , path="domid")...
> >       This returns result == 0 and errno == ENOENT.
> > 
> > logging:
> > libxl: debug: libxl_dm.c:1473:kill_device_model: Device Model
> > signaled libxl: error:
> > libxl_device.c:780:libxl__initiate_device_remove: unable to get my
> > domid
> > 
> > However, xenstore-ls, I see domid being there:
> >   bash> xenstore-ls |grep domid
> >      domid = "11"
> 
> What's missing is the domid from Dom0, not the domid of the guest. You
> are missing an entry like:
> 
> /local/domain/0/domid = "0"

Right...

> > 
> > Zooming in libxl__xs_read, I got as far as :
> > 
> > libxl__xs_read -> xs_read((gc=0x636880, t=0x0, path=0x7ffff7bc13ba
> > "domid") --> .. --> xs_talkv() where:
> > 
> >         ret = read_reply(h, &msg.type, len);
> >         if (!ret)
> >                 goto fail;
> > 
> >         mutex_unlock(&h->request_mutex);
> > 
> >         sigaction(SIGPIPE, &oldact, NULL);
> >         if (msg.type == XS_ERROR) {
> >                 saved_errno = get_error(ret); <=========
> > 
> > Ian(s), any thoughts/ideas?
> 
> You need to update your init scripts, since commit
> 02ebea7768fe723deaa56c2cfcb860874544b47d Dom0 domid is written to
> xenstore by xencommons init script, and libxl will fail to work
> properly if the domid of Dom0 is not found.

Ah, I already had seen your post googling for error and already made
sure I had latest init script. The problem was xencommons was not running
automatically. Once I added the sevice via systemctl, it works now. Thanks 
for the tip.

Mukesh

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2014-03-05 23:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  2:52 Issues with latest staging tree starting PV guest Mukesh Rathor
2014-03-04  9:47 ` Jan Beulich
2014-03-05  1:49 ` Mukesh Rathor
2014-03-05  9:11   ` Roger Pau Monné
2014-03-05 23:59     ` Mukesh Rathor [this message]

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=20140305155955.48db4e48@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=roger.pau@citrix.com \
    /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).