Ah sorry, forgot the reply all!

My personal Gentoo based system is systemd only, testing on Debian lead me
to sysv.

There is also a typo in the description for the service, my bad.


Yours,

Sjoer van der Ploeg

On Fri, Apr 1, 2016 at 7:01 PM, Wei Liu <wei.liu2@citrix.com> wrote:

> Add back xen-devel
>
> Please use the "reply-all" button in gmail in the future.
>
> On Fri, Apr 01, 2016 at 06:48:47PM +0200, Sjoer van der Ploeg wrote:
> > > The sysv init script for xendomains depends on xenstored and
> > > xenconsoled, and the systemd service file contains the same
> > > dependencies.
> > >
> > > It would be useful to track down which service is not started and
> > > explicitly provide the dependency.
> >
> > Manually enabling xencommons through update-rc.d also works, to put it
> like
> > this the xendomains fails to start because was xencommons was not
> > enabled/started. The error xendomains gave back only complained about
> > xenstored and xenconsoled.
> >
> > What actually happened is that the required modules were never loaded on
> > dom0 (causing numerous other unrelated problems), adding the systemd
> > service fixed that instead of having to manually enable xencommons with
> > update-rd.d (which is not the systemd workflow anyway). Scratching your
> > head as to why xendomains complains about two services that have in fact
> > been enabled and loaded when a sysv init.d script is the actual cause,
> was
> > not my first thought.
> >
> > On that note xendomains should state xencommons dependency, which it
> > currently does not.
> >
>
> Ah, so it is the kernel modules that are not loaded. I can see why that
> would be a problem. My experience with systemd is a bit rusty at the
> moment. I will find some time to have a look at this next week.
>
> Wei.
>
> >
> > Yours,
> >
> > Sjoer van der Ploeg
> >
>