Will the scripts you've posted for self-compilation work with 4.3.6?

Yes, it should work. Only if there are some big changes on vbox or unraid they should require changes.

 

will there be any leftovers after a server restart ?

No. Unraid runs on a ramfs, loaded from bzroot file at every boot, any changes to this filesystem (in this case installing development tools, etc) will "disappear" after reboot.

10x.

Compiling 4.3.6 as we speak...

Will update ASAP

couldn't make 4.3.6 work. the plugin just didn't install it at startup.

downloaded 4.3.4 you've compiled and now everything works...

Thanks

Shlomi

Did you got some error or something while creating 4.3.6 package?

no errors, and it works until a restart of the server.

but the virtualbox plugin didn't start it up automatically after a restart (or am I missing something?)

Guess you need to somehow "let the plugin know" what package file it should load at startup?

The plugin can be configured to automatically restart the package  upon restart.

The plugin can be configured to automatically restart the package  upon restart.

Yes, but I'm guessing his problem may be the plugin doesn't know it needs to load the new package version - with different file name - that he did manually copy to the flash... I don't use the plugin myself then not sure how this is done to make the plugin use a different vbox package file, but you can surely help him on that.

no errors, and it works until a restart of the server.

but the virtualbox plugin didn't start it up automatically after a restart (or am I missing something?)

 

What is the file name?

 

after using the procedure outlined by nars, it created VirtualBox-4.3.6-91406-Linux_x86.tgz

after using the procedure outlined by nars, it created VirtualBox-4.3.6-91406-Linux_x86.tgz

 

That is the problem !

 

I am using a1aina's convention as mentioned here: http://vbox.a1aina.com/

 

you should rename your file to:  vbox-4.3.6-unRAID-3.9.11p.tgz (if it is for unraid v5.0.4 - kernel version 3.9.11p)

 

Wait... there is something wrong then... as my script do not create package with that file name, I guess that is the virtualbox file you downloaded from virtualbox site? not the created package - that one should be created as vbox-4.3.6-unRAID-3.9.11p.tgz as theone pointed. Then I guess your mistake was the last 'cp', you did actually copy to the flash the file you downloaded from virtualbox site and not the created package.

Wait... there is something wrong then... as my script do not create package with that file name, I guess that is the virtualbox file you downloaded from virtualbox site? not the created package - that one should be created as vbox-4.3.6-unRAID-3.9.11p.tgz as theone pointed. Then I guess your mistake was the last 'cp', you did actually copy to the flash the file you downloaded from virtualbox site and not the created package.

I have used your procedure as follows:

cd ~
/boot/dev/buildev.sh make
mkdir /tmpfs && mount -t tmpfs -o rw,size=1G tmpfs /tmpfs && export TMPDIR=/tmpfs
wget http://download.virtualbox.org/virtualbox/4.3.6/VirtualBox-4.3.6-91406-Linux_x86.run
sh VirtualBox-4.3.6-91406-Linux_x86.run
/boot/dev/vboxpkgc.sh
cp VirtualBox-4.3.6-91406-Linux_x86.tgz /boot/config/plugins/virtualbox

 

Your last step should be:

cp vbox-4.3.6-unRAID-3.9.11p.tgz /boot/config/plugins/virtualbox

As promised, and seeing that lainie isn't still updating his packages, here is my own compiled package for VirtualBox 4.3.6, with modules compiled on unRaid 5.0.5:

http://nars.aloj.net/temp/unraid/vbox-4.3.6-unRAID-3.9.11p.tgz

Thank you Nars.

 

I may be off base here but can we use the same procedure to compile a 64bit version of VirtualBox?

 

With the latest 64bit beta of unraid I'd be willing to try my VM's on it using vbox 64bit.

I know the push/interest regarding virtualization is to use the baked in options and that would certainly be my preference.

I'm more just curious if it's doable should I want to run the beta for a while and keep vbox.

@hoek: If you are referring to the steps/scripts I did posted some pages back, vboxpkgc.sh script maybe doesn't need any changes but buildev.sh will surely need some changes, at least to get proper Slackware 14.1 x64 packages for unRaid 6.0 instead of Slackware 13.1. I will soon test unRaid 6.0 on a VM and may check what changes needed on these scripts, but as you said KVM will be surely a better option on unRaid 6.0, when all ready for it.

Will KVM run on atom based board?

Will KVM run on atom based board?

Found this on a quick search:

http://serverfault.com/questions/555641/settings-kvm-on-atom-processor

VirtualBox 4.3.6 package for unRaid 6.0 beta (64-bit):

http://nars.aloj.net/temp/unraid/vbox-4.3.6-unRAID-3.10.24p-x86_64.tgz

 

Note: to use it with the VirtualBox plugin you may need to remove the '-x86_64' suffix on the package filename or the plugin may not like it...

 

@theone: is the suffix a problem? can it be sorted? also if you are going to do changes on the plugin could you please also make it support .txz packages? as it does an huge difference in package size...

 

Also I did updated my 'buildev.sh' script to support unRaid 6.x, detecting it and getting the right slackware 14.1 packages.

I will see (hopefully this week) what I can do to support an additional suffis for 64bit and txz.

 

 

VirtualBox 4.3.6 package for unRaid 6.0 beta (64-bit):

http://nars.aloj.net/temp/unraid/vbox-4.3.6-unRAID-3.10.24p-x86_64.tgz

 

Thanks Nars

nars,

 

Can you post your scripts for compiling virtualbox for unraid v5.0.5 / v6beta?

 

You can get them at same urls from the steps I posted some pages back:

http://lime-technology.com/forum/index.php?topic=25099.msg274366#msg274366

just note that you need to download "AMD64" version (even if you have an intel) from VirtualBox site.

I have compiled a version for unraid v5.0.5 but after installation I don't get "/root/.VirtualBox" folder and symbolic link as a result.

 

When is this supposed to be created?

Does this mean the compilation is bad?