From: "Łukasz Oleś" <lukaszoles@gmail.com>
To: xen-devel@lists.xensource.com
Cc: vincent.hanquez@eu.citrix.com
Subject: oxenstored in stubdom ?
Date: Sun, 22 Aug 2010 00:39:10 +0200 [thread overview]
Message-ID: <201008220039.11900.lukaszoles@gmail.com> (raw)
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?
--
Łukasz Oleś
next reply other threads:[~2010-08-21 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 22:39 Łukasz Oleś [this message]
2010-08-22 7:34 ` oxenstored in stubdom ? Vincent Hanquez
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=201008220039.11900.lukaszoles@gmail.com \
--to=lukaszoles@gmail.com \
--cc=vincent.hanquez@eu.citrix.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).