From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Olaf Hering <olaf@aepfle.de>,
xen-devel@lists.xen.org, Ian Jackson <ian.jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Cc: Vasilis Liaskovitis <vliaskovitis@suse.com>
Subject: Re: [PATCH v1] tools/hotplug: convert proc-xen.mount to proc-xen.service
Date: Thu, 26 Oct 2017 16:45:38 +0100 [thread overview]
Message-ID: <cde0e85d-2d1b-d0f8-fee4-b7f2efeb4090@citrix.com> (raw)
In-Reply-To: <20171026152536.17072-1-olaf@aepfle.de>
On 26/10/17 16:25, Olaf Hering wrote:
> An upcoming change in systemd will mount xenfs right away, along with
> all other system mounts. This improves the detection of the
> virtualization environment, which is currently racy. Some parts of
> systemd rely on the presence of /proc/xen/capabilities, which will only
> exist if xenfs is mounted. Since xenfs is mounted by the proc-xen.mount
> unit, it will be processed very late. Other units may be processed
> earlier, and if they make use of ConditionVirtualization*= failures may
> occour.
>
> Unfortunately mounting xenfs by systemd as an API filesystem will lead
> to errors when proc-xen.mount is processed. Since that mount point
> already exists the unit is considered as failed, and other units that
> depend on proc-xen.mount will not start. To avoid this the existing
> proc-xen.mount will be converted into proc-xen.service, which just
> mounts xenfs manually. All dependencies are updated by this change.
>
> The existing conditionals in proc-xen.mount will prevent failures with
> existing systemd based installations:
> ConditionPathExists=!/proc/xen/capabilities will prevent execution with
> a new systemd that mounts xenfs. And this conditional, in combination
> with ConditionPathExists=/proc/xen, will trigger execution with an old
> systemd.
>
> An absolute path to the mount binary has to be used. /bin/mount is
> expected to be universally available, nowaways it is a symlink to
> /usr/bin/mount.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
Can't all information be obtained from /sys/hypervisor? If not, how
hard would it be to make happen?
What happens to all the software which currently has a dependency on
proc-xen.mount ?
Independently, how does this interact with having a xenfs entries in
/etc/fstab, which might plausibly still exist for compatibility with
other init systems?
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-26 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 15:25 [PATCH v1] tools/hotplug: convert proc-xen.mount to proc-xen.service Olaf Hering
2017-10-26 15:45 ` Andrew Cooper [this message]
2017-10-26 15:59 ` Olaf Hering
2017-10-26 16:14 ` Andrew Cooper
2017-10-26 17:05 ` Olaf Hering
2017-11-08 16:24 ` Olaf Hering
2017-11-08 17:28 ` Wei Liu
2017-11-08 17:38 ` Olaf Hering
2017-11-09 10:48 ` Ian Jackson
2017-10-30 10:08 ` Wei Liu
2017-10-27 13:58 ` 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=cde0e85d-2d1b-d0f8-fee4-b7f2efeb4090@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=vliaskovitis@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).