Fedora Installation :: F11 - VirtualBox And Kernel Compilation
Sep 13, 2009
I'm trying to get a fedora guest running reliable smp under VirtualBox 3.0.6. The VirtualBox manual says "Some Linux distributions, for example Fedora, ship a Linux kernel configured for a timer frequency of 1000Hz. We recommend to recompile the guest kernel and to select a timer frequency of 100Hz." So I tried recompiling the kernel. Being a responsible lad, when it came to setting the kernel specs:
Code:
# Polite request for people who spin their own kernel rpms:
# please modify the "buildid" define in a way that identifies
# that the kernel isn't the stock distribution kernel, for example,
# by setting the define to ".local" or ".bz123456"
#
# % define buildid .local
%define buildid .rim_for_vbox
I've successfully built and installed kernel, headers and firmware:kernel-2.6.30.5-43.rim_for_vbox.fc11.x86_64.rpm
kernel-firmware-2.6.30.5-43.rim_for_vbox.fc11.x86_64.rpm
kernel-headers-2.6.30.5-43.rim_for_vbox.fc11.x86_64.rpm
The system is working fine (well, so far). But trying to install the VirtualBox Guest Additions kernel add-ons still gives me
Please install the build and header files for your current Linux kernel. The current kernel version is 2.6.30.5-43.rim_for_vbox.fc11.x86_64. I'm pretty sure this is because my kernel doesn't match the development packagekernel-devel-2.6.30.5-43.fc11 (x86_64). So the key question is, how on Earth do I create a development package to match the responsibly-renamed kernel?
I'm trying to get Virtualbox up an running. So I have added virtualbox in my repo and added the key, looks fine so far. but afeter downloading I get this:
VirtualBox-3.0.8_53138_rhel5-1.x86_64 Creating group 'vboxusers'. VM users must be member of that group! No precompiled module for this kernel found -- trying to build one. Messages emitted during module compilation will be logged to /var/log/vbox-install.log.
Compilation of the kernel module FAILED! VirtualBox will not start until this problem is fixed. Please consult /var/log/vbox-install.log to find out why the kernel module does not compile. Most probably the kernel sources are not found. Install them and execute /etc/init.d/vboxdrv setup as root.
Trying to install virtualbox in F12 but fails when recompiling kernel module. Output of vbox-install log is:
Attempting to install using DKMS removing old DKMS module vboxdrv version 3.1.6 Deleting module version: 3.1.6 completely from the DKMS tree. Creating symlink /var/lib/dkms/vboxdrv/3.1.6/source -> /usr/src/vboxdrv-3.1.6
DKMS: add Completed.
Error! Your kernel source for kernel 2.6.32.11-99.fc12.i686.PAE cannot be found at /lib/modules/2.6.32.11-99.fc12.i686.PAE/build or /lib/modules/2.6.32.11-99.fc12. code....
I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
[code]...
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/2.6.37.1-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
my error when trying to run a VB (Virtualbox). Error as copied from error box. install the virtualbox-ose-modules package for your kernel and execute 'modprobe vboxdrv' as root. VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).
[code]...
I get this when trying to launch a VB after making one with wizzard.
Just I compiled Kernel xxx.3.6 in ubuntu in Virtual Machine for 32 bit. However, I wanted to do it for 64 bit, I dont know what parameter is necessary for 64 bit.
I wanted to try VirtualBox so I did: Code: yum install vboxgtk
In the list of dependencies I found that it needs to download kernel. I was just curious to know that why can't it manage with the PAE kernel. It requires the kernel 2.6.31.12-174.2.3.fc12 whereas I've got its PAE version working right now. Can someone please explain why is it so?
When I install the latest F12 kernel, my F12 installation freezes immediately on boot. The previous kernel booted fine. It's a little strange, because if I edit the grub.conf to use the old kernel, the freeze still occurs.Is anyone getting Kernel 2.6.31.12-174.2.22 to work in virtualbox? (both yes and no answers would be useful here)Does anyone have any idea of the cause (and especially, why updating the kernel would cause the _old_ kernel to freeze as well)
Why it asking me for options to be selected while I run: Code: make oldconfig.I am in verse to compile latest reased kernel 2.6.34-rc5 on Ubuntu 9.10?what i did is Just pressed "Enter" key ( i think it will dsiable everything?Not sure) and created a .config file.
How can I use DKMS to force the virtualbox setup to run using the correct kernel sources? This is the error I'm getting in the vbox logs
Code: Attempting to install using DKMS removing old DKMS module vboxdrv version 3.1.2 Deleting module version: 3.1.2 completely from the DKMS tree. Done.
Error! Your kernel source for kernel 2.6.31.6-166.fc12.x86_64 cannot be found at /lib/modules/2.6.31.6-166.fc12.x86_64/build or /lib/modules/2.6.31.6-166.fc12.x86_64/source. You can use the --kernelsourcedir option to tell DKMS where it's located.
Failed to install using DKMS, attempting to install without: Makefile:152: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
I have downloaded latest version of sun vm virtual box foe Fedora 13 x64. After installing and creating a VM when I want to start vm I got this error. And when I enter this command on terminal : /etc/init.d/vboxdrv setup
I get this error: Code: [root@localhost arash]# /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module [ OK ] Recompiling VirtualBox kernel module [FAILED] (Look at /var/log/vbox-install.log to find out what went wrong) Log file:
Code: [root@localhost arash]# cat /var/log/vbox-install.log Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop. [root@localhost arash]#
I tried to install the new Vbox 3.2.6 through rpm as a guide told me but I first had errors with the older vbox dependencies, so I uninstalled vbox 3.1.8.2 and now I am with a vbox period. Is there something I can do to fix this I tried this tutorial didn't work for me [URL] and another on the fedora forum (lost the history). error I get is Recompiling VirtualBox kernel module [FAILED] and Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing.
I am new to fedora core and needs desperate help.Now what i can notice is the kernel files doesnot match. will this makes a difference..what do you think ? How can i make the VirtualBox kernel module status [OK] ?
I've been reading about a temporary solution to the kernel/Fglrx issue caused by the last kernel update, but I haven't read about any permanent solution to this issue. Anyone know anything about a permanent solution (new kernel update?, new Fglrx driver?) to this compilation error?
enabling parallel compilation of kernel source.I've read that setting the CONCURRENCY_LEVEL environment variable should do that. The problem is that I see only one instance of a running gcc in top, notwithstanding I have set "export CONCURRENCY_LEVEL=5".
I upgraded to Lucid last night, and I'm getting this error when I try to run virtualbox-ose:
Quote: Kernel driver not installed (rc=-190 Please install the virtualbox-ose-dkms package and execute 'modprobe vboxdrv' as root. I try it, then I get: Quote: modprobe vboxdrv FATAL: Module vboxdrv not found.
I have no idea what's going on. Can anyone help? The version of virtualbox is 3.1.6-dfsg-2ubuntu2
After updating to kernel-2.6.33.6-147.fc13.x86_64 (and updating all kmods) VirtualBox guests no longer boot.
I had a Windows guest (from now on refereed as Crapdows) that worked normally. After the update, I could get to the "Start Windows Normally" screen, but then Crapdows refused to boot. At first, I thought it was a crappy M$ bug, but after creating another VM (Doublecrap), and starting from scratch, I was able to get to the "Windows is loading files" screen, and then the guest hangs again. This problem is generalized to all OS'es I've tried. In Ubuntu, I can get to the language selection screen before the installation freezes. The same applies for Fedora and SUSE guests.
I generally check what updates are being installed. This time sadly I didn't and again this kernel had one missing module. VirtualBox-OSE stopped working. It had been working fine with other upgrades. No it's not a problem with dkms or other stuff. This kernel doesn't have vboxdrv module like other kernels...i verified it...
[Code]...
The 2.6.38.8 version doesn't have vboxdrv module!....hence again I have to roll back to older kernel. So before blindly upgrading....read this message!
I had no problems up to the newest kernel version. But for 2.6.40-4 akmods fails to build the kmod with the following error:
Code: Building RPM using the command '/usr/bin/akmodsbuild --target x86_64 --kernels 2.6.40-4.fc15.x86_64 /usr/src/akmods/VirtualBox-OSE-kmod.latest' Building modules, stage 2. MODPOST 1 modules CC /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40-4.fc15.x86_64/vboxnetflt/vboxnetflt.mod.o LD [M] /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40- [Code]...
I'm simply trying to compile a vanilla kernel from Kernel.org, I've done it before, however "make menuconfig" returns an error after I've made my changes to the config file.
Code:
Why is make returning that error? I am using a 64-bit kernel.
I'm just installed OpenSuse 11.3 (64) on a 30gb SSD, hoping to get virtualbox 4.0 running to virtualize an instance of Windows 7.I went through some pain with my Nvidia video card and actually getting vb to install, but through lots of searching and tinkering got here.I created a vm in the vb control panel, but when I go to start it I get:
Code: Failed to open a session for the virtual machine Win7Main. The virtual machine 'Win7Main' has terminated unexpectedly during startup with exit code 1.
I'm running Virtualbox from the Sun website (need the USB support) and it breaks after each kernel update.The problem is that I installed a lot of Ubuntu systems for transitioning windows users with Windows in virtualbox to ease the migration but I have to rerun vboxdrv setup after each kernel patch.
I opted to install my Linux Fedora distribution, in a SUN VM (Virtualbox). [URL] I have 2 questions:
My current max res available to select is 1024x768. Can I run at 1920x1200? My display indicated that it is 'Unknown'. I don't know if that is in on the deal, or not...
Second question: When installing VBOXADDITIONS_3.1.2_56127, I am getting the error: Building the VirtualBox Guest Additions kernel modules [FAILED]
If I am displaying the log correctly, it indicates: Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop Pictures are located here, in the EVGA Linux forum: [URL] I am new to both Linux, and Fedora.
My mission statement: To run Linux using the Fedora distribution, in a VM window under Windows 7 64bit Ultimate, with the ability for scripting using Bash, with the Perl programming language installed, and use Apache Tomcat to monitor both apps, and various VM installs, on numerous Servers via the internet.
