From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Re: oxenstored in stubdom ? Date: Sun, 22 Aug 2010 20:37:00 +0100 Message-ID: References: <201008222118.51193.lukaszoles@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-2" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <201008222118.51193.lukaszoles@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-2?B?o3VrYXN6?= =?ISO-8859-2?B?IE9sZbY=?= Cc: "xen-devel@lists.xensource.com" , Vincent Hanquez List-Id: xen-devel@lists.xenproject.org On 22/08/2010 20:18, "=A3ukasz Ole=B6" wrote: >> I don't think xenstored-in-stubdomain is the big barrier to dom0 >> restartability, that's for sure. Personally, I don't think full dom0 >> restartability, for things like seamless dom0 kernel upgrade, will ever = be >> achieved. But I think particular vulnerable or critical services within >> dom0 can be made restartable. >=20 > Thanks for clarifying. >=20 > Which are these "critical services"? Is there any list of them? Primarily the main toolstack (xend, xenvm, xapi, or whatever), xenstored, xenconsoled. Xenstored is already pretty much restartable, as Vincent says. K.