From: Andrew Warfield <andrew.warfield@gmail.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Michael Hohnbaum <hohnbaum@us.ibm.com>,
xen-devel@lists.sourceforge.net,
Keir Fraser <keir.fraser@cl.cam.ac.uk>
Subject: Re: [PATCH] xenctld - a control channel multiplexing daemon
Date: Wed, 26 Jan 2005 19:11:07 +0000 [thread overview]
Message-ID: <eacc82a40501261111572c3b11@mail.gmail.com> (raw)
In-Reply-To: <1106767902.25573.7.camel@localhost>
> In reality, what's the different between a domain that's suspended to
> disk and a clone domain that just hasn't been started yet.
>
> Does the current persistent store architecture attempt to solve this
> problem? Does it attempt to solve both problems?
No. There has been no discussion of storing suspended domains. For
the moment, i think it's probably best to design the store to contain
runtime state for the currently executing set of VMs on the physical
host. So records in the store are persistent across daemon restarts,
and dom0 restarts.
I don't think any of use really imagine the store as being a very
complicated bit of code at all. The bit of design that needs a little
more thought is how things like device driver setup should look with
the new control tools. This isn't necessarily terrible -- but
changing e.g. device channel negotiation at driver setup is going to
be a lot less work this round (with three split drivers) than it is
going to be if we need yet another set of control tools for Xen 4. ;)
a.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-26 19:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 15:55 [PATCH] xenctld - a control channel multiplexing daemon Anthony Liguori
2005-01-21 16:39 ` Andrew Warfield
2005-01-21 17:19 ` Ronald G. Minnich
2005-01-21 19:59 ` Anthony Liguori
2005-01-21 20:44 ` Ronald G. Minnich
2005-01-21 21:14 ` Anthony Liguori
2005-01-21 20:54 ` Ronald G. Minnich
2005-01-21 21:28 ` Anthony Liguori
2005-01-21 21:37 ` Jared Rhine
2005-01-24 15:33 ` Ronald G. Minnich
2005-01-24 16:35 ` Anthony Liguori
2005-01-24 16:55 ` Jared Rhine
[not found] ` <Pine.LNX.4.58.0501240957520.12186@bluesteel.lanl.gov>
2005-01-24 17:52 ` Jared Rhine
2005-01-24 19:11 ` Anthony Liguori
2005-01-24 19:07 ` Anthony Liguori
2005-01-24 20:44 ` B.G. Bruce
2005-01-26 2:31 ` Jacob Gorm Hansen
2005-01-26 5:43 ` Anthony Liguori
2005-01-26 6:59 ` Jacob Gorm Hansen
2005-01-21 19:56 ` Anthony Liguori
2005-01-26 0:21 ` Michael Hohnbaum
2005-01-26 14:33 ` Andrew Warfield
2005-01-26 19:31 ` Anthony Liguori
2005-01-26 19:11 ` Andrew Warfield [this message]
2005-01-26 20:01 ` Anthony Liguori
2005-01-26 21:21 ` Daniel Stekloff
2005-01-26 22:28 ` Anthony Liguori
2005-01-26 21:57 ` Daniel Stekloff
2005-01-26 21:49 ` Michael Hohnbaum
2005-01-26 22:57 ` Anthony Liguori
2005-01-26 23:55 ` Michael Hohnbaum
2005-01-26 23:59 ` Daniel Stekloff
2005-01-27 7:05 ` Tobias Hunger
2005-01-27 14:19 ` Anthony Liguori
2005-01-27 18:05 ` Daniel Stekloff
2005-01-28 9:17 ` Steven Hand
2005-01-28 16:56 ` Daniel Stekloff
2005-01-27 0:13 ` Daniel Stekloff
2005-01-27 3:48 ` Daniel Stekloff
2005-01-26 23:36 ` Daniel Stekloff
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=eacc82a40501261111572c3b11@mail.gmail.com \
--to=andrew.warfield@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=andrew.warfield@cl.cam.ac.uk \
--cc=hohnbaum@us.ibm.com \
--cc=keir.fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.