From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: iscsi and HVM Date: Fri, 19 Aug 2011 00:25:15 -0400 Message-ID: <20110819042515.GB7625@dumpdata.com> References: <20110819003639.GA7625@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: James Harper Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Aug 19, 2011 at 12:01:41PM +1000, James Harper wrote: > > > > On Thu, Aug 18, 2011 at 02:12:59PM +1000, James Harper wrote: > > > If I use a block-iscsi script to handle the connection of an iscsi > > > > What script is that? > > This one > http://lists.xensource.com/archives/html/xen-devel/2007-11/msg00782.html > or at least very similar (can't find the original URL I copied it from). > I think I had to change the -a's to -b's so it detected if the block > device was already attached. > > I have solved (worked around) the problem by modifying the script to > convert the 'iscsi' to 'phy' in xenstore once the block-iscsi script was > done with it. Ah, never did that. Looks like you would need to write the support in 'xl' to actually look for those types of non-common backends and execute them. > > I think it would be better if there was a separate 'format' for qemu > used was different to the 'type' that the block-* scripts need to use, > even if the block-* scripts had to update it. So 'iscsi' would have a > 'format' of raw or phy or whatever it needs, as would 'drbd'. > > James > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel