Re: [Xen-users] problem building a PAE system

[AndreGround <andreground@xxxxxxxxx>]

Probably I've found the issue!

When rpmbuild goes for building the -xen version of the kernel it uses
the -xen.config file and it doesn't care about pae_flags in .spec
file! PAE is enabled by default!

[root@localhost linux-2.6.19.i686]# cat .config | grep PAE
CONFIG_X86_PAE=y
[root@localhost linux-2.6.19.i686]#

I'll come back tomorrow with my test results and details about what
I've discovered.

Must sleep now :)

Andrea

On 2/3/07, AndreGround <andreground@xxxxxxxxx> wrote:
> I would like to have PAE off in my dom0 cause I think that is the
> reason why I'm unable to start my old FC3 domU.
>
> I know that it would probably go fine if I choose the XenSource way
> but I really want to find an answer to this question...is it
> impossible to build both Kernel & HV with PAE disabled starting from
> SRPMs using FC6? Why if I turn off PAE in the .spec file I always get
> PAE mismatch error (dom0=yes)? How could dom0 be PAE enabled if I'm
> rebuilding kernels?
>
> Second thing is that I would like not to lose Fedora's updates to
> Kernel & HV and going for the SRPMs is the only way to get this.
>
> There must be a way :)
>
> Thanks again,
> Andrea
>
> On 2/3/07, Robert Hatch <robert.hatch@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > Can I ask why you want pae off?  Your system obviously supports it as
> > the dom0 would not boot so why must pae be off in the domU's?
> >
> > Anyway the solution to your problem is probably to either build xen from
> > source (hypervisor and xen kernel) or use the half way house of
> > downloading and installing the binary have a look here:
> > http://www.xensource.com/download/dl_304tarballs.html
> >
> > In binary you can choose whether to use a pae or non-pae hypervisor
> > which comes prebuilt with an appropriate kernel.  I prefer building the
> > whole thing from source as I do a lot of devel but to get going the
> > binary is fine. (just make sure you make the initrd and check/add the
> > grub conf when you install)
> >
> > rob
> >
> > p.s. remove the rpm's and reboot first just to be on the safe side
> >
> >
> > -----Original Message-----
> > From: AndreGround [mailto:andreground@xxxxxxxxx]
> > Sent: 02 February 2007 22:17
> > To: Robert Hatch; xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-users] problem building a PAE system
> >
> > Thanks for your reply Robert. Any help/idea is *REALLY* appreciated.
> >
> > The problem is that I don't want PAE enabled :)
> > Fedora provides both kernel & HV RPMs with PAE enabled.
> >
> > I'm actually trying to build both kernel & HV from Fedora's RPMs in
> > order to disable PAE support but I can't get them working as I always
> > stop @ the same point. "PAE mismatch between xen and dom0 (xen=no
> > dom0=yes)" when loading my brand new kernel.
> >
> > As you can see from the .spec file I've posted, I've disabled any
> > PAE-related flag.
> >
> > So, now, I have a lot of doubts:
> > 1) Why it happens?
> > 2) What does it exactly mean with dom0=yes?
> > 3) Does Fedora RPMs include, build and install also the hypervisor?
> > 4) Why Fedora Xen RPMs .spec file doesn't talk about PAE support?
> > 5) ... and so on ...
> >
> > Please help me...I'm going crazy! :)
> >
> > Andrea
> >
> > On 2/2/07, Robert Hatch <robert.hatch@xxxxxxxxxxxxxxxx> wrote:
> > > Have you installed the PAE hypervisor? As I understand it you need the
> > > kernel and hypervisor to match i.e. both need to be PAE (or in you
> > case
> > > not) otherwise you get this message.
> > >
> > > Hope this helps
> > >
> > > Rob
> > >
> > > -----Original Message-----
> > > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> > > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> > AndreGround
> > > Sent: 02 February 2007 16:15
> > > To: Daniel P. Berrange
> > > Cc: Petersson, Mats; Emiliano Gabrielli (aka AlberT);
> > > xen-users@xxxxxxxxxxxxxxxxxxx; Nico Kadel-Garcia
> > > Subject: Re: [Xen-users] problem building a PAE system
> > >
> > > Hi!
> > > with this .spec file, I get a brand new kernel from source with PAE
> > > disabled but I always get "PAE mode mismatch between Xen and DOM0
> > > (xen=no, dom0=yes) when I try to start it!
> > >
> > > Where's the mistake?
> > >
> > > Thanks in advance!
> > >
> > > .spec file:
> > >
> > > Summary: The Linux kernel (the core of the Linux operating system)
> > >
> > > # What parts do we want to build?  We must build at least one kernel.
> > > # These are the kernels that are built IF the architecture allows it.
> > >
> > > %define buildup 1
> > > # Only used on archs without run-time support (ie ppc, sparc64)
> > > %define buildsmp 0
> > > %define buildpae 0
> > > # Whether to apply the Xen patches, leave this enabled.
> > > %define includexen 1
> > > # Whether to build the Xen kernels, disable if you want.
> > > %define buildxen 1
> > > %define builddoc 0
> > > %define buildkdump 1
> > > %define buildheaders 1
> > > %define builddebug 0
> > >
> > > # Versions of various parts
> > >
> > > # After branching, please hardcode these values as the
> > > # %dist and %rhel tags are not reliable yet
> > > # For example dist -> .el5 and rhel -> 5
> > > #% define dist .XX
> > > #% define rhel Y
> > >
> > > #
> > > # Polite request for people who spin their own kernel rpms:
> > > # please modify the "release" field in a way that identifies
> > > # that the kernel isn't the stock distribution kernel, for example by
> > > # adding some text to the end of the version number.
> > > #
> > > %define sublevel 19
> > > %define kversion 2.6.%{sublevel}
> > > %define rpmversion 2.6.%{sublevel}
> > > %define release %(R="$Revision: 1.2895dru $"; RR="${R##: }"; echo
> > > ${RR%%?})%{?dist}
> > > %define signmodules 0
> > > %define xen_hv_cset 11774
> > > %define make_target bzImage
> > > %define kernel_image x86
> > > %define xen_flags verbose=y crash_debug=y
> > > %define xen_target vmlinuz
> > > %define xen_image vmlinuz
> > >
> > > %define KVERREL %{PACKAGE_VERSION}-%{PACKAGE_RELEASE}
> > > %define hdrarch %_target_cpu
> > >
> > > # groups of related archs
> > > #OLPC stuff
> > > %if 0%{?olpc}
> > > %define buildxen 0
> > > %define buildkdump 0
> > > %endif
> > > # Don't build 586 kernels for RHEL builds.
> > > %if 0%{?rhel}
> > > %define all_x86 i386 i686
> > > # we differ here b/c of the reloc patches
> > > %ifarch i686 x86_64
> > > %define buildkdump 0
> > > %endif
> > > %else
> > > %define all_x86 i386 i586 i686
> > > %endif
> > >
> > > # Override generic defaults with per-arch defaults
> > >
> > > %ifarch noarch
> > > %define builddoc 1
> > > %define buildup 0
> > > %define buildheaders 0
> > > %define all_arch_configs $RPM_SOURCE_DIR/kernel-%{kversion}-*.config
> > > %endif
> > >
> > > # Do debug builds on i686, x86_64
> > > %ifarch i686 x86_64
> > > %define builddebug 1
> > > %endif
> > >
> > > # kdump only builds on i686, x86_64, ppc64 ...
> > > %ifnarch i686 x86_64 ppc64 ppc64iseries
> > > %define buildkdump 0
> > > %endif
> > >
> > > # Xen only builds on i686, x86_64 and ia64 ...
> > > %ifnarch i686 x86_64 ia64
> > > %define buildxen 0
> > > %endif
> > >
> > > # Second, per-architecture exclusions (ifarch)
> > >
> > > %ifarch ppc64iseries i686 i586
> > > %define buildheaders 0
> > > %endif
> > >
> > > %ifarch %{all_x86}
> > > %define all_arch_configs
> > $RPM_SOURCE_DIR/kernel-%{kversion}-i?86*.config
> > > %define image_install_path boot
> > > %define signmodules 0
> > > %define hdrarch i386
> > > %endif
> > >
> > > %ifarch i686
> > > %define buildpae 0
> > > # we build always xen HV with pae
> > > %define xen_flags verbose=y crash_debug=y pae=n
> > > %endif
> > >
> > > %ifarch x86_64
> > > %define all_arch_configs
> > > $RPM_SOURCE_DIR/kernel-%{kversion}-x86_64*.config
> > > %define image_install_path boot
> > > %define signmodules 0
> > > %endif
> > >
> > > %ifarch ppc64 ppc64iseries
> > > %define all_arch_configs
> > > $RPM_SOURCE_DIR/kernel-%{kversion}-ppc64*.config
> > > %define image_install_path boot
> > > %define signmodules 0
> > > %define make_target vmlinux
> > > %define kernel_image vmlinux
> > > %define kernel_image_elf 1
> > > %define hdrarch powerpc
> > > %endif
> > >
> > > %ifarch s390
> > > %define all_arch_configs
> > $RPM_SOURCE_DIR/kernel-%{kversion}-s390*.config
> > > %define image_install_path boot
> > > %define make_target image
> > > %define kernel_image arch/s390/boot/image
> > > %endif
> > >
> > > %ifarch s390x
> > > %define all_arch_configs
> > $RPM_SOURCE_DIR/kernel-%{kversion}-s390x.config
> > > %define image_install_path boot
> > > %define make_target image
> > > %define kernel_image arch/s390/boot/image
> > > %define hdrarch s390
> > > %endif
> > >
> > > %ifarch sparc
> > > %define all_arch_configs
> > $RPM_SOURCE_DIR/kernel-%{kversion}-sparc.config
> > > %define make_target image
> > > %define kernel_image image
> > > %endif
> > >
> > > %ifarch sparc64
> > > %define buildsmp 1
> > > %define all_arch_configs
> > > $RPM_SOURCE_DIR/kernel-%{kversion}-sparc64*.config
> > > %define make_target image
> > > %define kernel_image image
> > > %endif
> > >
> > > %ifarch ppc
> > > %define all_arch_configs
> > > $RPM_SOURCE_DIR/kernel-%{kversion}-ppc{-,.}*config
> > > %define image_install_path boot
> > > %define make_target vmlinux
> > > %define kernel_image vmlinux
> > > %define kernel_image_elf 1
> > > %define buildsmp 1
> > > %define hdrarch powerpc
> > > %endif
> > >
> > > %ifarch ia64
> > > %define all_arch_configs
> > $RPM_SOURCE_DIR/kernel-%{kversion}-ia64*.config
> > > %define image_install_path boot/efi/EFI/redhat
> > > %define signmodules 0
> > > %define make_target compressed
> > > %define kernel_image vmlinux.gz
> > > # ia64 xen HV doesn't building with debug=y at the moment
> > > %define xen_flags verbose=y crash_debug=y
> > > %define xen_target compressed
> > > %define xen_image vmlinux.gz
> > > %endif
> > >
> > > # To temporarily exclude an architecture from being built, add it to
> > > # %nobuildarches. Do _NOT_ use the ExclusiveArch: line, because if we
> > > # don't build kernel-headers then the new build system will no longer
> > > let
> > > # us use the previous build of that package -- it'll just be
> > completely
> > > AWOL.
> > > # Which is a BadThing(tm).
> > >
> > > # We don't build a kernel on i386 or s390x -- we only do
> > kernel-headers
> > > there.
> > > # We also don't support s390, iseries and ia64 on Fedora.
> > > %define nobuildarches i386 s390 s390x ppc64iseries ia64
> > >
> > > %ifarch %nobuildarches
> > > %define buildup 0
> > > %define buildsmp 0
> > > %define buildpae 0
> > > %define buildxen 0
> > > %define buildkdump 0
> > > %define _enable_debug_packages 0
> > > %endif
> > >
> > >
> > > #
> > > # Three sets of minimum package version requirements in the form of
> > > Conflicts:
> > > # to versions below the minimum
> > > #
> > >
> > > #
> > > # First the general kernel 2.6 required versions as per
> > > # Documentation/Changes
> > > #
> > > %define kernel_dot_org_conflicts  ppp < 2.4.3-3, isdn4k-utils <
> > > 3.2-32, nfs-utils < 1.0.7-12, e2fsprogs < 1.37-4, util-linux < 2.12,
> > > jfsutils < 1.1.7-2, reiserfs-utils < 3.6.19-2, xfsprogs < 2.6.13-4,
> > > procps < 3.2.5-6.3, oprofile
> > > < 0.9.1-2
> > >
> > > #
> > > # Then a series of requirements that are distribution specific, either
> > > # because we add patches for something, or the older versions have
> > > # problems with the newer kernel or lack certain things that make
> > > # integration in the distro harder than needed.
> > > #
> > > %define package_conflicts initscripts < 7.23, udev < 063-6, iptables <
> > > 1.3.2-1, ipw2200-firmware < 2.4, selinux-policy-targeted < 1.25.3-14
> > >
> > > #
> > > # The ld.so.conf.d file we install uses syntax older ldconfig's don't
> > > grok.
> > > #
> > > %define xen_conflicts glibc < 2.3.5-1, xen < 3.0.1
> > >
> > > [...]
> > >
> > > On 1/19/07, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote:
> > > > On Fri, Jan 19, 2007 at 07:39:52PM +0100, AndreGround wrote:
> > > > > Perfect. Thanks everybody.
> > > > > I'll try to modify the spec in the SRPM of the kernel.
> > > > >
> > > > > So (taken from the same set):
> > > > > - Modified Kernel with PAE disabled (obtained by rebuilding the
> > > Fedora's
> > > > > SRPM)
> > > > > - Original hypervisor RPM (the one provided by Fedora, not
> > modified)
> > > >
> > > > In Fedora packaging, the kernel-xen RPM also contains the
> > hypervisor.
> > > > So you just need to re-build the single RPM - make sure you turn off
> > > > PAE for the kernel & hv bits of the build process though.
> > > >
> > > > Dan.
> > > > --
> > > > |=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392
> > > 2496 -=|
> > > > |=-           Perl modules: http://search.cpan.org/~danberr/
> > > -=|
> > > > |=-               Projects: http://freshmeat.net/~danielpb/
> > > -=|
> > > > |=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B
> > > 9505  -=|
> > > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-users
> > >
> > >
> >
> >
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users