From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: systemd-devel@lists.freedesktop.org,
Vasilis Liaskovitis <vliaskovitis@suse.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662)
Date: Fri, 1 Dec 2017 13:38:48 +0100 [thread overview]
Message-ID: <20171201133848.140d2063.olaf@aepfle.de> (raw)
In-Reply-To: <20171201122924.pz7tcv3wb3fyssdr@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 864 bytes --]
Am Fri, 1 Dec 2017 12:29:24 +0000
schrieb Wei Liu <wei.liu2@citrix.com>:
> But Olaf needs to know if some of the services like xenconsoled or
> xenstored should be started, and if some of the special file systems
> should be mounted, right? Those aren't tied to hardware in anyway. In my
> view that's the responsibility of the toolstack control domain.
No, I did not intent to make use of ConditionVirtualization= in the
xen*.service files in tools/hotplug/Linux/. That variable can not be used
for this purpose, and the patch would not change that.
In case you refer to the "proc-xen.mount" change from a few days/weeks ago,
this was all about avoiding the error when xenfs becomes an "API filesystem".
With this suggested change the existing "proc-xen.mount units would not fail
anymore because /proc/xen is added to the ignore list.
Olaf
[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2017-12-01 12:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 15:38 [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662) Olaf Hering
2017-11-29 15:46 ` Jan Beulich
2017-11-29 15:54 ` Olaf Hering
2017-11-29 16:01 ` Jan Beulich
[not found] ` <5A1EE7F40200007800193394@prv-mh.provo.novell.com>
2017-11-29 16:07 ` Olaf Hering
2017-11-29 16:24 ` Jan Beulich
[not found] ` <5A1EED6702000078001933EF@prv-mh.provo.novell.com>
2017-11-30 8:23 ` Olaf Hering
[not found] ` <20171130082355.GC3073@aepfle.de>
2017-11-30 8:35 ` Jan Beulich
[not found] ` <5A1FD0F10200007800193657@prv-mh.provo.novell.com>
2017-12-01 10:21 ` Wei Liu
2017-12-01 11:04 ` Olaf Hering
2017-12-01 17:06 ` [systemd-devel] " Lennart Poettering
2017-12-01 11:39 ` Jan Beulich
[not found] ` <5A214D820200007800193BFB@prv-mh.provo.novell.com>
2017-12-01 11:48 ` Wei Liu
2017-12-01 12:11 ` Jan Beulich
[not found] ` <5A2155110200007800193C60@prv-mh.provo.novell.com>
2017-12-01 12:15 ` Wei Liu
2017-12-01 12:23 ` Jan Beulich
[not found] ` <5A2157C40200007800193C90@prv-mh.provo.novell.com>
2017-12-01 12:29 ` Wei Liu
2017-12-01 12:38 ` Olaf Hering [this message]
2017-12-01 13:00 ` Wei Liu
2017-12-01 15:49 ` Olaf Hering
[not found] ` <20171201154901.GA13177@aepfle.de>
2017-12-01 15:59 ` Wei Liu
2017-12-01 16:52 ` Jan Beulich
2017-11-29 17:48 ` [systemd-devel] " Lennart Poettering
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=20171201133848.140d2063.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=systemd-devel@lists.freedesktop.org \
--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 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.