xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Sjoer van der Ploeg <sfjuocekr@gmail.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] Fixed --enable-systemd on latest Debian stretch. Added xencommons as a systemd.service.
Date: Fri, 1 Apr 2016 18:01:23 +0100	[thread overview]
Message-ID: <20160401170123.GA1032@citrix.com> (raw)
In-Reply-To: <CAGj-wbFYyMgfxpf8sWJnUukFe3fWp9BAKYChPmW3+NY7Tj=ggQ@mail.gmail.com>

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
> 

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

  parent reply	other threads:[~2016-04-01 17:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31 20:35 [PATCH] Fixed --enable-systemd on latest Debian stretch. Added xencommons as a systemd.service Sjoer van der Ploeg
2016-04-01 15:17 ` Wei Liu
     [not found]   ` <CAGj-wbFHgSe=NJ5L3U6Cno5U6k3XWfy16F3PNhwx6X5Q7GqT4Q@mail.gmail.com>
2016-04-01 15:57     ` Wei Liu
     [not found]       ` <CAGj-wbFYyMgfxpf8sWJnUukFe3fWp9BAKYChPmW3+NY7Tj=ggQ@mail.gmail.com>
2016-04-01 17:01         ` Wei Liu [this message]
2016-04-01 17:14           ` Sjoer van der Ploeg
2016-04-01 19:43           ` Olaf Hering
2016-04-02  0:45             ` Sjoer van der Ploeg
2016-04-02 10:59               ` Wei Liu
2016-04-02 11:12                 ` Wei Liu
2016-04-02 11:24                 ` Sjoer van der Ploeg
2016-04-04 10:30                   ` Wei Liu
     [not found]                     ` <CAGj-wbENk7vqdd-00kD2NASpEZcDb+uruAR_whgjySCJognJfA@mail.gmail.com>
2016-04-04 11:33                       ` 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=20160401170123.GA1032@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=sfjuocekr@gmail.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).