xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: "Łukasz Oleś" <lukaszoles@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: oxenstored in stubdom ?
Date: Sun, 22 Aug 2010 08:34:08 +0100	[thread overview]
Message-ID: <4C70D2F0.8080507@eu.citrix.com> (raw)
In-Reply-To: <201008220039.11900.lukaszoles@gmail.com>

On 21/08/10 23:39, Łukasz Oleś wrote:
> Hi,
>
> recently on irc channel (##xen) was some "discussion" about xen vs kvm...
>
> There was idea that it would be nice if domUs could survive dom0 restart, but
> this needs, for example, to have xenstored running in separate domain.
>
> In 2009 Alex Zeffertt posted some patches
> (http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00696.html) to
> add this functionallity, but they weren't applied.
>
> So.. having xenstore in separate domain can have other advantages
> (performance?).
> Is it (or will be) possible  run oxenstroed in stubdomain?

oxenstored is already restartable (or used to be and easy to fix if it 
was broken), so from a xenstore point of view, you could already restart 
dom0; Obviously this would block all the domains that try to do a 
xenstore query, but if the dom0 is restarted quickly enough this 
shouldn't be too noticeable since a normal working domain shouldn't use 
much xenstore after starting up.

Regarding performance nobody profiled oxenstored in this context as far 
as i know; I'm not sure that would be a win, and i would much rather 
squeeze performance in the code directly than move xenstored in a 
complicated setup.

-- 
Vincent

  reply	other threads:[~2010-08-22  7:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21 22:39 oxenstored in stubdom ? Łukasz Oleś
2010-08-22  7:34 ` Vincent Hanquez [this message]
2010-08-22  8:23   ` Keir Fraser
2010-08-22  9:14     ` Vincent Hanquez
2010-08-22  9:44       ` Keir Fraser
2010-08-22 19:18         ` Łukasz Oleś
2010-08-22 19:37           ` Keir Fraser

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=4C70D2F0.8080507@eu.citrix.com \
    --to=vincent.hanquez@eu.citrix.com \
    --cc=lukaszoles@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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).