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: Stephan Böni <boeni@xxxxxx>
Date: Fri, 2 Sep 2005 18:26:50 +0200
Delivery-date: Fri, 02 Sep 2005 16:24:51 +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: AcWvyOqMsQmhrKIKQLCisL3ib4uZ4gAEc2zA
Thread-topic: [Xen-users] Re: Xen installation
>> 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


>       - make ARCH=xen dep
>       - make ARCH=xen vmlinuz
>       - 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?

Thanks
Stephan

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

<Prev in Thread] Current Thread [Next in Thread>