Bug 216293 - blktap does not build on ia64
blktap does not build on ia64
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen (Show other bugs)
ia64 Linux
high Severity high
: ---
: ---
Assigned To: Keiichiro Tokunaga
: 212315 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2006-11-18 15:52 EST by Aron Griffis
Modified: 2013-07-03 09:26 EDT (History)
9 users (show)

See Also:
Fixed In Version: RHBA-2007-0959
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 14:15:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Updated blktap patch, as posted for internal review (17.57 KB, patch)
2006-12-04 21:01 EST, Jarod Wilson
no flags Details | Diff
Further updated patch, actually builds *and* works! (at least mostly) (7.32 KB, patch)
2007-06-21 00:42 EDT, Jarod Wilson
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:0959 normal SHIPPED_LIVE Updated kernel packages for Red Hat Enterprise Linux 5 Update 1 2007-11-07 19:47:37 EST

  None (edit)
Description Aron Griffis 2006-11-18 15:52:28 EST
+++ This bug was initially created as a clone of Bug #208895 +++

Description of problem:
The kernel/drivers/xen/blktap/blktap.ko module does not build on ia64:

drivers/xen/blktap/blktapmain.c: In function 'fast_flush_area':
drivers/xen/blktap/blktapmain.c:902: error: implicit declaration of function

Version-Release number of selected component (if applicable):

