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"
Well, just like you said Stefan, it was the second alternative that turned out to be correct, I was tired (and running a fever) and clearly not paying enough attention to what I was doing. Thank you for pointing that out to me 😉
When I started out working with *nix systems a friend of mine helped me and gave me a script that I've kept around , it's purpose was to make a diff between two kernel sources and transfer manual changes from the old source tree to the new one's config. A nice help back then before I learnt how to configure the kernel I needed for the computer I had, but not very foolproof I've now learnt... because I hadn't copied /arch/x86/configs/defconfig.smp to .config it took my entire .config file from the 4.2.15 source and basically copied that into the 4.2.16 source tree... now you might remember that the kernel in 4.2.15 was CONFIG_LOCALVERSION=".RNx86_64.2.2" and THAT'S what I saw and noticed that it didn't match `uname -r` ...
So this is to all I've might have offended by saying that the Netgear guys had messed up, Please forgive my mistake! :oops: :oops:
The good news is that since I started over with a fresh source doing all my changes manually I've now got all needed bits and pieces up and running and my VirtualBox servers are back up. Still running a slight fever so I'm going to hit the sack again (already slept most of the day) and unless someone else beats me to it I'll try and write an short how-to on installing/updating all that's needed to get VirtualBox up-to-date and running on 4.2.16.
Once again, thank you Stefan for :slap: you gave me, guess I needed it :roll: :lol:
mkdir /c/VirtualBox cd /c/VirtualBox wget -q http://www.readynas.com/download/GPL/RNDP6xxx_4.2.16_WW_src.zip unzip -q RNDP6xxx_4.2.16_WW_src.zip "linux-2.6.37.5/*" ln -snf `pwd`/linux-2.6.37.5 /usr/src/linux cd linux-2.6.37.5 cp arch/x86/configs/defconfig.smp .config make ARCH=x86_64 silentoldconfig make prepare make modules_prepare make make modules
Section 3, optional for upgraders, not relevant for new installs. IF upgraders want to start clean with the install insert this command now to uninstall previous lingering VirtualBox components.
Note that it's the extpack that contains the RDP module...
Instructions on how to install/create/configure/start VM's might be added later if needed.
Edit: Fixed wrong parameter on uninstall command. Edit 2: Added two lines to create a work-directory, "VirtualBox" on your data volume "c" to avoid filling the root filesystem (when logging in as root the default directory is /root/ which resides on the small 4GB system partition). Also added a few "extra" make commands after Sebastien and I found that they were needed on his ReadyNAS to successfully build the VBox kernel modules, I didn't need them but since they don't hurt in any way (just takes a tad bit longer to complete the kernel preparations) I include them in the guide as a precaution.
First, thank you for your instructions. VirtualBox works very well on RAIDiator 4.2.15 but since the update, and despite your guide, I can no longer start it.
ChildNemesis:~# /usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.37.5.RNx86_64.2.1) or it failed to load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed. 0%... Progress state: NS_ERROR_FAILURE VBoxManage: error: Failed to install "/root/Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack": Extension pack 'Oracle VM VirtualBox Extension Pack' is already installed. In case of a reinstallation, please uninstall it first
ChildNemesis:~# /etc/init.d/vboxdrv setup Stopping VirtualBox kernel modules ...done. Uninstalling old VirtualBox DKMS kernel modules ...done. Trying to register the VirtualBox kernel modules using DKMS ...failed! (Failed, trying without DKMS) Recompiling VirtualBox kernel modules ...failed! (Look at /var/log/vbox-install.log to find out what went wrong)
Progress state: NS_ERROR_FAILURE VBoxManage: error: Failed to install "/root/Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack": Extension pack 'Oracle VM VirtualBox Extension Pack' is already installed. In case of a reinstallation, please uninstall it first
ChildNemesis:~# /etc/init.d/vboxdrv setup Stopping VirtualBox kernel modules ...done. Uninstalling old VirtualBox DKMS kernel modules ...done. Trying to register the VirtualBox kernel modules using DKMS ...failed! (Failed, trying without DKMS) Recompiling VirtualBox kernel modules ...failed! (Look at /var/log/vbox-install.log to find out what went wrong)
Would you have an idea of what to do?
Havin the same problem. vbox-install.log
t0wnz:~# cat /var/log/vbox-install.log Makefile:167: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
I get this on my ultra 4, I'm using /c/.vbox as the working directory, not sure if that makes a difference
frodo:/c/.vbox# /usr/bin/VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.37.5.RNx86_64.2.1) or it failed to load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed. 0%... Progress state: NS_ERROR_FAILURE VBoxManage: error: Failed to install "/c/.vbox/Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack": Extension pack 'Oracle VM VirtualBox Extension Pack' is already installed. In case of a reinstallation, please uninstall it first frodo:/c/.vbox# /etc/init.d/vboxdrv setup Stopping VirtualBox kernel modules ...done. Uninstalling old VirtualBox DKMS kernel modules ...done. Trying to register the VirtualBox kernel modules using DKMS ...failed! (Failed, trying without DKMS) Recompiling VirtualBox kernel modules ...failed! (Look at /var/log/vbox-install.log to find out what went wrong) frodo:/c/.vbox# cat /var/log/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/.vbox/linux-2.6.37.5/Module.symvers is missing; modules will have no dependencies and modversions.
Been working with Sebastien over msn tonight to get this sorted and we've eliminated some potential issues but it's still to early for me to tell when we might have a universal solution. 😐😞 Results using my guide seems vary, so for now, please be aware that upgrades may or may not work!
frodo:/c/.vbox# /etc/init.d/vboxdrv setup Stopping VirtualBox kernel modules ...done. Uninstalling old VirtualBox DKMS kernel modules ...done. Removing old VirtualBox netadp kernel module ...done. Removing old VirtualBox netflt kernel module ...done. Removing old VirtualBox kernel module ...done. Trying to register the VirtualBox kernel modules using DKMS ...failed! (Failed, trying without DKMS) Recompiling VirtualBox kernel modules ...done. Starting VirtualBox kernel modules ...failed! (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
dmsg:
vboxdrv: no symbol version for module_layout
What's your status on this now? Have you worked it out? If not, could you help me help you, please give some more details on your system, what model NAS do you have, what RAIDiator version is it running and so on. Also check your kernel source directory, does the file "Module.symvers" exist? The dmsg output that you included is known to happen if that file's not found.
Firstly - Thanks for the guide - I'm busy running through the Virtualbox installation now!
Secondly, Apologise if I'm asking some stupid questions here (I'm new to Linux and VirtualBox).
Can I confirm that the only way to manage Virtualbox on the NAS is via the CLi? The reason that I ask it that VMWare Esxi (That with which I am familiar), uses a Windows application to connect to and manage the VMWare enviroment, only the basic setup is done in the console.
OK - I think I have Virtualbox successfully installed and running..
I'm trying to get PHPVirtualbox running so I can manage the VM environment. I've searched the forum but cannot find the answer to these two questions:
The addon requires that you have one vm running - Catch 22 here, as I was going to use phpvboxmgr to create one..... Is CLi the only option? What does verifying the config do? What should it look like? Mine looks like this:
I haven't used VirtualBox on the ReadyNAS, but I think you'd need to create your first VM using the CLI (thereafter you should hopefully be able to use the GUI). As for getting VirtualBox to automatically start on each boot, I think there's instructions somewhere (maybe in this thread).
VRDE Connection: not active Clients so far: 8 Last started: 2011/05/14 13:59:14 UTC Last ended: 2011/05/14 14:05:14 UTC Sent: 0 Bytes Average speed: 0 B/s Sent total: 0 Bytes Received: 0 Bytes Speed: 0 B/s Received total: 0 Bytes
Guest:
OS type: Linux26 Additions run level: 2 Configured memory balloon size: 0 MB
ok hope you can use some of this.
if someone has ideas which flag should be turned on to improve the performance of the VM please let me know
VBoxManage modifyvm "Kubuntu" --pae off --nestedpaging off --vtxvpid off --hwvirtex off --hwvirtexexcl off --ioapic off VBoxManage modifyvm "Kubuntu" --vram 32 --usb off --usbehci off
I'm not sure if these really needed but the Pro Pionner has not a CPU with VTX or things like these and VBox turned on these flags on default i guess
edit: here is a deamon script for the nas so it will save the VM when the NAS will restart or shutdown and auto launch it on powerup:
#!/bin/bash ### BEGIN INIT INFO # Provides: vboxheadless # Required-Start: $local_fs $remote_fs $network $syslog # Required-Stop: $local_fs $remote_fs $network $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 ### END INIT INFO # # vboxheadless This init.d script is used to start and Stop VM'S. # VBOXNAME="Kubuntu"
wont work, well it does not make an error or something but it also wont be displayed in the logs (messages, syslog, system, deamon or dmesg) maybe a netgear thing. could somebody please tell me which command I could use so it will be displayed in the deamon.log or in frontview in the protocol tab or both?
I installed Windows 7 Ultimate x32 as the guest and for the life of me I can not get Windows 7 to detect a NIC card. Does anyone have any suggestions? Other thank that, it is working great!
Virtual networking hardware For each card, you can individually select what kind of hardware will be presented to the virtual machine. VirtualBox can virtualize the following six types of networking hardware:
