Running VirtualBox VM host on ReadyNAS Pro

[fbmachines]

Mackila wrote:

Hi, You are the guy who made me buy 2x4GB for my pro... As I changed processor to E6600, I use my nas to host some VM. I got them running "as services" with help from scripts from here and there. When you want to start a VM then disconnect your ssh session, & is not enough. It only sends VBoxHeadless to the background, but it stays attached to your ssh session. Try this instead : nohup VBoxHeadless --startvm <uuid|name> --vrde on --vrdeaddress <host ip> --vrdeport <port for RDP> & - Mackila

I was able to close the SSH session with the '&'. After getting back to the prompt simply type 'logout'. Then you would be able to close the session and still have the VM running.

I will give your method a try also. Thanks for the heads up. 😄

Now if only I could figure out why a share from my VM isn't opening from a guest. :?

[jmalmlund]

Mackila wrote:

Hi, You are the guy who made me buy 2x4GB for my pro... As I changed processor to E6600, I use my nas to host some VM. I got them running "as services" with help from scripts from http://sisco.laf.free.fr/codes/MyVM.html and http://www.glump.net/howto/virtualbox_as_a_service#create_the_init.d_script. When you want to start a VM then disconnect your ssh session, & is not enough. It only sends VBoxHeadless to the background, but it stays attached to your ssh session. Try this instead : nohup VBoxHeadless --startvm <uuid|name> --vrde on --vrdeaddress <host ip> --vrdeport <port for RDP> & - Mackila fbmachines wrote: jmalmlund wrote: Edited my start command in the previous post.. you just need to add an '&' to the end of the start command to put the VBox process into the background allowing you to disconnect your ssh session. Thanks! I'll give it a try when I get home. I knew it had to be something simple. [...]

If you exit your shell cleanly whatever process you have put running in the background should keep running, I've never had any problems with this.

To cleanly disconnect/exit the shell you may use 'logout', 'exit' or press <ctrl-D> on an empty prompt.

[leak]

Ok, I've got to missed something here. Right now I have successfully installed Virtualbox on my Ultra, but then what?

I want to install CentOS, but how do I do that? Never used VB before. Is there any program I run on my PC that connects and manage VB on my NAS? Where I can install my ISO's, stop, start the server and so on?

And how do I check if VB is running? When i start it it says this

t0wnz:/backup/GPL# /etc/init.d/vboxdrv start
Starting VirtualBox kernel module ...done.
t0wnz:/backup/GPL#

But when I type

t0wnz:/backup/GPL# ps | grep vboxdrv
t0wnz:/backup/GPL#

I see nothing. What should I do 🙂 ?

edit; my bad.

t0wnz:/backup/GPL# ps -ef | grep vboxdrv
root     12170 20742  0 14:33 pts/0    00:00:00 grep vboxdrv
t0wnz:/backup/GPL#

[mdgm-ntgr]

You might want to take a look at this add-on: http://www.readynas.com/forum/viewtopic.php?f=48&t=44145

[leak]

mdgm wrote:
You might want to take a look at this add-on: http://www.readynas.com/forum/viewtopic.php?f=48&t=44145

Wonderful, exactly what I was looking for, but one problem tho...

How do I get the config file for the addon? Right now the config file looks like this

86400, // "never" changes 'getGuestOSTypes' => 86400, 'getSystemProperties' => 86400, 'getInternalNetworks' => 86400, 'getMediums' => 600, 'getVMs' => 2, '__getMachine' => 7200, '__getNetworkAdapters' => 7200, '__getStorageControllers' => 7200, '__getSharedFolders' => 7200, '__getUSBController' => 7200, ); */ } 

which I assume is wrong? Anyway, I cant access http://nas-ip/phpvboxmgr/ . "An unknown PHP error occurred...".

[WhoCares_]

Try a different browser, that's a known problem of the jquery-version I'm forced to use in the add-on.

-Stefan

[leak]

WhoCares? wrote:
Try a different browser, that's a known problem of the jquery-version I'm forced to use in the add-on. -Stefan

Tried both Firefox and Explorer, same thing. Is there any way I can doublecheck if vboxdrv really is running?

Edit; Looks like VB isnt running at all. And I dont get any error's when I run

t0wnz:~# /etc/init.d/vboxdrv start
Starting VirtualBox kernel module ...done.
t0wnz:~#

[WhoCares_]

I fear using SSH would be the only way. And while you're on the command line you may also fix the config file for the problem with line breaks shouldn't show there.

-Stefan

[leak]

WhoCares? wrote:
I fear using SSH would be the only way. And while you're on the command line you may also fix the config file for the problem with line breaks shouldn't show there. -Stefan

Theres no problem using ssh for me. And for the config file in frontview folder (ssh) there are not any linebreaks at all.

Should I see the VB when I type "ps -A" lika a running proccess? How can I confirm that it actually working?

t0wnz:~# /etc/init.d/vboxdrv status
VirtualBox kernel modules (vboxdrv, vboxnetflt and vboxnetadp) are loaded.

It all looks good, but I cant find anything about vbox under "ps -A" at all.

[WhoCares_]

Can't say much about that right now, will have to check when I'm in the office again later at night today.

-Stefan

[leak]

WhoCares? wrote:
Can't say much about that right now, will have to check when I'm in the office again later at night today. -Stefan

Thank you for taking time anyway. Really looking forward to getting this to work!
If it matter, I followed sphardy's guide (viewtopic.php?f=35&t=26468&start=225#p258406). But used the newest version (4.2.15) but the same VB version.

Edit; Made som headway! Installed the 4.0 instead, and now I get a config file for the phpscript. I have the vboxwebsrv running, but when i try to access nas-ip/phpboxmgr I get this message

SoapFault Object
(
    [message:protected] => Method 'ns1:ISystemProperties_getMaxVDISize' not implemented: method name or namespace not recognized
    [string:private] => 
    [code:protected] => 0
    [file:protected] => /frontview/ui/resource/html/phpvboxmgr/lib/vboxServiceWrappers.php
    [line:protected] => 3592
    [trace:private] => Array
        (
            [0] => Array
                (
                    [file] => /frontview/ui/resource/html/phpvboxmgr/lib/vboxServiceWrappers.php
                    [line] => 3592
                    [function] => __soapCall
                    [class] => SoapClient
                    [type] => ->
                    [args] => Array
                        (
                            [0] => ISystemProperties_getMaxVDISize
                            [1] => Array
                                (
                                    [0] => Array
                                        (
                                            [_this] => 2980c5227245087f-000000000000007e
                                        )

                                )

                        )

                )

            [1] => Array
                (
                    [file] => /frontview/ui/resource/html/phpvboxmgr/lib/vboxServiceWrappers.php
                    [line] => 54
                    [function] => getMaxVDISize
                    [class] => ISystemProperties
                    [type] => ->
                    [args] => Array
                        (
                        )

                )

            [2] => Array
                (
                    [file] => /frontview/ui/resource/html/phpvboxmgr/lib/vboxconnector.php
                    [line] => 2631
                    [function] => __get
                    [class] => VBox_ManagedObject
                    [type] => ->
                    [args] => Array
                        (
                            [0] => maxVDISize
                        )

                )

            [3] => Array
                (
                    [file] => /frontview/ui/resource/html/phpvboxmgr/lib/vboxconnector.php
                    [line] => 218
                    [function] => getSystemPropertiesCached
                    [class] => vboxconnector
                    [type] => ->
                    [args] => Array
                        (
                            [0] => Array
                                (
                                    [fn] => getSystemProperties
                                )

                            [1] => Array
                                (
                                    [data] => 
                                    [errors] => Array
                                        (
                                        )

                                    [persist] => Array
                                        (
                                        )

                                )

                        )

                )

            [4] => Array
                (
                    [function] => __call
                    [class] => vboxconnector
                    [type] => ->
                    [args] => Array
                        (
                            [0] => getSystemProperties
                            [1] => Array
                                (
                                    [0] => Array
                                        (
                                            [fn] => getSystemProperties
                                        )

                                    [1] => Array
                                        (
                                            [0] => Array
                                                (
                                                    [data] => 
                                                    [errors] => Array
                                                        (
                                                        )

                                                    [persist] => Array
                                                        (
                                                        )

                                                )

                                        )

                                )

                        )

                )

            [5] => Array
                (
                    [file] => /frontview/ui/resource/html/phpvboxmgr/lib/ajax.php
                    [line] => 93
                    [function] => getSystemProperties
                    [class] => vboxconnector
                    [type] => ->
                    [args] => Array
                        (
                            [0] => Array
                                (
                                    [fn] => getSystemProperties
                                )

                            [1] => Array
                                (
                                    [0] => Array
                                        (
                                            [data] => 
                                            [errors] => Array
                                                (
                                                )

                                            [persist] => Array
                                                (
                                                )

                                        )

                                )

                        )

                )

        )

    [faultstring] => Method 'ns1:ISystemProperties_getMaxVDISize' not implemented: method name or namespace not recognized
    [faultcode] => SOAP-ENV:Sender
)

Edit2; Seems like phpvirtualbox isnt compatible with php5 at all. Altho they have released a new build, version 0.4-5.
Is anyone here running phpvirtualbox with vbox 4.x.x successfully?

Edit3; Installed phpvbox 0.4-5 instead and now it works flawless! I just swaped the config file with the old config file and it worked (probably missed some new feature tho).

[leak]

New radiator out now and I updated without thinking about VB, so now it's broken. Tried to download the new .16 GPL but failing at "make ARCH=x86_64".

So, is it possible to install VB on the new radiator, 4.2.16 ?

And also, how do I expand the capacity? I choose about 10gb, but after 3-4gb its full. And Should it really be stored at /dev/md0?

[jmalmlund]

leak wrote:
New radiator out now and I updated without thinking about VB, so now it's broken. Tried to download the new .16 GPL but failing at "make ARCH=x86_64". So, is it possible to install VB on the new radiator, 4.2.16 ?

It should be, working on it... 😉

Edit: It seems Netgear has made some mistake or I'm just tired... the new GPL source supplied contains kernel version 2.6.37.5.RNx86_64.2.2 but the kernel that's included in 4.2.16 is version 2.6.37.5.RNx86_64.2.1

It's nearing midnight localtime so I'm of to bed so I can look at this with fresh eyes tomorrow...

Edit2: Since I had recompiled a couple of modules in 4.2.15 I copied that .config file and never really reacted to this earlier..

Netgear have not only provided us with a GPL source that doesn't match the one they used to build the actual 4.2.16 release but they also have an incomplete kernel source lacking patches needed to compile!
Both drivers/target/target_core_iblock.c and drivers/target/target_core_pscsi.c and has references to an undecleard pointer, 'blkdev_get_by_path'

I'm going to try and patch the source now but I fear I might break Frontview by replacing the firmware kernel by my own build. So I think we're out of luck (to get VirtualBox back any easy way) until Netgear realizes their mistake and re-releases the GPL source they really did use when they built 4.2.16.

[jmalmlund]

leak wrote:
And also, how do I expand the capacity? I choose about 10gb, but after 3-4gb its full. And Should it really be stored at /dev/md0?

/dev/md0 is system root which is 4GB and you should really NOT store ANYTHING on there unless absolutely necessary, which should be close to never.
Keep all your data on /dev/c/c,d,e,f.... and if you want to have something to appear to be on a system path use symlinks to the actual data.

[WhoCares_]

jmalmlund wrote:
Edit: It seems Netgear has made some mistake or I'm just tired... the new GPL source supplied contains kernel version 2.6.37.5.RNx86_64.2.2 but the kernel that's included in 4.2.16 is version 2.6.37.5.RNx86_64.2.1

I don't know how you come to that conclusion. The GPL sources I'm using contain a kernel that identifies itself as "2.6.37.5.RNx86_64.2.1" - as can be checked by

cd linux-2.6.37.5/arch/x86/configs
grep "RNx86" *

Should list defconfig.smp with a CONFIG_LOCALVERSION string of ".RNx86_64.2.1"

jmalmlund wrote:
Netgear have not only provided us with a GPL source that doesn't match the one they used to build the actual 4.2.16 release but they also have an incomplete kernel source lacking patches needed to compile! Both drivers/target/target_core_iblock.c and drivers/target/target_core_pscsi.c and has references to an undecleard pointer, 'blkdev_get_by_path'

I just compiled the kernel for the fun of it. Those two files you name aren't built here at all so that has to be related to a problem with your kernel config. Also the kernel is built without problems for me.

jmalmlund wrote:
I'm going to try and patch the source now but I fear I might break Frontview by replacing the firmware kernel by my own build.

No need to worry, you simply can't replace the kernel. The worst thing that'll happen is that your modules will fail to load.

jmalmlund wrote:
So I think we're out of luck (to get VirtualBox back any easy way) until Netgear realizes their mistake and re-releases the GPL source they really did use when they built 4.2.16.

Well, I don't know who's to blame here and I'm not going to judge either. All I can say is that it works for me using the GPL source archive I downloaded. Which may be a different one than the one you downloaded but I don't know that either. I do know, however, that the md5sum of my GPL sources archive matches the MD5 given at the download page for 4.2.16 GPL sources.

-Stefan

[jmalmlund]

WhoCares? wrote:

jmalmlund wrote: Edit: It seems Netgear has made some mistake or I'm just tired... the new GPL source supplied contains kernel version 2.6.37.5.RNx86_64.2.2 but the kernel that's included in 4.2.16 is version 2.6.37.5.RNx86_64.2.1 I don't know how you come to that conclusion. The GPL sources I'm using contain a kernel that identifies itself as "2.6.37.5.RNx86_64.2.1" - as can be checked by cd linux-2.6.37.5/arch/x86/configs grep "RNx86" * Should list defconfig.smp with a CONFIG_LOCALVERSION string of ".RNx86_64.2.1"

Yes, it should, but my first download said ".2" in the end.. but then again, I downloaded the sources before the link and listed md5sum was posted.
Now after re-downloading and checking the md5sum this time around I get the correct md5sum so I'll start over now.

WhoCares? wrote:

jmalmlund wrote: Netgear have not only provided us with a GPL source that doesn't match the one they used to build the actual 4.2.16 release but they also have an incomplete kernel source lacking patches needed to compile! Both drivers/target/target_core_iblock.c and drivers/target/target_core_pscsi.c and has references to an undecleard pointer, 'blkdev_get_by_path' I just compiled the kernel for the fun of it. Those two files you name aren't built here at all so that has to be related to a problem with your kernel config. Also the kernel is built without problems for me.

I took the config file from 4.2.15 and started from that, I think they are or at least were needed for iSCSI target.

WhoCares? wrote:

jmalmlund wrote: I'm going to try and patch the source now but I fear I might break Frontview by replacing the firmware kernel by my own build. No need to worry, you simply can't replace the kernel. The worst thing that'll happen is that your modules will fail to load. jmalmlund wrote: So I think we're out of luck (to get VirtualBox back any easy way) until Netgear realizes their mistake and re-releases the GPL source they really did use when they built 4.2.16. Well, I don't know who's to blame here and I'm not going to judge either. All I can say is that it works for me using the GPL source archive I downloaded. Which may be a different one than the one you downloaded but I don't know that either. I do know, however, that the md5sum of my GPL sources archive matches the MD5 given at the download page for 4.2.16 GPL sources. -Stefan

Well, I'm to blame for posting to soon, cuz, a re-download of the source wasn't hard to do :? :oops:

[leak]

jmalmlund wrote:

leak wrote: And also, how do I expand the capacity? I choose about 10gb, but after 3-4gb its full. And Should it really be stored at /dev/md0? /dev/md0 is system root which is 4GB and you should really NOT store ANYTHING on there unless absolutely necessary, which should be close to never. Keep all your data on /dev/c/c,d,e,f.... and if you want to have something to appear to be on a system path use symlinks to the actual data.

Hum, weird that vb installs my OS there then? How do i change so it installs it under /dev/c ?

And how do I update my VB now that I'm on .16? Just like before?

[horim80]

I tried to re-install VirtualBox on 4.2.16
When I try to compile kernel then I got error.

nas-EA-40-4F:/backup/GPL/linux-2.6.37.5# make ARCH=x86_64
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/docproc
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/kxgettext.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/lex.zconf.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'.  Stop.

Any advice?

[WhoCares_]

cd linux-2.6.37.5
make mrproper
cp arch/x86/configs/defconfig.smp .config
make ARCH=x86_64 silentoldconfig

-Stefan

[horim80]

WhoCares? wrote:
cd linux-2.6.37.5 make mrproper cp arch/x86/configs/defconfig.smp .config make ARCH=x86_64 silentoldconfig -Stefan

Thanks for FAST reply!
It working!

[leak]

WhoCares? wrote:
cd linux-2.6.37.5 make mrproper cp arch/x86/configs/defconfig.smp .config make ARCH=x86_64 silentoldconfig -Stefan

Cant get my kernel module to start. vbox-install.log

Makefile:170: Warning: using /usr/src/linux as the source directory of your Linux kernel. If this is not correct, specify KERN_DIR=<directory> and run Make again.
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -C /usr/src/linux modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
	echo;								\
	echo "  ERROR: Kernel configuration is invalid.";		\
	echo "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
	echo "         Run 'make oldconfig && make prepare' on kernel src to fix it.";	\
	echo;								\
	/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*

  WARNING: Symbol version dump /c/backup/GPL/linux-2.6.37.5/Module.symvers
           is missing; modules will have no dependencies and modversions.

make -f scripts/Makefile.build obj=/tmp/vbox.0
/tmp/vbox.0/Makefile:170: Warning: using /usr/src/linux as the source directory of your Linux kernel. If this is not correct, specify KERN_DIR=<directory> and run Make again.
  gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d  -nostdinc -isystem /usr/lib/gcc/i486-linux-gnu/4.1.2/include -I/c/backup/GPL/linux-2.6.37.5/arch/x86/include -Iinclude  -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_FXSAVEQ=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -fno-stack-protector -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -Wdeclaration-after-statement -Wno-pointer-sign -I/usr/src/linux/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxdrv/ -I/tmp/vbox.0/vboxdrv/include -I/tmp/vbox.0/vboxdrv/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS  -DMODULE  -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)"  -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /tmp/vbox.0/linux/.tmp_SUPDrv-linux.o /tmp/vbox.0/linux/SUPDrv-linux.c
In file included from /tmp/vbox.0/linux/SUPDrv-linux.c:31:
/tmp/vbox.0/linux/../SUPDrvInternal.h:81:30: error: linux/version.h: No such file or directory
/tmp/vbox.0/linux/../SUPDrvInternal.h:84:12: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/linux/../SUPDrvInternal.h:84:33: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/linux/../SUPDrvInternal.h:84:47: error: missing binary operator before token "("
/tmp/vbox.0/linux/../SUPDrvInternal.h:88:8: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/linux/../SUPDrvInternal.h:88:29: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/linux/../SUPDrvInternal.h:88:43: error: missing binary operator before token "("
In file included from include/linux/gfp.h:4,
                 from include/linux/slab.h:12,
                 from /tmp/vbox.0/linux/../SUPDrvInternal.h:100,
                 from /tmp/vbox.0/linux/SUPDrv-linux.c:31:
include/linux/mmzone.h:18:30: error: generated/bounds.h: No such file or directory
include/linux/mmzone.h:254:5: warning: "MAX_NR_ZONES" is not defined
In file included from include/linux/gfp.h:4,
                 from include/linux/slab.h:12,
                 from /tmp/vbox.0/linux/../SUPDrvInternal.h:100,
                 from /tmp/vbox.0/linux/SUPDrv-linux.c:31:
