WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xenctld - a control channel multiplexing daemon
From: Andrew Warfield <andrew.warfield@xxxxxxxxx>
Date: Wed, 26 Jan 2005 19:11:07 +0000
Cc: Michael Hohnbaum <hohnbaum@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxx>
Delivery-date: Wed, 26 Jan 2005 19:12:24 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=TRKJAcEb4rGiFkr9nciePMbzOXtxMlWfAhvhOO6skXfNSRAy9rANCxRae+GeNhjpkrSOiskL9S1IgxEwk2G5eh8oSRuNoczKkOls8wgIMfZ2nZbo5pyofhDIx8XEIQKQK8LpRZ77WC5RDneVDvTAfUJbuHqNIQzApT6IFyu3DIs=
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <1106767902.25573.7.camel@localhost>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <1106322956.17263.26.camel@localhost> <eacc82a4050121083937725a83@xxxxxxxxxxxxxx> <1106698862.19729.40.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <eacc82a405012606336357ab08@xxxxxxxxxxxxxx> <1106767902.25573.7.camel@localhost>
Reply-to: andrew.warfield@xxxxxxxxxxxx
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>