OpenVZ Forum


Home » General » Discussions » VirtualBox compatibility
Re: VirtualBox compatibility [message #33040 is a reply to message #32893] Thu, 18 September 2008 20:56 Go to previous messageGo to previous message
januszzz is currently offline  januszzz
Messages: 50
Registered: January 2007
Location: Opole, Poland
Member
I confirm the bug. Vbox modules fail to compile on OpenVZ kernel 2.6.18-028stab053-1 (in HN of course):

[...]
Building modules, stage 2.
make -rR -f /usr/src/linux-2.6.18-openvz-028.053-r2/scripts/Makefile.mod post
scripts/mod/modpost -m -i /usr/src/linux-2.6.18-openvz-028.053-r2/Module.symvers -I /var/tmp/portage/app-emulation/virtualbox-modules-2.0.2/work /vboxdrv/Module.symvers -o /var/tmp/portage/app-emulation/virtualbox-modules-2.0.2/work /vboxdrv/Module.symvers vmlinux /var/tmp/portage/app-emulation/virtualbox-modules-2.0.2/work /vboxdrv/vboxdrv.o
WARNING: "register_cpu_notifier" [/var/tmp/portage/app-emulation/virtualbox-modules-2.0.2/wor k/vboxdrv/vboxdrv.ko] undefined!
make[2]: *** [__modpost] Error 1
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.18-openvz-028.053-r2'
make: *** [vboxdrv] Error 2

This is serious problem as I'm completely running all my machines on 2.6.18. Is there a way to solve this? maybe we should ask on Vbox / Sun forum too?
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message icon11.gif
Previous Topic: How is this Done?
Next Topic: Help ....Please ... Is this Possible
Goto Forum:
  


Current Time: Thu Jul 11 12:24:10 GMT 2024

Total time taken to generate the page: 0.02344 seconds