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] Re: Xen installation

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Re: Xen installation
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Fri, 2 Sep 2005 19:07:43 +0100
Cc: "John A. Sullivan III" <jsullivan@xxxxxxxxxxxxxxxxxxx>, Stephan Böni <boeni@xxxxxx>
Delivery-date: Fri, 02 Sep 2005 18:05:32 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1125682151.3067.56.camel@localhost>
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>
References: <983B408465C04C49B0344D51FA21C7553E7416@xxxxxxxxxxxxxxxxxxx> <1125682151.3067.56.camel@localhost>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
Easiest way to build your kernels:

* Download Xen source bia tarball or mercurial.
* make world
* cd linux-2.6.whatever-xen0
* make ARCH=xen menuconfig # change stuff
* cd ..
* make dist

*Should* pick up your config changes and put the build kernels under the 
dist/install/ tree.

Cheers,
Mark

On Friday 02 September 2005 18:29, John A. Sullivan III wrote:
> On Fri, 2005-09-02 at 18:42 +0200, Stephan Böni wrote:
> > >> I'm trying to install xen-2.0-testing and having some troubles.. Docs
> > >> for Xen seem to be pretty vague about installation process and mostly
> > >> tell me to use binary package.
> > >>
> > >> I want to compile my own kernel (both privileged and unprivileged),
> > >> and can't figure out, how..
> > >>
> > >> Could someone tell me precise steps to do this?
> > >
> > >* Unpack kernel source tree somewhere (call it $KERNELSRCDIR)
> > >
> > >* cd $XENSRCDIR/linux-2.x.yy-xen-sparse
> > >
> > >* Run mkbuildtree from the linux-2.x.yy-xen-sparse directory with
> > > $KERNELSRCDIR as an argument (eg ./mkbuildtree $KERNELSRCDIR)
> > >
> > >* Go back to the kernel source dir and build your kernel more-or-less as
> > > normal, but set the architecture to xen *at* *all* *times* (ghods
> > > how much mess I've caused by not following that rule).  So,
> > > basically:
> > >
> > > - make ARCH=xen menuconfig
> >
> > # make ARCH=xen menuconfig
> > scripts/kconfig/mconf arch/xen/Kconfig
> > arch/xen/i386/Kconfig:747: can't open file "drivers/pci/pcie/Kconfig"
> > make[1]: *** [menuconfig] Error 1
> > make: *** [menuconfig] Error 2
> >
> > # cd drivers/pci
> > # ln -s . pcie
> > # cd ../..
> >
> > Now it works. Do i need to select something in the menu?
> >
> > > - make ARCH=xen dep
> >
> > not needed anymore (with kernel 2.6)
> >
> > >   - make ARCH=xen vmlinuz
> >
> > # make ARCH=xen vmlinuz
> >   CHK     include/linux/version.h
> >   CC      arch/i386/kernel/asm-offsets.s
> > In file included from include/asm-xen/asm/msr.h:5,
> >                  from include/asm-xen/asm/processor.h:17,
> >                  from include/asm/thread_info.h:16,
> >                  from include/linux/thread_info.h:21,
> >                  from include/linux/spinlock.h:12,
> >                  from include/linux/capability.h:45,
> >                  from include/linux/sched.h:7,
> >                  from arch/i386/kernel/asm-offsets.c:7:
> > include/asm-xen/hypervisor.h:44:39: asm-generic/pgtable-nopmd.h: No such
> > file or directory
> > In file included from include/asm-xen/asm/msr.h:5,
> >                  from include/asm-xen/asm/processor.h:17,
> >                  from include/asm/thread_info.h:16,
> >                  from include/linux/thread_info.h:21,
> >                  from include/linux/spinlock.h:12,
> >                  from include/linux/capability.h:45,
> >                  from include/linux/sched.h:7,
> >                  from arch/i386/kernel/asm-offsets.c:7:
> > include/asm-xen/hypervisor.h:79: error: parse error before '*' token
> > include/asm-xen/hypervisor.h:79: warning: function declaration isn't a
> > prototype include/asm-xen/hypervisor.h:90: error: parse error before '*'
> > token include/asm-xen/hypervisor.h:90: warning: function declaration
> > isn't a prototype In file included from include/linux/timex.h:61,
> >                  from include/linux/sched.h:11,
> >                  from arch/i386/kernel/asm-offsets.c:7:
> > include/asm-xen/asm/io.h:48:31: asm-generic/iomap.h: No such file or
> > directory make[1]: *** [arch/i386/kernel/asm-offsets.s] Error 1
> > make: *** [arch/i386/kernel/asm-offsets.s] Error 2
> >
> > >   - make ARCH=xen modules
> > >   - make ARCH=xen modules-install
> > >
> > >* Copy the built vmlinuz file to /boot/whatever.
> > >
> > >The only difference, effectively, between the dom0 and domU is choosing
> > >whether to enable the privileged guest (dom0).  Note that a lot of
> > > kernel options (IDE support) tend to get turned off in domU mode, so
> > > don't worry if your .config file looks a little thin when building the
> > > domU.
> >
> > What's wrong? Do you have any solution?
>
> <snip>
> ouch! I'm afraid I don't off hand and am under a nasty deadline and so
> can't be of much help.  I hope someone else on the list can step in and
> help - John

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