Bug#403712: [Debian] Re: Bug#403712: kernel-patch-openvz: Cannot compile kernel, undefined symbols

2006-12-25 Thread David Baron
> > Get the following harmless quip on boot: > > Dec 23 18:26:18 d_baron kernel: Testing NMI watchdog ... CPU#0: NMI > > appears to be stuck (0->0)! > > This means that on your motherboard/CPUs kernel was unable > to setup NMI watchdog. nothing bad, except for kernel won't be > able to detect it's

Bug#403712: [Debian] Re: Bug#403712: kernel-patch-openvz: Cannot compile kernel, undefined symbols

2006-12-25 Thread Kirill Korotaev
David, >>Compiled and booted!! I apparently will work with "voluntary preemption" as >>well as "no premption". No oopses, flags. Next week I will start to play with >>it! > > >>Caveat: >>Unionfs will not compile against the patched sources (not using it yet so it >>can wait). > > > Get the

Bug#403712: [Debian] Re: Bug#403712: kernel-patch-openvz: Cannot compile kernel, undefined symbols

2006-12-22 Thread Kirill Korotaev
David, > Compiled and booted!! I apparently will work with "voluntary preemption" as > well as "no premption". No oopses, flags. Next week I will start to play with > it! thanks a lot for patience and help! all the faced bugs will be fixed in next version. > Caveat: > Unionfs will not compile a

Bug#403712: [Debian] Re: Bug#403712: kernel-patch-openvz: Cannot compile kernel, undefined symbols

2006-12-21 Thread Kirill Korotaev
David, > Got it to build and even attempt to boot--no undefineds! thanks a lot for your help! the previous bugs are fixed: http://bugzilla.openvz.org/show_bug.cgi?id=411 > The thing listed a lot of oops codes, many involving the journaling, so I > panicked and stopped it. > > Additionally, ther

Bug#403712: [Debian] Re: Bug#403712: kernel-patch-openvz: Cannot compile kernel, undefined symbols

2006-12-21 Thread Kirill Korotaev
David Baron wrote: > On Thursday 21 December 2006 08:16, Ola Lundqvist wrote: > >>Hi David >> >>When I compiled the kernel yesterday using the same version of the kernel >>and the openvz patch I did not need to do anything with symlinking. >> >>My compile line look something like this: >>export PA

Bug#403712: [Debian] Re: Bug#403712: kernel-patch-openvz: Cannot compile kernel, undefined symbols

2006-12-20 Thread Kirill Korotaev
David, >>David, >>ahhh... I guess I know the answer. >>you simply set CONFIG_VE_CALLS to 'y', while IPV6 support is in module, >>so OpenVZ kernel has reference to symbols in module :/ > > >>Pleae check CONFIG_VE_CALLS, CONFIG_VZ_DEV and CONFIG_IPV6 options > These thing are indeed set to 'y', IP

Bug#403712: [Debian] Re: Bug#403712: kernel-patch-openvz: Cannot compile kernel, undefined symbols

2006-12-20 Thread Kirill Korotaev
> This would seem to indicate one (or more) pieces that need be compiled into > the kernel, would it not? (I do compile in all the ovz stuff rather than > leave as modules because I had missing symbols on boot the last time I > tried.) > > If someone could point me in the correct direction

Bug#403712: [Debian] Re: Bug#403712: kernel-patch-openvz: Cannot compile kernel, undefined symbols

2006-12-20 Thread Kirill Korotaev
David, can you attach your resulting .config file please? Thanks, Kirill >>>Hi >>> >>>I have built it now and I have no problem building. Not at least >>>with make-kpkg. >> >>I use this. >> >> >>>According to upstream you did not run make oldconfig for some reason? >> >>It does this anyway. I co