From: Vasilis Liaskovitis <vliaskovitis@suse.com>
To: xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>, Franck Bui <fbui@suse.com>
Subject: Re: [RFC] removing proc-xen.mount due to systemd change
Date: Mon, 02 Oct 2017 12:26:24 +0200 [thread overview]
Message-ID: <1506939984.3176.3.camel@suse.com> (raw)
In-Reply-To: <59D2051A02000072001E7B87@smtp.nue.novell.com>
Apologies for formatting. Here is my question in plain text:
There are systemd services that check for dom0 detection before xenfs
gets mounted by proc-xen.mount. See this systemd bug report for an
example:
https://github.com/systemd/systemd/issues/6442
Upstream systemd has accepted the patch for this: https://github.com/sy
stemd/systemd/pull/6662,
which mounts xenfs at systemd init time i.e. making /proc/xen an API
file.
However the issue now is that proc-xen.mount will refuse to mount
/proc/xen as it an API file system, and the service will fail. This
breaks xen, as other services depending on proc-xen.mount also
fail.
What is the preferred way to deal with this in xen?
- We can remove proc-xen.mount completely, for systems using systemd.
- any other options?
thank you,
- Vasilis
On Mon, 2017-10-02 at 11:21 +0200, Vasilis Liaskovitis wrote:
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-02 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 9:21 [RFC] removing proc-xen.mount due to systemd change Vasilis Liaskovitis
2017-10-02 10:26 ` Vasilis Liaskovitis [this message]
2017-10-02 10:35 ` Wei Liu
2017-10-02 13:55 ` Franck Bui
2017-10-02 14:12 ` Franck Bui
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=1506939984.3176.3.camel@suse.com \
--to=vliaskovitis@suse.com \
--cc=fbui@suse.com \
--cc=jgross@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.