From: Chris Lalancette <clalance@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] Re: [PATCH]: Expand Xen blkfront for > 16 xvd
Date: Tue, 19 Aug 2008 08:52:52 +0200 [thread overview]
Message-ID: <48AA6DC4.9060709@redhat.com> (raw)
In-Reply-To: <48A9AE88.3060507@goop.org>
Jeremy Fitzhardinge wrote:
> Chris Lalancette wrote:
>> Jeremy,
>> Until recently, the maximum number of xvd block devices you could attach to
>> a Xen domU was 16. This limitation turned out to be problematic for some users,
>> so it was expanded to handle a much larger number of disks. However, this
>> requires a couple of changes in the way that blkfront scans for disks. This
>> functionality is already present in the Xen linux-2.6.18-xen.hg tree; the
>> attached patch adds this functionality to the mainline xen-blkfront
>> implementation.
>
> I haven't tested this yet. You have tested it OK with some pvops
> kernel? If so, send it to Jens Axboe with my ack.
Yes, I tested it with a 2.6.25-something Fedora 9 pv-ops kernel (i386). I'll
send it along to Jens.
>
>> I successfully tested it on a 2.6.25 tree. I build tested it
>> on 2.6.27-rc3, but couldn't get that tree to boot due to some other bug.
>
> What other bug?
This is http://bugzilla.redhat.com/show_bug.cgi?id=459067, that I think you've
already looked at. Basically any F-10 or upstream git kernel is crashing on an
i386 RHEL-5 HV. We were a little confused by your comment in that bug, however;
we were under the impression that the fix you mentioned was specifically a
32-on-64 fix, not for 32-on-32. If we were wrong, please point it out.
Thanks,
Chris Lalancette
prev parent reply other threads:[~2008-08-19 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 9:54 Chris Lalancette
2008-08-18 17:16 ` Jeremy Fitzhardinge
2008-08-19 6:52 ` Chris Lalancette [this message]
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=48AA6DC4.9060709@redhat.com \
--to=clalance@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome