From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Disk naming (Was Re: [PATCH] Guest boot loadersupport [1/2]) Date: Fri, 15 Apr 2005 16:05:03 -0500 Message-ID: <42602C7F.2010703@us.ibm.com> References: <200504152116.16334.mark.williamson@cl.cam.ac.uk> <200504152129.14487.mark.williamson@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200504152129.14487.mark.williamson@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Mark Williamson Cc: "xen-devel@lists.xensource.com" , Adam Heath List-Id: xen-devel@lists.xenproject.org Mark Williamson wrote: >But Xend configures the blkback driver using the control interface messages, >so the sizing of the ctrlif messages is still a problem (that was what >Anthony was saying, I think). > > I'm was trying at least :-) >That said, there would, of course, be ways this could be fixed. One nice side >effect of supporting passing filenames to the blkback would be the ability to >configure file based block devices when the backend is not dom0. > > This brings up a really interesting point. Is there a good story yet for how more complex devices can be created on driver domains? For instance, how would you create an iSCSI device that existed on a driver domain (or is this something that wouldn't be all that useful)? Can we assume an rexec capability between dom0 and a driver domain? Regards, Anthony Liguori >Cheers, >Mark > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel > > >