Re: [Xen-devel] [PATCH] xenctld - a control channel multiplexing daemon

[Daniel Stekloff <dsteklof@xxxxxxxxxx>]

On Wed, 2005-01-26 at 12:01, Anthony Liguori wrote:
> On Wed, 2005-01-26 at 13:11, Andrew Warfield wrote:
> > > 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.
> 
> Excellent!  Then I have no worries at all about it.
> 
> You mentioned the current design looks a lot like a file system, any
> thoughts on actually using the file system?  Either within the normal
> file system (within something like /var/xen/<domid>) or as a pid-like
> /proc entry (like /proc/xen/<domid>).


Do you really want the store in Kernel Space? Wouldn't it be better if
it were stored in User Space? Could you restart Dom0 if it's in Dom0?
Wouldn't it be better to store out on disk that can be recovered? You
could use the store for more than the above, domain configuration could
be stored and accessed there. 

Thanks,
Dan



-------------------------------------------------------
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel