Hi!
I (and some people too) have been experiencing problems with virtualbox-ose since it was upgraded to version 2.0.2.
The problems are described here:
http://bugs.archlinux.org/task/11528?project=5
and here:
http://bbs.archlinux.org/viewtopic.php?id=55406&p=1
There is a workaround for this problem (I have not tried it), but does anybody know when will this be solved in the repos?
Thank you!
On Sun, Sep 21, 2008 at 23:15, Jaime Oyarzun Knittel joyarzun@alumnos.inf.utfsm.cl wrote:
There is a workaround for this problem (I have not tried it), but does anybody know when will this be solved in the repos?
When I find the solution. There has been a communication issue between bash and I, so I didn't try his PKGBUILD. Now I have a new problem to solve, after a correction between 2.0.2-1 and 2.0.2-2. I submitted it to get more feedback, as I don't know exactly what's going on now.
On Mon, Sep 22, 2008 at 15:52, Geoffroy Carrier geoffroy.carrier@koon.fr wrote:
Now I have a new problem to solve, after a correction between 2.0.2-1 and 2.0.2-2. I submitted it to get more feedback, as I don't know exactly what's going on now.
To be more precise: it now works running as 'root' without any libs problem. But it doesn't work as a user, failing to find /dev/vboxdrv.
if you are compiling it yourself, just add the --disable-hardening flag.
daniel
On Mon, 2008-09-22 at 15:54 +0200, Geoffroy Carrier wrote:
On Mon, Sep 22, 2008 at 15:52, Geoffroy Carrier geoffroy.carrier@koon.fr wrote:
Now I have a new problem to solve, after a correction between 2.0.2-1 and 2.0.2-2. I submitted it to get more feedback, as I don't know exactly what's going on now.
To be more precise: it now works running as 'root' without any libs problem. But it doesn't work as a user, failing to find /dev/vboxdrv.
On Mon, Sep 22, 2008 at 16:23, daniel g. siegel dgsiegel@gmail.com wrote:
if you are compiling it yourself, just add the --disable-hardening flag.
Already done.
daniel g. siegel wrote:
if you are compiling it yourself, just add the --disable-hardening flag.
daniel
That solved the permissions issue, but it still can't find /dev/vboxdrv.
This was reported in http://www.virtualbox.org/ticket/2305.
On Tue, Sep 23, 2008 at 12:52 AM, Jaime Oyarzun Knittel joyarzun@alumnos.inf.utfsm.cl wrote:
That solved the permissions issue, but it still can't find /dev/vboxdrv.
On my machine taht device is correctly created after inserting the vboxdrv module.
Corrado
On Tue, Sep 23, 2008 at 09:26, bardo ilbardo@gmail.com wrote:
On my machine taht device is correctly created after inserting the vboxdrv module.
Are you running virtualbox as root? Because that's the only way it works here.
You need the module and adding the user to the group virtualbox.
2008/9/23 Geoffroy Carrier geoffroy.carrier@koon.fr:
On Tue, Sep 23, 2008 at 09:26, bardo ilbardo@gmail.com wrote:
On my machine taht device is correctly created after inserting the vboxdrv module.
Are you running virtualbox as root? Because that's the only way it works here.
-- Geoffroy Carrier
Svein Tonning wrote:
You need the module and adding the user to the group virtualbox.
That's really obvious. In virtualbox *ose* thinks aren't working, however I think I solved it, I'll check it during the morning.
Jaime Oyarzun Knittel ha scritto:
Svein Tonning wrote:
You need the module and adding the user to the group virtualbox.
That's really obvious. In virtualbox *ose* thinks aren't working,
<snip> You meant *things* ;)
however I think I solved it, I'll check it during the morning.
Let us know if you solved it ;)
Ángel Velásquez wrote:
Jaime Oyarzun Knittel ha scritto:
[...]
That's really obvious. In virtualbox *ose* thinks aren't working,
<snip> You meant *things* ;)
Haha, can't get used to this language yet :)
however I think I solved it, I'll check it during the morning.
Let us know if you solved it ;)
Well, I had to rebuild the package virtualbox-modules from ABS.
What I did was:
1. Add the --disable-hardening flag in virtualbox-modules PKGBUILD.
2. makepkg --nobuild
3. Remove the flag -DVBOX_WITH_HARDENING from the variable KFLAGS in virtualbox-modules/src/VirtualBox-2.0.2/src/VBox/HostDrivers/Support/linux/Makefile
4. makepkg --noextract -i
5. Reload the module (modprobe -vr vboxdrv && modprobe -v vboxdrv).
6. chmod 666 /dev/vboxdrv.
The last step is a bit ugly, but works. I don't know why am I not allowed to use /dev/vboxdrv with 660 persmissions, even if I belong to the vboxusers group.
I hope it works, please tell :)
arch-general@lists.archlinux.org