Fedora :: Is Anyone Getting Kernel 2.6.31.12-174.2.22 To Work In Virtualbox?
Mar 2, 2010
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
ADVERTISEMENT
Apr 21, 2010
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....
View 6 Replies
View Related
Mar 23, 2011
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?
View 5 Replies
View Related
Apr 27, 2010
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.
View 6 Replies
View Related
Jan 22, 2010
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?
View 2 Replies
View Related
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?
View 4 Replies
View Related
Aug 6, 2011
with the new kernel update, my virtualbox won't open. Something about installing DKMS something first. Where would I find this to install?
View 3 Replies
View Related
Dec 28, 2009
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
View 8 Replies
View Related
Jun 13, 2010
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]#
View 13 Replies
View Related
Jul 27, 2010
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 Related
Sep 26, 2010
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] ?
View 5 Replies
View Related
Aug 7, 2010
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.
Is it time to get my hammer?
View 4 Replies
View Related
Jun 16, 2011
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!
View 10 Replies
View Related
Aug 2, 2011
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]...
View 13 Replies
View Related
Oct 15, 2009
I've got a problem with getting my VPN connection from my virtual machine working (a XP64 running in VirtualBox). I really need to get it working so that I can nuke my windows partition, and because I would like run linux programs while using my XP VPN connection (as I need to run some XP programs at school). I've found this manual on how to do it on Ubuntu, but I am doubt about how to translate it to Fedora (and I really prefer Fedora). [URL]
View 6 Replies
View Related
Apr 24, 2011
I am doing a project for school to set up a Linux network in virtual-box. I have very little Linux experience and am struggling to make anything work. I am trying to get webmin to work but it won't connect. I followed the install instructions perfectly and everything seemed to work fine. I've opened any ports that it said to open. but I still can't get it to connect. When I enter https://myservername:10000/ it just try to load until it times out. When I try to ping that address it says not valid network address. I'm at a loss and this is due in a few days.
View 3 Replies
View Related
Sep 19, 2009
My USB-modem and my freerunner phone is no longer recognized by fedora. Last time this happened I just reinstalld Fedora because I had no id�a what caused the problem. But now I recognized that virtualbox was the last package I installed before the problem occured.
I tried to uninstall virutalbox but the problem remained. Is there a way to reset all the network settings without reinstalling fedora?
View 3 Replies
View Related
Jun 9, 2010
I have ubuntu 9.10 and want to give fedora a go through Live usb but how? I my cd dvd drive does not work and my virtualbox is not taking my usb pendrive.
View 2 Replies
View Related
Jun 12, 2009
there is an issue with the way the Linux Kernel addresses memory by default and the graphic drivers for my Asus G1Sn. I have a patch that I had compiled against a custom kernel for 2.6.27.xx how ever it does not work with the latest kernel in Fedora 11. It is beyond me to rewrite the patch to work with a different kernel.
View 1 Replies
View Related
Jan 2, 2011
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.
[code]....
View 9 Replies
View Related
Feb 10, 2010
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?
View 7 Replies
View Related
Jan 6, 2010
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.
View 2 Replies
View Related
Oct 31, 2010
I am running Fedora 12 on an Intel Core 2 Duo system.
I ran a software update which installed a new kernel (2.6.32.23-170.fc12.i686.PAE) along with many other things.
I am now unable to run VirtualBox which I had installed and running successfully before the update.
I tried removing and reinstalling VirtualBox from YUMEX, and rebooting. This did not help.
When I launch VirtualBox from a terminal, it produces the following output:
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: VBoxVMM.so: cannot open shared object file: No such file or directory
I'm not sure what it is complaining about. The files VirtualBox.so and VBoxVMM.so both exist in the /usr/lib/virtualbox directory.
What can be done to get VirtualBox working again on this system?
View 13 Replies
View Related
Jan 31, 2010
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.
View 14 Replies
View Related
Jun 2, 2011
Today is two out of three boot messages fixed. Working on the third one now, and that relates to virtual machines. The whole Virtual machine thing is new to me. Never used it, but I'd like to start. Therefore, I am no longer willing to just ignore this. The error message during boot is this:
Quote: Starting VirtualBox kernel module [60G[[0;31mFAILED[0;39m] (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
View 14 Replies
View Related
Dec 7, 2009
I have Fedora 12 right now, and I've come to the conclusion that the ATI catalyst drivers version 9.11 aren't going to work at all on that system, so I was going to downgrade to fedora 10 and install 9.8 or so on it. But what I was wondering is if I install Fedora 10 and then upgrade the kernel will that make the ATI drivers not work? Do I need to turn automatic updates off?
View 4 Replies
View Related
Nov 3, 2010
The audio stopped working since I upgraded my kernel from 2.6.35.6-45 to 2.6.36.6-48.
Is reinstalling alsa / pulse the only option ?
View 14 Replies
View Related
Mar 23, 2010
when I open virtualbox OSE and tried to run a vm i get this error
Code:
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. Re-setup the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. So i tried doing what it said and I got this error when i tried to run /etc/init.d/vboxdrv setup (as root)
Code:
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module, NOT. It has been packaged.Recompiling VirtualBox
[code]....
Then i ran dmesg and there was a ton of stuff that seemed to be unreleated so i ran dmesg -c to clear it. then i ran the vboxdrv this again then checked dmesg again expecting there to be nothing but the vboxdrv stuff but it was still blank.I really dont know what to do at this point I tried uninstalling and reinstalling but that makes no difference
View 6 Replies
View Related
Apr 26, 2011
I am using the 13.1 build scripts from slackbuilds.org. I modified the scripts to build 3.2.12 rather than 3.2.10.
In 13.1 the main VirtualBox 3.2.12 OSE package built and installed without errors. The VirtualBox GUI starts without errors.
Running the virtualbox-kernel-mksrctarball.sh script built a kernel source package without errors.
Yet the VirtualBox kernel module won't build. I receive the following error:
Code:
]*** Building 'vboxdrv' module ***
make[1]: Entering directory `/dev/shm/virtualbox-kernel-3.2.12/vboxdrv'
make KBUILD_VERBOSE= -C /lib/modules/2.6.33.11-smp-2/build SUBDIRS=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv SRCROOT=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv modules
[Code].....
View 2 Replies
View Related
May 31, 2010
I tried to build the virtualbox 3.1.6 kernel using the files from slackbuilds.org and I got this error that says it cannot find the kernel include directory. My current kernel is 2.6.33.2 (slack 13.1).
I tried SOME_VAR=/usr/include --> (I forgot the exact variable name, but I used the variable name I saw in the error message) just a guess , but it didn't work of course.
Is it at /usr/src/linux-2.6.33.2/include or something like that? Or is there anything wrong with the slackbuild script?
View 4 Replies
View Related
