Re: [Xen-devel] Issues with latest staging tree starting PV guest.

[Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>]

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

> On 05/03/14 02:49, Mukesh Rathor wrote:
> > On Mon, 3 Mar 2014 18:52:39 -0800
> > Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> 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@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel