From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: Re: Help please: bug#625 SCSI disk conflicts with blkfront---best approach for fix?
Date: Tue, 20 Jun 2006 09:59:27 -0500 [thread overview]
Message-ID: <pan.2006.06.20.14.59.24.611640@us.ibm.com> (raw)
In-Reply-To: 1150802478.7727.6.camel@localhost.localdomain
The best fix is to stop hijacking major numbers that we don't own.
This has been discussed on LKML and we've been told not to do this. The
longer we allow this the harder it will be for users when they eventually
have to switch over to xdX.
Regards,
Anthony Liguori
On Tue, 20 Jun 2006 12:21:17 +0100, Harry Butterworth wrote:
> I think bugzilla 625 is caused by compiling the scsi disk driver into
> the domU kernel. xen_blk can't then get the SCSI major number 8. This
> is a usability issue because people create broken domU kernels and then
> raise bugs. What's the best fix? Changing the Kconfig files to
> prohibit built in scsi disk when blkfront is enabled? Is there a better
> option?
>
> Thanks,
> Harry.
next prev parent reply other threads:[~2006-06-20 14:59 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 [this message]
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
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=pan.2006.06.20.14.59.24.611640@us.ibm.com \
--to=aliguori@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.