blktap has been disabled on ia64 for now:
$ grep TAP configs/*xen*
configs/config-xen-ia64:# CONFIG_XEN_BLKDEV_TAP is not set

-- Additional comment from chrisw@redhat.com on 2006-10-02 11:29 EST --
Created an attachment (id=137553)
blktap compile fix for ia64

-- Additional comment from chrisw@redhat.com on 2006-10-02 11:36 EST --
Here is a patch that gets things building.  It's a bit of a hack since
it copies create_lookup_pte_addr into ia64 specific source files.  With
this patch the thing builds, and boots.  However each of the blkback, netback
and blktap fail with the same error.  Basically none of the backend drivers are
working on ia64, they each fail in balloon_alloc_empty_page_range() due to
failed __get_free_pages() attempt with large order.

-- Additional comment from sct@redhat.com on 2006-10-02 12:15 EST --
Yes; the backend allocating issue is already being tracked as bug 202971.

-- Additional comment from chrisw@redhat.com on 2006-10-02 12:20 EST --
OK, in that case we could apply the blktap fix to get things working to a point
that they can be debugged.

-- Additional comment from prarit@redhat.com on 2006-10-04 12:00 EST --
Assigning to agriffis.

-- Additional comment from sakaia@jp.fujitsu.com on 2006-10-16 07:15 EST --
GNTMAP_application_map does not support Xen/IA64.
the blktap uses this function, so it does not run.
even if it fixes compilation.

-- Additional comment from yongkang.you@intel.com on 2006-10-16 22:10 EST --
This bug is still in kernel-xen-2.6.18-1.2784.fc6

-- Additional comment from dzickus@redhat.com on 2006-10-16 22:34 EST --
in kernel-2.6.18-1.2728.el5

-- Additional comment from sct@redhat.com on 2006-10-17 04:41 EST --
Reopening, because the el5 kernel is not a fix for a devel bug!

-- Additional comment from agriffis@redhat.com on 2006-10-25 14:22 EST --
Unfortunately the compile fix for blktap on ia64 isn't nearly enough.  Sure it
allows the module to build, and that's great so that it doesn't need to be
disabled.  However the requisite support isn't in the ia64 hypervisor yet.  See

Hopefully this will be fixed upstream in time for RHEL5 release.  Unfortunately
it didn't make FC6

-- Additional comment from agriffis@redhat.com on 2006-11-08 15:22 EST --
Isaku Yamahata (Fujitsu) finished this work.  It is now in xen-unstable:


Unfortunately blktap has diverged somewhat between xen-unstable.hg and RHEL5,
with unique fixes in each that haven't yet been merged to the other.  They'll
undoubtedly converge in due course, but at the moment this means a little
porting work for the above patches to apply to RHEL5.  I'll update this bug with
those soon, hopefully.

-- Additional comment from agriffis@redhat.com on 2006-11-18 12:58 EST --
Created an attachment (id=141558)
blktap/ia64 patches ported to rhel5

-- Additional comment from agriffis@redhat.com on 2006-11-18 14:36 EST --
Note that the blktap patches also require this change in

Comment 1 Aron Griffis 2006-11-18 15:54:03 EST
*** Bug 212315 has been marked as a duplicate of this bug. ***
Comment 2 Aron Griffis 2006-11-18 15:57:00 EST
Note that attachment 141558 [details] should obsolete attachment 137553 [details] but I didn't have
permissions to do that.
Comment 3 RHEL Product and Program Management 2006-11-18 16:20:24 EST
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 4 Larry Troan 2006-11-20 14:03:10 EST
Per discussion with Prarit and Aron,
> Bug 212315/216293: blktap does not build on ia64
> This is completely fixed upstream and is important for the tech
> preview.  I just need to post the patches ported to RHEL5.  I will do
> that ASAP.
Should be an RC blocker.

Aron please ACK for devel; QE please ACK/NAK as appropriate.
Comment 5 Larry Troan 2006-11-20 14:07:06 EST
Note that the patch in comment #2 is more complicated that others in this group.
Affects drivers/xen/blktap/blktapmain.c and drivers/xen/blktap/xenbus.c.
Comment 6 Aron Griffis 2006-12-04 18:09:51 EST
devel ACK

I put this on rhkernel-list today so we should get some comments back about the
common code mods.
Comment 9 Jarod Wilson 2006-12-04 21:01:25 EST
Created attachment 142795 [details]
Updated blktap patch, as posted for internal review

This patch obsoletes attachment 141558 [details].
Comment 16 Brian Stein 2007-06-14 13:44:58 EDT
If blktap is building/working on IA64, this should be closed.
Comment 17 Jarod Wilson 2007-06-14 15:04:22 EDT
Well... First ia64 xen kernels have to actually be able to *boot*... :)

(bug 241674 and bug 243312)
Comment 18 Jarod Wilson 2007-06-20 14:26:56 EDT
...still not building. With the config option flipped back on in the latest
kernel (-29.el5):

drivers/xen/blktap/blktapmain.c: In function 'fast_flush_area':
drivers/xen/blktap/blktapmain.c:859: error: implicit declaration of function
make[3]: *** [drivers/xen/blktap/blktapmain.o] Error 1
make[2]: *** [drivers/xen/blktap] Error 2
make[1]: *** [drivers/xen] Error 2
make: *** [drivers] Error 2
Comment 19 Jarod Wilson 2007-06-20 17:23:06 EDT
I've got the blktap module compiling now, but not behaving entirely. Though it
could be something else actually causing my problems, so stay tuned. More info
to come later tonight. Current patch was posted to rhkernel-list earlier
tonight, and there's a slightly different version that made its way into the
upstream xen-unstable hg tree:


Comment 20 Jarod Wilson 2007-06-21 00:42:47 EDT
Created attachment 157513 [details]
Further updated patch, actually builds *and* works! (at least mostly)

This is the version of the patch with which I'm actually able to use blktap to
access a disk image, install a guest with, etc. Only issue at the moment, so
far as I can tell, is top reporting some insane memory usage from tapdisk. Its
reporting figures several orders of magnitude greater than the amount of memory
in the system (its claiming to use 2000% of memory), but swap isn't being
abnormally used, no oom-kills, etc., so it may just be an accounting error of
some sort, since I can't see any other ill effects.
Comment 21 Jarod Wilson 2007-06-21 01:12:02 EDT
Guest install finished just fine, no more tapdisk process reporting gross memory usage once its shut 
down. More testing in the morning.
Comment 22 Jarod Wilson 2007-06-21 17:38:49 EDT
Patch submitted for internal review.
Comment 23 Jarod Wilson 2007-06-28 17:56:07 EDT
Updated patch including a one-line-of-code addition from fujitsu to eliminate
the tapdisk memory issue posted for review.

We still have one remaining problem with some dom0 console spew on domU bootup

blk_tap: BLKTAP: READ request sector[8192002,16000], Total [8192000]
blk_tap: BLKTAP: Sector request greaterthan size

This happens on bootup within the initrd. After some initrd hacking
(basically, adding a bunch of sleep calls between steps), I've
determined that there are two distinct bursts of spew, one that
coincides with "Creating root device." (aka mkrootdev -t ext3 ...) and
one with "Mounting root filesystem." (aka mount /sysroot). Doesn't
matter if root is on lvm or a plain partition, happens the same way on a
guest with no lvm whatsoever and a guest w/lvm. Haven't yet been able to
trigger this spew doing heavy I/O within the guest either, thus far it
has only been triggered in the initrd.
Comment 24 Suzanne Yeghiayan 2007-06-29 16:15:00 EDT
From Jun 28 RHEL 5 meeting:

REPORTER: bstein
STATUS:   More progress.  Are booting and testing.  Fujitsu doesn't
          use blktap.
          Update: in POST as of Jun 21 PM.
REPORTER: bstein
STATUS:   Fujitsu just gave another patch Jun 27.
DECISION: Add to potential Beta respin of kernel.

Copied dzickus on bugzilla.
Comment 25 Don Zickus 2007-07-10 12:20:23 EDT
in 2.6.18-33.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5
Comment 26 Larry Troan 2007-07-11 10:03:54 EDT
Per comment #24, looks like Fujitsu provided the patch. 
Assume they will test this fix.
Comment 29 Mike Gahagan 2007-09-19 15:56:19 EDT
Confirmed that blktap is building on ia64 as of the -43 kernel
Comment 31 errata-xmlrpc 2007-11-07 14:15:24 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.