Vbox modules are not built after installing kernel-3.11.0-200.fc19.x86_64

Sérgio Basto sergio at serjux.com
Sat Sep 14 03:16:39 UTC 2013


On Qui, 2013-09-12 at 09:42 +0200, Joachim Backes wrote: 
> 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.
after update VirtualBox-kmodsrc with :
rpm -Uvh
http://buildsys.rpmfusion.org/plague-results/fedora-development-rpmfusion_free/VirtualBox/4.2.16-2.fc20/x86_64/VirtualBox-kmodsrc-4.2.16-2.fc20.x86_64.rpm

in F19 akmods works for me 

you have same rpm here for i686 :
http://buildsys.rpmfusion.org/plague-results/fedora-development-rpmfusion_free/VirtualBox/4.2.16-2.fc20/i686/VirtualBox-kmodsrc-4.2.16-2.fc20.i686.rpm


This technique also for fedora vm guests of F20 

feel free to ask anything 


Best regards, 
-- 
Sérgio M. B.



More information about the test mailing list