From: Juergen Gross <jgross@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xenstore domain
Date: Tue, 8 Dec 2015 17:02:33 +0100 [thread overview]
Message-ID: <5666FF19.5020200@suse.com> (raw)
In-Reply-To: <5666F16D.7040804@citrix.com>
On 08/12/15 16:04, Andrew Cooper wrote:
> On 08/12/15 14:44, Juergen Gross wrote:
>> I'm just playing a little bit with xenstore in an own domain.
>>
>> I've come across some questions I'd like to have some answers to before
>> presenting official patches to make this an easy configurable option:
>>
>> a) As this would need a boot time configuration item I'd like to add
>> e.g. /etc/xen/server.conf where such global configuration options
>> could be set via directives. Is this generally okay? If yes, which
>> format? Easiest way would be entries like
>> VAR=value
>> which can be either sourced in from shell scripts or can easily be
>> parsed in all programming languages. What are the preferences here?
>
> Any configuration like this going to be toolstack-specific. I would
> recommend against using a name as generic as that.
>
> /etc/xl.conf already exists, which IMO would be the natural place for
> this to live, but it isn't parseable by shell, because of vif notation.
OTOH that file wouldn't be just for xl. It would be consumed by e.g.
xencommons. Other configuration options I'd plan to add would be
driver domains dedicated to specific interface cards.
> One option might be to alter xl.conf to be compatible with shell
> parsing. It wouldn't be complicated (even in upgrade situations), and
> would offer rather more flexibility.
Shell parsing could be even handled via a rather simple filter, I guess.
>> b) Today init-xenstore-domain will require flask to be enabled. An
>> alternative would be to add a new domain creation flag to allow the
>> domains with that flag set calling xc_domain_getinfo(). Thoughts?
>
> Which flag?
A new domcr_flag.
>> c) In order to be as flexible as possible I think the xenstore domain
>> should be allowed to auto-balloon according to it's needs. Is anyone
>> already working on ballooning support for mini-os?
>
> This is the C xenstore? Have you investigated whether Mirage-based
> stubdomains can balloon?
Aren't they based on mini-os, too?
Juergen
next prev parent reply other threads:[~2015-12-08 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 14:44 xenstore domain Juergen Gross
2015-12-08 15:04 ` Andrew Cooper
2015-12-08 16:02 ` Juergen Gross [this message]
2015-12-08 16:34 ` Andrew Cooper
2015-12-09 0:53 ` Jon Ludlam
2015-12-09 7:34 ` Juergen Gross
2015-12-10 20:24 ` Andrew Cooper
2015-12-11 5:01 ` Juergen Gross
2015-12-10 21:13 ` Doug Goldstein
2015-12-11 4:57 ` Juergen Gross
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=5666FF19.5020200@suse.com \
--to=jgross@suse.com \
--cc=andrew.cooper3@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.