WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Problems building a xen0 kernel on Suse 9.3

To: "James Bulpin" <James.Bulpin@xxxxxxxxxxxx>
Subject: RE: [Xen-users] Problems building a xen0 kernel on Suse 9.3
From: "Jeffrey Buell" <jbuell@xxxxxxxxxx>
Date: Tue, 24 May 2005 11:40:50 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 24 May 2005 18:40:18 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVgF75xfWostUNcRlKJMnUtGgSaoAAdW66w
Thread-topic: [Xen-users] Problems building a xen0 kernel on Suse 9.3
James,

I did exactly the same thing as you did, except I skipped your initial rpm
command (but rpm -qa confirms I have the right source).  In the end I got the
same undefined references as before.  Hopefully you can fix your "unrelated
problems" so we can see if this is a SUSE/Xen problem or not.  An unrelated
issue is using the O= option to relocate the build output to a different
directory.  Do you ever use this?  This works fine for the regular kernel but
causes an immediate failure when building a Xen kernel (missing asm
directories).

Jeff

# rpm -qa | grep source
kernel-source-2.6.11.4-20a
# make ARCH=xen

  <everything compiles>

  CHK     include/linux/compile.h
  UPD     include/linux/compile.h
  CC      init/version.o
  LD      init/built-in.o
  LD      .tmp_vmlinux1
arch/xen/kernel/built-in.o(.text+0x85b): In function `ctrl_if_suspend':
: undefined reference to `teardown_irq'
drivers/built-in.o(.text+0x4b2c7): In function `balloon_process':
balloon.c: undefined reference to `kmap_flush_unused'
make: *** [.tmp_vmlinux1] Error 1


> 
> On Tue, May 24, 2005 1:59 am, James Bulpin said:
> > I've just tried a build of the tree extracted from that RPM 
> on my FC3 box
> > - it appears to build fine. I'll check on a SuSe box 
> tomorrow - access
> > isn't practical right now.
> 
> I tried the following on an out-of-the-box SuSE 9.3 install:
> 
> rpm --install /tmp/kernel-source-2.6.11.4-20a.i586.rpm
> cd /usr/src/linux  (symlinks to linux-2.6.11.4-20a)
> cp ./arch/i386/defconfig.xen .config
> make ARCH=xen oldconfig
> make ARCH=xen
> 
> It got a good way through the build and only stopped due to 
> an unrelated
> problem.
> 
> Can you post the actual errors you saw?
> 
> Regards,
> 
> James
> 
> > On Mon, May 23, 2005 6:01 pm, Jeffrey Buell said:
> >> James,
> >>
> >> Not much chance of insulting my intelligence here.  I have 
> been using
> >> Xen
> >> as
> >> part of the Fedora core 4 development releases, but I'm 
> new to SuSE 9.3.
> >> In
> >> FC4 I use the source RPMs (for both the kernel and Xen) as 
> supplied by
> >> Fedora, and I'd like to do the same with SuSE, using 
> source from the
> >> installation CDs.  I didn't need to install any source RPM 
> in order to
> >> build
> >> the regular kernel.  Does Xen need something extra not installed by
> >> SuSE?
> >> I'm not sure if I'm "building a xen kernel tree".  In FC4 the xen
> >> kernels
> >> are
> >> built in the same way and same directory as the regular 
> kernel.  I just
> >> need
> >> ARCH=xen and a xen config file.  Is the procedure 
> different in SuSE?
> >>
> >> Thanks for your help,
> >>
> >> Jeff
> >>
> >>>
> >>> Jeff,
> >>>
> >>> Please don't take this the wrong way, I don't mean to insult your
> >>> intelligence - are you sure you're building a xen kernel tree
> >>> rather than
> >>> the native (ARCH=xen will not work on the latter). Presumably
> >>> this is the
> >>> SuSE source RPM rather than one of our tarball or BK
> >>> distributions? Could
> >>> be an issue with the location that the RPM installs the source to.
> >>>
> >>> Regards,
> >>>
> >>> James
> >>> (will be offline from now until tomorrow)
> >>>
> >>> On Fri, May 20, 2005 11:03 pm, Jeffrey Buell said:
> >>> > I installed Suse 9.3 Pro along with all the kernel tools
> >>> and sources.  I
> >>> > was
> >>> > easily able to build a new regular kernel, but not a xen0
> >>> kernel.  With
> >>> > ARCH=xen and using the supplied config file, "make" almost
> >>> immediately
> >>> > runs
> >>> > into problems creating links to various asm directories in the
> >>> > kernel/build
> >>> > dir.  I fixed this by copying all of /usr/src/linux into
> >>> kernel/build.
> >>> > Everything then compiled but I got 2 undefined references:
> >>> teardown_irq
> >>> > in
> >>> > ctrl_if_suspend, and kmap_flush_unused in balloon_process.
> >>> Presumably
> >>> > there
> >>> > is no bug since a working xen0 kernel was supplied in the
> >>> distro.  What do
> >>> > people do differently when building a xen0 kernel vs. a
> >>> regular kernel?
> >>> >
> >>> > Jeff

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users