Running VirtualBox VM host on ReadyNAS Pro

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.