From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Logan Subject: Re: Where can I find some tutorial or manual on how to use xenstore? Date: Thu, 29 Jun 2006 15:42:17 +0100 Message-ID: <44A3E6C9.4060403@symantec.com> References: <44A26331.6060200@symantec.com> <20060628130526.GC26663@leeni.uk.xensource.com> <44A28647.3010108@symantec.com> <20060628145724.GA27633@leeni.uk.xensource.com> <44A29E53.4000803@symantec.com> <20060628153219.GC27633@leeni.uk.xensource.com> <44A3DB56.2000509@symantec.com> <20060629141959.GB20815@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20060629141959.GB20815@leeni.uk.xensource.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: Ewan Mellor Cc: xen-devel@lists.xensource.com, jacobg@diku.dk, ushuanglily@gmail.com List-Id: xen-devel@lists.xenproject.org >> Can I just confirm what your proposal is: >> >> Add a generic device config to the xm config file that would contain the >> driver id, virtual device, physical device ..... >> Add a generic device handler to xend that would pass the unparsed >> generic config through to xenstore. >> Add a hotplug script that would parse the unparsed config in xenstore >> and start the driver. >> When saving a domain, xend would save the generic device config. >> xend would call restore for the generic devices. >> >> If that's correct, I'll find some time to investigate how this could done. >> > > Yes, that's it. It sounds like something that would be very useful. > > Cheers, > > Ewan. > I can't promise that I'll get onto this straightaway, but if we're going to go ahead with a new driver, we'll have to have some way of dealing with save/restore and migration. This looks like a way to solve the problem. Cheers, Nick