NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Running VirtualBox VM host on ReadyNAS Pro
What is VirtualBox?
So, I got bored while laundry was going... and decided to see how well a virtual OS would run on the Pro. My first choice of VM was VirtualBox, just cause I'm familiar with it after using it for ages, plus its open and free :) Eventually, I may look into VMWare as well.
After a bit of messing around, got it installed. Since the system is based off of Debian, was easy to get VirtualBox itself there (deb package). The trickiest part was getting the kernel modules required installed (see end of post).
In the end, I've got Windows 2003 R2 running on my Pro, interacting with it via RDP, and I am happy with the performance. I've added an extra 1GB memory (for a total of 2GB). I assigned 1GB of ram to my virtual OS, which still leaves the default configuration of 1GB for the NAS itself (which is more than enough still, 800MB+ is always cached).
I made a 10GB virtual disk to install the OS on. If I need more space later for extra applications, I can just add another virtual drive to that installation. And since I always like a bit extra security, I went a bit beyond the usual, and also have TrueCrypt running full disk encryption in the virtual OS. So no one can even boot and read the data in that OS without my bootup password.
I don't really have any screenshots to show, just a standard Windows installation. Here is a few of the steps I used while creating the VM on the console:
VirtualBox 3.1 has changed the CLI configuration. Until I update this how-to, please reference this: http://www.uhleeka.com/blog/2009/12/vir ... 9-04-host/
With the OS booted up and just sitting at the desktop, top reports:
Ad-hoc installation of VirtualBox. Should work for RAIDiator 4.2.4. Download links for the kernel modules, for those who don't want to go through the mess of compiling them.
So, I got bored while laundry was going... and decided to see how well a virtual OS would run on the Pro. My first choice of VM was VirtualBox, just cause I'm familiar with it after using it for ages, plus its open and free :) Eventually, I may look into VMWare as well.
After a bit of messing around, got it installed. Since the system is based off of Debian, was easy to get VirtualBox itself there (deb package). The trickiest part was getting the kernel modules required installed (see end of post).
In the end, I've got Windows 2003 R2 running on my Pro, interacting with it via RDP, and I am happy with the performance. I've added an extra 1GB memory (for a total of 2GB). I assigned 1GB of ram to my virtual OS, which still leaves the default configuration of 1GB for the NAS itself (which is more than enough still, 800MB+ is always cached).
I made a 10GB virtual disk to install the OS on. If I need more space later for extra applications, I can just add another virtual drive to that installation. And since I always like a bit extra security, I went a bit beyond the usual, and also have TrueCrypt running full disk encryption in the virtual OS. So no one can even boot and read the data in that OS without my bootup password.
I don't really have any screenshots to show, just a standard Windows installation. Here is a few of the steps I used while creating the VM on the console:
VirtualBox 3.1 has changed the CLI configuration. Until I update this how-to, please reference this: http://www.uhleeka.com/blog/2009/12/vir ... 9-04-host/
# Creating the Virtual Machine.
$ VBoxManage createvm -name "Windows2003" -register
$ VBoxManage modifyvm "Windows2003" -memory "1024MB" -acpi on -boot1 dvd -nic1 nat
$ VBoxManage createvdi -filename "/c/backup/VirtualBox/Windows2003.vdi" -size 10000 -register
$ VBoxManage modifyvm "Windows2003" -hda "/c/backup/VirtualBox/Windows2003.vdi"
$ VBoxManage registerimage dvd /c/backup/VirtualBox/Windows2003Ent.iso
$ VBoxManage modifyvm "Windows2003" -dvd /c/backup/VirtualBox/Windows2003Ent.iso
$ VBoxHeadless -startvm "Windows2003" &
# Connected via Remote Desktop at this point.
# After the installation, first page requires Ctrl-Alt-Del, so I sent the keycodes.
$ VBoxManage controlvm "Windows2003" keyboardputscancode 1d 38 53
# System is up and running, time to install GuestAdditions for better video, etc.
$ wget http://download.virtualbox.org/virtualbox/2.2.2/VBoxGuestAdditions_2.2.2.iso
$ VBoxManage registerimage dvd /c/backup/VirtualBox/VBoxGuestAdditions_2.2.2.iso
$ VBoxManage controlvm "Windows2003" dvdattach /c/backup/VirtualBox/VBoxGuestAdditions_2.2.2.iso
With the OS booted up and just sitting at the desktop, top reports:
top - 16:17:10 up 1 day, 17:58, 1 user, load average: 0.00, 0.01, 0.00
Tasks: 93 total, 1 running, 92 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.7%us, 0.2%sy, 0.0%ni, 99.2%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 2072432k total, 2020100k used, 52332k free, 6120k buffers
Swap: 1048536k total, 144k used, 1048392k free, 784620k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
10297 root 20 0 1104m 1.0g 4720 S 4 52.5 57:31.53 VBoxHeadless
12792 root 20 0 46092 9520 1720 S 1 0.5 59:54.51 motion
12196 root 20 0 9196 7688 980 S 0 0.4 0:57.72 wastesrv
1 root 20 0 1948 600 508 S 0 0.0 0:01.30 init
Ad-hoc installation of VirtualBox. Should work for RAIDiator 4.2.4. Download links for the kernel modules, for those who don't want to go through the mess of compiling them.
$ mkdir /lib/modules/`uname -r`/miscOr, if you want to compile the kernel modules yourself:
$ cd /lib/modules/`uname -r`/misc
$ wget http://www.readynas.com/contributed/chirpa/modules/virtualbox/pro/vboxdrv.ko
$ wget http://www.readynas.com/contributed/chirpa/modules/virtualbox/pro/vboxnetflt.ko
$ echo "deb http://download.virtualbox.org/virtualbox/debian etch non-free" >> /etc/apt/sources.list
$ wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | apt-key add -
$ apt-get update
$ apt-get install virtualbox-2.1
$ /etc/init.d/vboxdrv start
envyious:/c/backup# echo "deb http://download.virtualbox.org/virtualbox/debian etch non-free" >> /etc/apt/sources.listInstall of VirtualBox 2.2.2, before Sun updates the Debian Repository...
envyious:/c/backup# wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | apt-key add -
envyious:/c/backup# apt-get update && apt-get install build-essential
...
Setting up build-essential (11.3) ...
envyious:/c/backup# wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.4_WW_src.zip
envyious:/c/backup# unzip -q RNDP6xxx_4.2.4_WW_src.zip -d ./GPL
envyious:/c/backup# cd GPL/linux-x86-2.6/
envyious:/c/backup/GPL/linux-x86-2.6# make && make prepare
...
envyious:/c/backup/GPL/linux-x86-2.6# ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux
envyious:/c/backup/GPL/linux-x86-2.6# KERN_DIR=/usr/src/linux
envyious:/c/backup/GPL/linux-x86-2.6# apt-get install virtualbox-2.1
...
Setting up virtualbox-2.1 (2.1.4-42893_Debian_etch) ...
Adding group `vboxusers' (GID 101) ...
Done.
Messages emitted during module compilation will be logged to /var/log/vbox-install.log.
Success!
Starting VirtualBox kernel module: done.
envyious:/c/backup/GPL/linux-x86-2.6# cd
envyious:/c/backup/GPL/linux-x86-2.6# VBoxManage list vms
VirtualBox Command Line Management Interface Version 2.1.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
# wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.4_WW_src.zip
# unzip -q RNDP6xxx_4.2.4_WW_src.zip -d ./GPL
# cd GPL/linux-x86-2.6/
# make && make prepare
# ln -s /c/backup/GPL/linux-x86-2.6/ /usr/src/linux
# export KERN_DIR=/usr/src/linux
# apt-get install libfontconfig1 libglib2.0-0 libice6 libsdl1.2debian libsm6 libx11-6 libxcursor1 libxext6 libxi6 libxmu6 libxrandr2 libxrender1 libxslt1.1 libxt6 python2.4
# wget -q http://download.virtualbox.org/virtualbox/2.2.2/virtualbox-2.2_2.2.2-46594_Debian_etch_i386.deb
# dpkg -i virtualbox-2.2_2.2.2-46594_Debian_etch_i386.deb
Setting up virtualbox-2.2 (2.2.2-46594_Debian_etch) ...
Recompiling VirtualBox kernel module: done.
Starting VirtualBox kernel module: done.
441 Replies
Replies have been turned off for this discussion
- 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? 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.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.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 bycd 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.
-StefanWhoCares? 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 bycd 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: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?- 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? cd linux-2.6.37.5
make mrproper
cp arch/x86/configs/defconfig.smp .config
make ARCH=x86_64 silentoldconfig
-StefanWhoCares? 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!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.logMakefile: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?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
