All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: xenstore domain
Date: Tue, 8 Dec 2015 15:44:14 +0100	[thread overview]
Message-ID: <5666ECBE.6090102@suse.com> (raw)

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?

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?

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?


Juergen

             reply	other threads:[~2015-12-08 14:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08 14:44 Juergen Gross [this message]
2015-12-08 15:04 ` xenstore domain Andrew Cooper
2015-12-08 16:02   ` Juergen Gross
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=5666ECBE.6090102@suse.com \
    --to=jgross@suse.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.