FS#12877 - Virtualbox is outdated and blocks upgrade to kernel 2.6.28 (patch included)
Attached to Project:
Community Packages
Opened by Jakob Gruber (schuay) - Wednesday, 21 January 2009, 14:19 GMT
Last edited by Geoffroy Carrier (gcarrier) - Friday, 23 January 2009, 17:57 GMT
Opened by Jakob Gruber (schuay) - Wednesday, 21 January 2009, 14:19 GMT
Last edited by Geoffroy Carrier (gcarrier) - Friday, 23 January 2009, 17:57 GMT
|
Details
Description:
virtualbox-ose is still stuck at 2.0.4 and since it requires kernel26<2.6.28 it blocks updates to the newest kernel. a patch is included for both PKGBUILDs (update to 2.1.0, kernel 2.6.28 supported). also, there's still a warning at compile time "hardening is disabled, you shouldn't build vbox for distributions without hardening". can we fix this somehow without breaking vbox again? Additional info: * package version(s) virtualbox-ose 2.0.4 virtualbox-modules 2.0.4 * config and/or log files etc. Steps to reproduce: |
This task depends upon
First, "_OSE" was appended to toplevel directory's name. When the references on PKGBUILD file are updated the building process starts correctly.
Although, there are some error messages when installing package was created.
--------
install: no se puede efectuar `stat' sobre «../obj/src/VBox/VMM/tstVMM/tstVMM»: No existe el fichero o el directorio
install: no se puede efectuar `stat' sobre «vditool»: No existe el fichero o el directorio
install: no se puede efectuar `stat' sobre «/home/diego/archpkgs/virtualbox-ose/src/VirtualBox-2.1.2_OSE/src/VBox/Installer/linux/VBoxAddIF.sh»: No existe el fichero o el directorio
--------
After installing module looks to be loading correctly. dmesg reports the following lines:
--------
vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: Found 1 processor cores.
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 2.1.2_OSE (interface 0x000a0009).
--------
However, when a virtual machine is started the driver can't be opened. The following error popups
--------
VirtualBox kernel driver is not accessible, permission problem. If you have built VirtualBox yourself, make sure that you do not have the vboxdrv kernel module from a different build or installation loaded. Also, make sure the vboxdrv udev rule gives you the permission you need to access the device. (VERR_VM_DRIVER_NOT_ACCESSIBLE).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {e3c6d4a1-a935-47ca-b16d-f9e9c496e53e}
--------
Ups. My fault. vboxusers group membership was not granted. Besides the missing files, it looks good now.