Virtualbox and Windows 7

[beny]

ok i try in the same way and report i don't know if i can load all the modules in ram i have also the multilib 500 modules+-

[beny]

i have build virtualbox in my guest account with changes and it work with guest account, in copy2ram i have this:
guest@porteus:~$ virtualbox
VirtualBox: Error -10 in SUPR3HardenedMain!
VirtualBox: Effective UID is not root (euid=1000 egid=100 uid=1000 gid=100)
do not work but if i do this:
guest@porteus:~$ su
Password:
root@porteus:/home/guest# virtualbox
Qt WARNING: Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
but virtualbox start without problems

[beny]

found the trick to run virtualbox on copy2ram guest account look if work for you:
chmod 4711 /opt/virtualbox/virtualbox
bogomips there is another user that have this issue can try the same?

[fred08155]

So something seems to miss in the module made by vbox builder?
Aaaah, wrong rights assigned? Or what does the chmod do?

If you like you can test extension pack config.
There are two versions. One version with extension pack installed as guest and root, other version only installed as root.

I uploaded relevant modules here
http://filehorst.de/folder.php?key=b3pZvdP0
I guess virtualbox also needs python 2.7 since i had it installed before using vbox builder. You can download python 2.7 through USM.

[beny]

hi you have all the hardware connected to the system i have printer, usb sat decoder, sd reader, dvd reader, mouse usb internet shared folder...

[fred08155]

found the trick to run virtualbox on copy2ram guest account look if work for you:
chmod 4711 /opt/virtualbox/virtualbox

Sorry, didn´t work. Now i cannot start virtualbox as guest AND as root. Same error message as before.

VirtualBox: Error -10 in SUPR3HardenedMain!
VirtualBox: Effective UID is not root (euid=1000 egid=100 uid=1000 gid=100)

VirtualBox: Tip! It may help to reinstall VirtualBox.

Can you please upload your module somewhere? Maybe yours is working.

[beny]

hi with copy2ram every change you do at reboot is lost so you have to redo this:
guest@porteus:~$ su
Password:
root@porteus:/home/guest# chmod 4711 /opt/VirtualBox/VirtualBox
guest@porteus:~$ virtualbox
and work,you have to try to fix the permission in hardcoded way, isn't my module good or bad, or brokenman have to tweak the vbox builder for the user right permission

[fred08155]

I know that changes are lost after reboot. This is why i included your modification into my virtualbox xzm module (extract module, chmod 4711 on sub directory path, dir2xzm and reboot with new module).
Still no success. I even had the mod redone after booting the new module. Same error message again.

Found something googling about the issue. But this needs to be done during compiling virtualbox...

I needed to configure with the switch --disable-hardening

[beny]

hi i have found this line in slackbuild of virtualbox:

# Enable Hardening - Defaulting to yes as requested by upstream
if [ "${HARDENING:-yes}" = "yes" ]; then
harden="--enable-hardening"
else
harden="--disable-hardening"
fi
but we have a brokenman's script for the build,and i think he can answer for the permission issue.

[fred08155]

After further googling i found the solution.
I rebuild virtualbox with vbox builder. Didn´t change anything on the situation...

After some research i tried this with success.

First

Code: Select all

sudo usermod -a -G vboxusers guest

Then

Code: Select all

chmod 4711 /opt/VirtualBox/VirtualBox

Now i just need to pack the addition of guest to the vboxusers group into a xzm module.

I hope that´s all.

[fred08155]

Hmmm... seems to be more complicated than i thought.
I saved usermod changes successfully to a xzm module. But i cannot save chmod 4711 changes. changes-time script does not detect this change. Manually created module seems to get ignored somehow.
Is there a way to edit this into the virtualbox module? Or merge it in from my selfmade module?

[francois]

Try to put a z in front of the name of your manually changed module so that it gets loaded last. Virtualbox has a v and might erase the effect of your module.