All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: Re: iscsi and HVM
Date: Fri, 19 Aug 2011 00:25:15 -0400	[thread overview]
Message-ID: <20110819042515.GB7625@dumpdata.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01DE3DD0@trantor>

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

  reply	other threads:[~2011-08-19  4:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18  4:12 iscsi and HVM James Harper
2011-08-19  0:36 ` Konrad Rzeszutek Wilk
2011-08-19  2:01   ` James Harper
2011-08-19  4:25     ` Konrad Rzeszutek Wilk [this message]
2011-08-19  4:35       ` James Harper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110819042515.GB7625@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.