From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerone Young 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 Message-ID: <1150816688.2457.4.camel@localhost.localdomain> References: <1150802478.7727.6.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: 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: Keir Fraser Cc: Dan Smith , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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