From: Jerone Young <jyoung5@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Dan Smith <danms@us.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: Re: Help please: bug#625 SCSI disk conflicts with blkfront---best approach for fix?
Date: Tue, 20 Jun 2006 10:18:07 -0500 [thread overview]
Message-ID: <1150816688.2457.4.camel@localhost.localdomain> (raw)
In-Reply-To: <d9829a479a5f7000700d18e84886c96a@cl.cam.ac.uk>
On Tue, 2006-06-20 at 16:13 +0100, Keir Fraser wrote:
> On 20 Jun 2006, at 16:05, Dan Smith wrote:
>
> > AL> The longer we allow this the harder it will be for users when they
> > AL> eventually have to switch over to xdX.
> >
> > I very much agree. What is the plan for switching over to xd devices
> > only?
>
> There isn't one. We could add a compile option to make blkfront only
> understand xvdX. Then vendors can compile with that if they want.
Currently Redhat (Fedora 5) Xen can understand xvdX . But Suse (OpenSuse
10.1) Xen cannot. Haven't looked into it but this is just the case at
the moment.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-06-20 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 11:21 Help please: bug#625 SCSI disk conflicts with blkfront---best approach for fix? Harry Butterworth
2006-06-20 14:59 ` Anthony Liguori
2006-06-20 15:05 ` Dan Smith
2006-06-20 15:09 ` Jerone Young
2006-06-20 15:13 ` Keir Fraser
2006-06-20 15:18 ` Jerone Young [this message]
2006-06-20 15:11 ` Keir Fraser
2006-06-20 15:24 ` Dan Smith
2006-06-20 15:36 ` Keir Fraser
2006-06-20 20:54 ` Randy Thelen
2006-06-20 15:49 ` Anthony Liguori
2006-06-23 11:28 ` Help please: bug#625 SCSI disk conflicts with?blkfront---best " Horms
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=1150816688.2457.4.camel@localhost.localdomain \
--to=jyoung5@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=danms@us.ibm.com \
--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.