Fedora :: VirtualBox Not Opening With New Kernel Version
Aug 6, 2011with the new kernel update, my virtualbox won't open. Something about installing DKMS something first. Where would I find this to install?
View 3 Replieswith the new kernel update, my virtualbox won't open. Something about installing DKMS something first. Where would I find this to install?
View 3 RepliesI have a fedora 11 with kernel package: kernel-PAE-2.6.29.6-217.2.3.fc11.i686
I would like to install the devel package for this kernel version, but I can't find it, because in the fedora repo there is only the original kernel (2.6.29.4....) and in the updates repo there is only the newest kernel package (2.6.30....)
Where can I find the packages which are between the fedora and update repos' versions?
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?
I have a server running Reh Hat Linux 7.3 with kernel 2.4.18. Can i upgrade kernel to version 2.6 and glibc to version 2.5?
View 6 Replies View Relatedmy 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.
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)
View 14 Replies View RelatedI'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?
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.
Creating symlink /var/lib/dkms/vboxdrv/3.1.2/source ->
/usr/src/vboxdrv-3.1.2
DKMS: add Completed.
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.
Code:
[root@nevada Downloads]# uname -r
2.6.31.6-166.fc12.x86_64
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.
View 5 Replies View RelatedI 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] ?
View 5 Replies View RelatedAfter 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.
Is it time to get my hammer?
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 using this guide videos - howto: debian linux kernel compilation, part 1 and the author says i need kernel 2.6.26 this version of kernel doesnt longer exist in kernel.org website and the only 2.6.26 i found is a patch here. should i use the patch? or download another version of kernel?
View 2 Replies View RelatedI'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.
[code]....
I installed openSUSE 11.2 on virtualbox. My host is windows 7. I tried to install the guest additions, but i get an error saying
Code:
Building VirtualBox Guest Additions Kernel Modules...Failed
(Your system does not seem to be set up to build kernel modules)
How should i go about to let my system build kernel modules?
When I installed fedora 11 the other day using the live CD it installed the i586 kernel and not the i686, despite the fact that smolt seems to know that that the hardware is i686 (well, actually it's x86, but I'm not going to argue because I forgot to get that one...). Why would it install the i586 one though? (uname -r 2.6.29.6-213.fc11.i586) But more importantly, are there any specific issues which this version can cause that I should be aware of? I can't really be bothered to change it at the moment if there is no real issue with it but I'm not too sure what difference it makes? Is it slower? It seems to know that I have a quad-core processor and seems to use them fine.
View 10 Replies View RelatedI'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.
View 2 Replies View RelatedI 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.
I'm using F11 and I've downloaded and installed kernel 2.6.30.4-25.fc11.x86_64 from koji.
Since I'm dumb.... I've installed with rpm -Uvh kernel* so now I've loose the latest stable fedora kernel...
I've tried to manually download kernel but when I try to install it complains because it's older then the current installed.
How can I restore to kernel 2.6.29?
Which is the current stable version of kernel in fedora 10 and how can I installed because right now I have unstable kernel:
uname -a
Linux blind 2.6.29.3-60.fc10.x86_64 #1 SMP Sat May 9 04:18:14 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
I just want to get back to latest stable kernel of fedora 10. I'm not able from the grub to choose an older because there are only kernels for fedora 9. The problem was that previously I used fedora 9 however I upgrade it but it was still with kernel of fedora 9 so I pick it the unstable of fedora 10 and I installed it. Right now I just want to get back to current version of kernel in fedora 10 so I can upgrade it to fedora 11.
I am relatively new to the Linux System (8 months). I am having issues after upgrading the Scientific Linux 6 kernel from its current 2.6.x version to the latest version that SL6 has available. The issue is that once I install the upgrade and reboot, the internet becomes extremely laggy when scrolling on web pages, so much so that you get a ripple like effect as your scrolling. Which doesn't occur in the current kernel i am using.
Current Kernel is: 2.6.32-71.18.2.el6
New Kernel RPM update is: 2.6.32-71.29.1.el6
I wish I could figure out the problem but I am having trouble identifying what exactly the current kernel has that the new one doesn't that would cause the internet lag. I have read other topics with similar kernel update problems, but none have expressed an internet problem & only an internet problem from a kernel update.
What happens if you get an update for an older version kernel when you are using a new version?
View 3 Replies View Relatedi am using Fedora 14. Once system get hanged during opening a video file so I had to restart the system by pressing restart button. But after restarting there are few problems appearing like system monitor not opening and Thunder bird opening but not showing any folder including inbox.
---------- Post added at 04:54 AM GMT ---------- Previous post was at 04:42 AM GMT ----------
Looks like SElinux has stopped working
After new kernel update I noticed that I have 2 different versions of 1 kernel installed.
Kernels are:
2.6.30.5-43.fc11.i686.PAE (this one I use because previous kernels are all .PAE)
and
2.6.30.5-43.fc11.i586
Should I now expect any problems with later kernel releases or can I leave it this way? I boot in the .PAE kernel.
I'm building a Kernel on System A to use on System B. I've followed the walkthrough on [URL], and I get the following rpms:
kernel-debuginfo-common-i686-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-firmware-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAE-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAEdebug-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAEdebug-debuginfo-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAEdebug-devel-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAE-debuginfo-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
kernel-PAE-devel-2.6.30.8-64.hymerfania_dbg.fc11.i686.rpm
What I don't get are any
kernel-headers-<version>.<arch>.rpm
Files. Don't I need them to rebuild modules and drivers on System B? Otherwise, how should I copy my new headers to System B? BTW, System B crashes when I try to build the Kernel on it, that's why I'm building debugger Kernels on System A.
Where are the kernel headers for the current kernel of F12KDE? I am trying to configure VMWare player on my machine, and on initial startup I got an error message.
View 3 Replies View Related