Replying to myself again. :-P More on the problem building the rpm on Fedora 12.
On Wed, 2010-04-14 at 14:24 -0400, Michael H. Warfield wrote: > Hey all, > With the release of 2.6.32, I've been looking to get back involved with > OpenVZ. Quickly ran into a problem, though. I'm using cgroups but > found I could not mount the cgroups file system like on Fedora generic > like this in my fstab: > > cgroup /var/lib/cgroup cgroup defaults 0 0 > > Seems the cgroup file system isn't compiled in. Looking at at the > config, seems like there are a bunch of CGROUP related options that are > missing... > > 107a108,109 > > CONFIG_CGROUP_NS=y > > CONFIG_CGROUP_FREEZER=y > 108a111,117 > > CONFIG_CPUSETS=y > > CONFIG_PROC_PID_CPUSET=y > > CONFIG_CGROUP_CPUACCT=y > > CONFIG_RESOURCE_COUNTERS=y > > CONFIG_CGROUP_MEM_RES_CTLR=y > > CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y > > CONFIG_MM_OWNER=y > > I may even be missing a few there as well. > > I'm not entirely sure what's appropriate for the CONFIG_CGROUP_SCHED > option, though, since OpenVZ adds a CONFIG_VZ_FAIRSCHED=y option. Is > this going to be a major conflict? > > Updating the .ovz configs with the missing ones, it seems to compile > find under rpmbuild on Fedora 12 but then blows up in the build > process... > > Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.mMJQBD > + umask 022 > + cd /home/mhw/rpmbuild/BUILD > + '[' /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64 '!=' / ']' > + rm -rf /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64 > ++ dirname /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64 > + mkdir -p /home/mhw/rpmbuild/BUILDROOT > + mkdir /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64 > + cd kernel-2.6.32 > + LANG=C > + export LANG > + unset DISPLAY > + cd linux-2.6.32 > + /usr/lib/rpm/check-buildroot > + /usr/lib/rpm/redhat/brp-compress > + /usr/lib/rpm/redhat/brp-strip /usr/bin/strip > + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip > + /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump > + /usr/lib/rpm/brp-python-bytecompile > + /usr/lib/rpm/redhat/brp-python-hardlink > + /usr/lib/rpm/redhat/brp-java-repack-jars > Processing files: kernel-2.6.32-afanasyev.1.x86_64 > error: File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/boot/vmlinuz-2.6.32-afanasyev.1 > error: File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/boot/vmlinux-2.6.32-afanasyev.1 > error: File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/boot/System.map-2.6.32-afanasyev.1 > error: File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/lib/modules/2.6.32-afanasyev.1 > error: File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/lib/modules/2.6.32-afanasyev.1/kernel > error: File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/lib/modules/2.6.32-afanasyev.1/build > > > RPM build errors: > File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/boot/vmlinuz-2.6.32-afanasyev.1 > File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/boot/vmlinux-2.6.32-afanasyev.1 > File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/boot/System.map-2.6.32-afanasyev.1 > File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/lib/modules/2.6.32-afanasyev.1 > File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/lib/modules/2.6.32-afanasyev.1/kernel > File not found: > /home/mhw/rpmbuild/BUILDROOT/kernel-2.6.32-afanasyev.1.x86_64/lib/modules/2.6.32-afanasyev.1/build > I've seen that before. It's a problem in how $BUILDROOT is handled in > the .spec file. Seems like I started seeing that in some odd packages > beginning with F11. Actually, this problem is not at all what I had earlier experienced with other packages. That had to do with setting up RPM_BUILD_ROOT and the change in the default from /usr/srv/redhat to ~/rpmbuild. This is yet another change in the behavior of rpmbuild. It's now, apparently, handling the initial cleanup of RPM_BUILD_ROOT during the initial phase of the %install. OpenVZ has all the kernel install stuff being done in the %build phase, which is then blown away when rpmbuild does and rm -rf in the start of %install. That's going to have to be fixed, regardless, and the sooner the better. Doing it correctly with all the install work done during the install phase should work on all platforms appropriately. > RHEL 6 is looming closer. It's more likely to be F13 based than F12 > based but the build system problems are going to be similar and > certainly going to want fuller support for CGROUPS, since that's already > a significant feature of F12 as well as the latest cuts of Ubuntu. This has probably been broken since the Fedora 10 timeframe, since that's when a lot of these rpmbuild changes took place. It simply wasn't worth bothering to even make the effort until OpenVZ 2.6.32 came out due to the gap in the kernel revs. RHEL 6 and related ilk (CentOS, et al) will probably all follow suit and immediately develop the same problems as well. > Given that OpenVZ 2.6.32 is still pretty new, should these be filled in > Bugzilla or what? I have now filed a Bugzilla report on the spec file problem and building on Fedora, Bugzilla #1495. http://bugzilla.openvz.org/show_bug.cgi?id=1495 > Regards, > Mike Regards, Mike -- Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@wittsend.com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF | possible worlds. A pessimist is sure of it!
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users