include/linux/mmzone.h:303: error: ‘MAX_NR_ZONES’ undeclared here (not in a function)
In file included from /tmp/vbox.0/linux/SUPDrv-linux.c:31:
/tmp/vbox.0/linux/../SUPDrvInternal.h:101:8: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/linux/../SUPDrvInternal.h:101:30: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/linux/../SUPDrvInternal.h:101:44: error: missing binary operator before token "("
/tmp/vbox.0/linux/../SUPDrvInternal.h:104:34: error: asm/semaphore.h: No such file or directory
In file included from /tmp/vbox.0/linux/SUPDrv-linux.c:32:
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:43:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:43:26: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:43:40: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:46:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:46:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:46:41: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:66:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:66:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:66:41: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:72:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:72:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:72:41: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:78:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:78:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:78:41: error: missing binary operator before token "("
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:81,
                 from /tmp/vbox.0/linux/SUPDrv-linux.c:32:
include/linux/mm.h:466:63: warning: "NR_PAGEFLAGS" is not defined
include/linux/mm.h:514:62: warning: "NR_PAGEFLAGS" is not defined
In file included from /tmp/vbox.0/linux/SUPDrv-linux.c:32:
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:86:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:86:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:86:41: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:89:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:89:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:89:41: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:94:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:94:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:94:41: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:117:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:117:26: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:117:40: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:130:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:130:26: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:130:40: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:171:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:171:26: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:171:40: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:205:7: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:205:29: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:205:43: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:207:7: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:207:29: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:207:43: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:225:6: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:225:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:225:41: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:232:6: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:232:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:232:41: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:270:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:270:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:270:41: error: missing binary operator before token "("
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:358:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:358:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:358:41: error: missing binary operator before token "("
/tmp/vbox.0/linux/SUPDrv-linux.c:47:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:47:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:47:41: error: missing binary operator before token "("
/tmp/vbox.0/linux/SUPDrv-linux.c:69:7: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:69:28: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:69:42: error: missing binary operator before token "("
/tmp/vbox.0/linux/SUPDrv-linux.c:172:6: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:172:28: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:172:42: error: missing binary operator before token "("
/tmp/vbox.0/linux/SUPDrv-linux.c:220:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:220:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:220:41: error: missing binary operator before token "("
/tmp/vbox.0/linux/SUPDrv-linux.c: In function ‘vboxdrvLinuxUid’:
/tmp/vbox.0/linux/SUPDrv-linux.c:223: error: ‘struct task_struct’ has no member named ‘uid’
/tmp/vbox.0/linux/SUPDrv-linux.c:229:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:229:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:229:41: error: missing binary operator before token "("
/tmp/vbox.0/linux/SUPDrv-linux.c: In function ‘vboxdrvLinuxGid’:
/tmp/vbox.0/linux/SUPDrv-linux.c:232: error: ‘struct task_struct’ has no member named ‘gid’
/tmp/vbox.0/linux/SUPDrv-linux.c:238:5: warning: "LINUX_VERSION_CODE" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:238:27: warning: "KERNEL_VERSION" is not defined
/tmp/vbox.0/linux/SUPDrv-linux.c:238:41: error: missing binary operator before token "("
/tmp/vbox.0/linux/SUPDrv-linux.c: In function ‘vboxdrvLinuxEuid’:
/tmp/vbox.0/linux/SUPDrv-linux.c:241: error: ‘struct task_struct’ has no member named ‘euid’
make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxdrv] Error 2

Any tips?

[WhoCares_]

Without further information: Not really 😉 Did you run at least "make modules_prepare" in your kernel directory?

-Stefan

[fbmachines]

How do I completely remove VB so I can start from scratch?

[leak]

WhoCares? wrote:
Without further information: Not really 😉 Did you run at least "make modules_prepare" in your kernel directory? -Stefan

Did one, but almost the same problem.. This time vboxdrv setup took some longer time, but it failed anyway..

If I remove everything and re-install it, can I follow the guide a couple pages back but change to the new version? And copy the file like you posted?

[WhoCares_]

Sure. I just can't guarantee it will work then. I haven't tried to install VirtualBox on 4.2.16 yet, so I'm not yet familiar with all the possible problems and pitfalls.

-Stefan