Porteus

Porteus User Forum
https://forum.porteus.org/

Virtual Box

https://forum.porteus.org/viewtopic.php?f=117&t=6997

Page 1 of 1

Virtual Box

Posted: 13 Jun 2017, 11:47
by raja
I tried to build VB in v 3.2.2 64 bit. The builder downloaded necessary sources,compiled, and left "VirtualBox-5.1.22-115126-Linux_amd64" executable for run command and and a "VirtualBox-5.1.22-porteus-v3.2.2-x86_64-1prt" .xzm module.

Terminal checks for archive integrity and vanishes. I don't get to see VB gui.

any help?

Re: Virtual Box

Posted: 13 Jun 2017, 12:52
by donald
rightclick and activate:
VirtualBox-5.1.22-porteus-v3.2.2-x86_64-1prt.xzm
and ignore the *.run file.
this file is/was used to build the module.

EDIT
VirtualBox-5.1.22-115126 made in XFCE x86_64

http://filehorst.de/d/bfBjmBDd

How to get it:
Wait 15 sec > click "Jetzt zur Download-Seite" (means go to download page) >
click "Klicke hier, um ihn zu starten" (means click to start the download)

Re: Virtual Box

Posted: 13 Jun 2017, 20:22
by fulalas
I'm facing the same problem: http://forum.porteus.org/viewtopic.php? ... 105#p55932

@donald, could you help us explaining how exactly you're building with Vbox builder?

Re: Virtual Box

Posted: 13 Jun 2017, 20:39
by beny
hi to build virtualbox we need the devel package,and the crippled-source of the kernel that is in use,virtualbox follow the kernel version so if you change kernel version you have to rebuild the kernel module of virtualbox..

Re: Virtual Box

Posted: 13 Jun 2017, 21:47
by fulalas
@beny, there's some missing piece. I did exactly this with Porteus 3.2.2 x64 untouched (i.e. kernel 4.9.0):

1- activate devel x64 module;
2- activate crippled_sources x64 module;
3- activate Python 2.7.11 x64 module;
4- build VirtuaBox 5.1.22 from inside Vbox builder;

It generates a VirtualBox module inside /tmp. After activating it, I try to open VirtuaBox, then getting this message:

Code: Select all

VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/opt/VirtualBox/VBoxRT.so",) failed: <NULL>

VirtualBox: Tip! It may help to reinstall VirtualBox.
Looking at /var/log/vbox-install.log I noticed a lot of warnings and errors:

Code: Select all

VirtualBox 5.1.22 r115126 installer, built 2017-04-28T15:37:00Z.

Testing system setup...
Installing VirtualBox to /opt/VirtualBox

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
cp: preserving permissions for ‘/tmp/vbox.0/VBox’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/common/log’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/common/misc’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/common/err’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/common/alloc’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/common/table’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/common/time’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/common/checksum’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/common/string’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/common’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/generic’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/include/internal’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/include/iprt/nocrt’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/include/iprt’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/include/VBox/vmm’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/include/VBox’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/include’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/linux’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/math/gcc’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/math’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/r0drv/generic’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/r0drv/linux’: Invalid argument
cp: preserving permissions for ‘/tmp/vbox.0/r0drv’: Invalid argument
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/4.9.0-porteus/build -j4 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
echo >&2;							\
echo >&2 "  ERROR: Kernel configuration is invalid.";		\
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";	\
echo >&2 ;							\
/bin/false)

[cutting the middle of the log because it's too big for this post]

vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
Installation successful

Re: Virtual Box

Posted: 13 Jun 2017, 22:48
by beny
we have had a tread with the virtualbox permission issue with guest account due seem with the build as root but guest do not have the same permission so virtualbox fail to start if this is the problem try this:

Re: Virtualbox and Windows 7
found the trick to run virtualbox on copy2ram guest account look if work for you:
chmod 4711 /opt/virtualbox/virtualbox
btw can be not this the problems,but you can try the change of...

Re: Virtual Box

Posted: 14 Jun 2017, 03:29
by fulalas
@beny, thanks! I fixed it by executing these 2 commands in sequence:

sudo chown root:root /opt/VirtualBox/VirtualBox
sudo chmod 4511 /opt/VirtualBox/VirtualBox

I think brokenman should do that in his Vbox builder script in order to fix the problem.

Re: Virtual Box

Posted: 14 Jun 2017, 05:29
by Ed_P
Is there a command or script that allows someone to know what kernel a particular VirtualBox module is designed to run with?

Re: Virtual Box

Posted: 14 Jun 2017, 07:02
by fulalas
If the module was created by Porteus Vbox builder, you can extract the module and check the name of the subfolder inside /lib/modules.

Re: Virtual Box

Posted: 14 Jun 2017, 11:10
by raja
Thanks,Shall try this week end.

Re: Virtual Box

Posted: 14 Jun 2017, 13:57
by Ed_P
fulalas wrote:check the name of the subfolder inside /lib/modules.
:good: Perfect. Thank you. :beer:

Re: Virtual Box

Posted: 14 Jun 2017, 14:17
by donald
fulalas wrote: @donald, could you help us explaining how exactly you're building with Vbox builder?
To be honest,i haven't done anything uncommon.

Booted stock porteus (xfce x86_64 kernel 4.9) with the devel and crippled-sources
module already in the modules folder, nothing else, no python, into guest account.

Ran v-box builder > activated the v-box xzm and voila..v-box did start..

Re: Virtual Box

Posted: 25 Jun 2017, 12:15
by brokenman
I think brokenman should do that in his Vbox builder script in order to fix the problem.
Done

Re: Virtual Box

Posted: 25 Jun 2017, 15:14
by fulalas
brokenman wrote:
I think brokenman should do that in his Vbox builder script in order to fix the problem.
Done
Great! :good:
All times are UTC
Page 1 of 1
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/