On 09/12/2013 09:18 AM, Joachim Backes wrote: > Hi all testers, > > having a problem after updating from kernel3.10.11-200.fc19.x86_64 to > kernel-3.11.0-200.fc19.x86_64: The vbox mudules are not built during > reboot. I saw akmodbuild failing: > ------------------------------------------------------------------------------------ > 12 Sep 07:17:06 akmods: Building RPM using the command '/bin/akmodsbuild > --target x86_64 --kernels 3.11.0-200.fc19.x86_64 > /usr/src/akmods/VirtualBox-kmod.latest' > make: Entering directory `/usr/src/kernels/3.11.0-200.fc19.x86_64' > CC [M] > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxnetflt/linux/VBoxNetFlt-linux.o > CC [M] > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxnetflt/VBoxNetFlt.o > CC [M] > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxnetflt/SUPR0IdcClient.o > CC [M] > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxnetflt/SUPR0IdcClientComponent.o > CC [M] > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxnetflt/linux/SUPR0IdcClient-linux.o > LD [M] > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxnetflt/vboxnetflt.o > Building modules, stage 2. > MODPOST 1 modules > CC > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxnetflt/vboxnetflt.mod.o > LD [M] > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxnetflt/vboxnetflt.ko > make: Leaving directory `/usr/src/kernels/3.11.0-200.fc19.x86_64' > + for module in 'vbox{netadp,netflt,sf,video,pci}' > + make VBOX_USE_INSERT_PAGE=1 -j2 -C > /usr/src/kernels/3.11.0-200.fc19.x86_64 > SUBDIRS=/tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxsf > modules > make: Entering directory `/usr/src/kernels/3.11.0-200.fc19.x86_64' > CC [M] > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxsf/vfsmod.o > CC [M] > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxsf/dirops.o > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxsf/dirops.c:292:5: > error: unknown field 'readdir' specified in initializer > .readdir = sf_dir_read, > ^ > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxsf/dirops.c:292:5: > warning: initialization from incompatible pointer type [enabled by default] > /tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxsf/dirops.c:292:5: > warning: (near initialization for 'sf_dir_fops.flush') [enabled by default] > make[1]: *** > [/tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxsf/dirops.o] > Error 1 > make[1]: *** Waiting for unfinished jobs.... > make: *** > [_module_/tmp/akmodsbuild.1oMvBmcT/BUILD/VirtualBox-kmod-4.2.16/_kmod_build_3.11.0-200.fc19.x86_64/vboxsf] > Error 2 > make: Leaving directory `/usr/src/kernels/3.11.0-200.fc19.x86_64' > error: Bad exit status from /var/tmp/rpm-tmp.7VlATv (%build) > > > RPM build errors: > user mockbuild does not exist - using root > group mockbuild does not exist - using root > user mockbuild does not exist - using root > group mockbuild does not exist - using root > Bad exit status from /var/tmp/rpm-tmp.7VlATv (%build) > ---------------------------------------------------------------------------------------- > > I rebooted several times, but this did not help. Reinstalling VirtualBox > ans akmod-Virtualbox did not help too. For me thats a known problem, > because after each update from kernel-3.x.uuu to kernel-3.y.vvv I have > these problems if x differs from y. > > Anybody has a good recipe for me? Thanks in advance. Or should I file a > BZ against DKMS? > > Kind regards > > Joachim Backes > Sorry, I forgot to say that I'm using VBox from rpmfusion.

Joachim Backes <joachim.backes <at> rhrk.uni-kl.de> writes: > having a problem after updating from kernel3.10.11-200.fc19.x86_64 to > kernel-3.11.0-200.fc19.x86_64: The vbox mudules are not built during > reboot. I saw akmodbuild failing: VirtualBox 4.2.16 does not support the 3.11 kernel ( https://www.virtualbox.org/ticket/11946 ). You need to use 4.2.18, which is now available from the Oracle repo,

or wait for Rpmfusion to update their version.

https://www.virtualbox.org/ticket/12083 ). Oracle has a 4.3 Beta 2 ( https://forums.virtualbox.org/viewtopic.php?f=1&t=57311 ) but I haven't tried that.

On 12.09.2013 10:19, Joachim Backes wrote: > On 09/12/2013 09:53 AM, Andre Robatino wrote: >> Joachim Backes <joachim.backes <at> rhrk.uni-kl.de> writes: >> >>> having a problem after updating from kernel3.10.11-200.fc19.x86_64 to >>> kernel-3.11.0-200.fc19.x86_64: The vbox mudules are not built during >>> reboot. I saw akmodbuild failing: >> VirtualBox 4.2.16 does not support the 3.11 kernel ( >> https://www.virtualbox.org/ticket/11946 ). You need to use 4.2.18, which is >> now available from the Oracle repo, >> > Hi Andre, > > this was I tried to avoid, but I know that installing vbox from oracle > always helps in such a situation. So I'll wait until vbox-4.2.18 from > rpmfusion appears :-( > > Thanks. > > Joachim Backes Just in case, until vbox gets updated, here [1] is the kmod SRPM with patches for kernel-3.11 compatibility that I'm currently using. Sandro [1] http://smani.fedorapeople.org/kmod-VirtualBox-4.2.16-1.20130819.fc20.x86_...