From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Proposal for init/kexec/hotplug format for Xen Date: Sun, 27 Feb 2005 10:16:43 -0600 Message-ID: <4221F26B.2030306@us.ibm.com> References: <1109451460.32219.11.camel@localhost.localdomain> <68d3daa4e95f4ba6740c6c0ffd3f67b8@cl.cam.ac.uk> <4221E676.5000008@us.ibm.com> <4221ED32.2010407@us.ibm.com> <260c30236e5ef2b632b85e5ebaebcb6b@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <260c30236e5ef2b632b85e5ebaebcb6b@cl.cam.ac.uk> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Keir Fraser Cc: Rusty Russell , Jeremy Katz , Xen Mailing List List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > I think we will provide a custom protocol for allowing guest kernels > to access the persistent store -- it needn't be very complicated, and > will allow things like basic device bootstrap to be done via the store > without any chicken-and-egg or deadlock problems. Also there may be > security implications in allowing arbitrary guests to make TCP > connections to domain0 (at the very least, there may be possible DoS > attacks) -- of course we allow this by default right now, but we don't > want to make it a requirement of using Xen. One of the things I'd like to see in the new management tools is a higher level interdomain communication library. A very useful abstraction would be a interdomain stream built on top of shared memory and event channels. Interdomain streams would be perfect for something like this. Regards, Anthony Liguori ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click