You are not logged in.
good question
but not to me :-)
Zygfryd Homonto
Offline
Why? Any reason?
They don't want to give that technology away ?
I mean, you can USE it for free, but you just can't see how it's implemented.
The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...
Offline
This topic seems to be going off track
I have updated and although it starts VM will not it gives the error others are getting
If you need more info just say I'll open a terminal 0_0
MrG
Mr Green
Offline
Same here: VBox only finds vboxdrv when I run it with root.
Offline
VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root.
VBox status code: -4 (VERR_INVALID_HANDLE).Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
Same issue here..
There's no console output, but it seems to run as root.
Here's the permissions
$ ls -l /dev/vboxdrv
crw-rw---- 1 root vboxusers 10, 60 2008-09-22 08:51 /dev/vboxdrv
I am in the vboxusers group as always
$ groups
tty disk lp wheel uucp log dbus hal video audio optical floppy storage scanner camera users vboxusers
lsmod shows vboxdrv is loaded but still the issue persists.
Offline
dninja wrote:Why? Any reason?
They don't want to give that technology away ?
I mean, you can USE it for free, but you just can't see how it's implemented.
In fact, there is propietary code there, I suppose it isn't cheap.
Offline
Assuming the kernel module has changed, have you rebooted or manually removing the kernel module and then restarting it?
It works fine for me when running as root just not as a normal user so I assume that the --disable-hardening wasn't included in the build
This flag was included in the 2.0.2-2 release, but it solved the permissions problems only (check abs). For me, it solved two problems that i had on 2.0.2-1, but a new one appeared.
I'll try to help on finding the cause of the problem tonight, but after all, it isn't bad living a few days without Windows
Offline
I'm also getting the same error as flateric mentioned above after updating to virtualbox-ose 2.0.2-2. I think the matching kernel modules are not in the repositories as yet coz I can see the modules as virtualbox-modules-2.0.2-1. Any thoughts ?
Cheers,
Jayanath
"There is LIFE beyond the 8x8 cubicle"
Offline
maybe .... I can run it using sudo.... so could be a permissions problem
Mr Green
Offline
maybe .... I can run it using sudo.... so could be a permissions problem
How did it go?
I recompiled the kernel module from abs (community/modules/virtualbox-modules) but it happens the same...
Offline
Same error as flateric:
Offline
This has been filed as a major defect here. http://www.virtualbox.org/timeline?daysback=15
Check the defect #2305.
Last edited by jayanath (2008-09-22 17:57:30)
Cheers,
Jayanath
"There is LIFE beyond the 8x8 cubicle"
Offline
It's definitely some sort of permissions problem. Virtualbox can run just fine under root or sudo, but not under normal user. It is NOT a kernel module issue, otherwise root wouldn't work at all either.
Last edited by longhornxtreme (2008-09-24 05:25:34)
Offline
Is it the device permission? /dev/vboxdrv
Mr Green
Offline
Shouldn't the versions of modules and virtualbox match?
sudo pacman -Rs virtualbox-ose
checking dependencies...
Remove (4): virtualbox-ose-2.0.2-2 xalan-c-1.10-2 xerces-c-2.8.0-1
virtualbox-modules-2.0.2-1
Total Removed Size: 33.68 MB
Offline
They do match, they're the same version.
The packager just fixed some of his packaging errors for the VirtualBox package...right ?
The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...
Offline
Hi.
Did you try this? At least it worked for me...
The first you have to know is how to compile from ABS... check that community is enabled in /etc/abs.conf, then (as root) execute the 'abs' command and go to /var/abs/community/modules/virtualbox-modules . Then do:
1. Add the --disable-hardening flag in virtualbox-modules PKGBUILD (in the build() function it sould be something like this: ./configure --with-qt-dir=/opt/qt --with-gcc=/usr/bin/gcc-3.4 --with-g++=/usr/bin/g++-3.4 --disable-hardening
2. makepkg --nobuild --asroot
3. Remove the flag -DVBOX_WITH_HARDENING from the variable KFLAGS in
/var/abs/community/modules/virtualbox-modules/src/VirtualBox-2.0.2/src/VBox/HostDrivers/Support/linux/Makefile
4. makepkg --noextract -i --asroot
5. Reload the module (modprobe -vr vboxdrv && modprobe -v vboxdrv).
6. chmod 666 /dev/vboxdrv.
It should work, please tell me if it does.
Offline
Nice going, it works! Thanks for the tip!
Could somebody please update the official virtualbox-modules PKGBUILD?
Last edited by schuay (2008-09-24 16:07:57)
Offline
Just use the virtualbox in the archlinuxfr repo until the Arch devs get their ducks in a row on this.
Res Publica Non Dominetur
Laptop: Arch x86 | Thinkpad X220 | Core i5 2410-M | 8 GB DDR3 | Sandy Bridge
Desktop: Arch x86_64 | Custom | Core i7 920 | 6 GB DDR3 | GeForce 260 GTX
Offline
Just use the virtualbox in the archlinuxfr repo until the Arch devs get their ducks in a row on this.
But I don't wanna!
I'll just be lazy and wait for the maintainers to fix this. Do we know if a bug has been filed on Arch?
Offline
georgia_tech_swagger wrote:Just use the virtualbox in the archlinuxfr repo until the Arch devs get their ducks in a row on this.
But I don't wanna!
I'll just be lazy and wait for the maintainers to fix this. Do we know if a bug has been filed on Arch?
I've just added a link about this forum thread on the following bug:
http://bugs.archlinux.org/task/11528
Offline
==> Missing Dependencies:
-> dev86
-> iasl
-> pulseaudio
-> gcc34
==> ERROR: Could not resolve all dependencies.
==> WARNING: Integrity checks (md5) are missing or incomplete.
==> Extracting Sources...
==> ERROR: Unable to find source file VirtualBox-2.0.2-OSE.tar.bz2 for extraction.
Aborting...
Tried above but all I get are errors, not sure I like makepkg as root?
downloading this each time
VirtualBox-2.0.2-OSE.tar.bz2\?e\=1222321606\&h\=3b0e41b1867a9401fd19408b8423cdab
Grrrrr!!!!!! lol
MrG
Last edited by Mr Green (2008-09-25 05:46:20)
Mr Green
Offline
==> Missing Dependencies: -> dev86 -> iasl -> pulseaudio -> gcc34 ==> ERROR: Could not resolve all dependencies.
==> WARNING: Integrity checks (md5) are missing or incomplete. ==> Extracting Sources... ==> ERROR: Unable to find source file VirtualBox-2.0.2-OSE.tar.bz2 for extraction. Aborting...
Tried above but all I get are errors, not sure I like makepkg as root?
downloading this each time
VirtualBox-2.0.2-OSE.tar.bz2\?e\=1222321606\&h\=3b0e41b1867a9401fd19408b8423cdab
Grrrrr!!!!!! lol
MrG
Well, first do:
pacman -Sy dev86 iasl pulseaudio gcc34
Then, in /var/abs/community/modules/virtualbox-modules
mv VirtualBox-2.0.2-OSE.tar.bz2\?e\=1222321606\&h\=3b0e41b1867a9401fd19408b8423cdab VirtualBox-2.0.2-OSE.tar.bz2
And you're ready to continue
Offline
He not tell me that lol...... sure loaded extra deps..... thanks :-)
All working here now
Last edited by Mr Green (2008-09-25 13:20:27)
Mr Green
Offline