[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Jeffrey Buell" <jbuell@xxxxxxxxxx>
  • Date: Mon, 23 May 2005 11:01:31 -0700
  • Delivery-date: Mon, 23 May 2005 18:01:01 +0000
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcVd/Q2tzTTkEV9/TSufjnVIj68gaABwcRQw
  • Thread-topic: Xen-users Digest, Vol 3, Issue 55


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,
> 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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.