For some reason, when I click on the Slackbuild link for virtualbox-kernel (3.1.6) for virtualbox-kernel-3.1.6.tar.xz , it downloads as virtualbox-kernel-3.1.6.tar.tar. The file is misnamed. If it is renamed virtualbox-kernel-3.1.6.tar.xz , the SlackBuild works just fine.
View 10 RepliesI 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?
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].....
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?
I download "VirtualBox-3.1.2-56127-Linux_amd64.run" and installed it, and got a messages like this " virtualbox have been installed successfully in my system", but when I run virtualbox, I've been told "/etc/init.d/vboxdrv setup" something like that. And I run virtualbox in terminal, got this:
Warning: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.29.6) or it failed to load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed.
I run "/etc/rc.d/rc.vboxdrv start" as a root, got messages like this :
Starting VirtualBox kernel module ...failed!
(modprobe vboxdrv failed.)
I had an issue with the module build for vbox 3.1.2 breaking on the latest kernel ( /etc/rc.d/rc.vboxdrv setup ). Apparently the issue is that a kernel header (autoconf.h ) has changed its location in the module tree and hence the issue.
2 options:
1. upgrade to 3.1.4
2. create a symlink as follows
cd /usr/src/linux/include/linux
ln -s ../generated/autoconf.h autoconf.h
If others are have the problem of VirtualBox failing to build the kernel modules with kernel 2.6.32 try this :-
1. Install VirtualBox and watch as the kernel modules fail to compile.
2. Change the line
Code:
KFLAGS += -DRT_ARCH_AMD64
TO
Code:
KFLAGS += -DRT_ARCH_X86_64
In the following files :-
Code:
Line 231 /opt/VirtualBox/src/vboxdrv/Makefile
Line 170 /opt/VirtualBox/src/vboxnetadp/Makefile
Line 174 /opt/VirtualBox/src/vboxnetflt/Makefile
3. Run /etc/rc.d/rc.vboxdrv setup
You will now have a working VirtualBox setup. NB This is written purely from the standpoint of using the Closed source version of VB not the OSE version.
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.
Is there any way to install "VirtualBox-3.2.12-68302" in the "slackware64-current" (Kernel 2.6.38.7) ?
I have problems with the 4.0.x version of VB!
The version "VirtualBox-3.2.12-68302" works fine with my hardware!
I tested using "VB 3.2.12" and Slackware64-13.37 (kernel 2.6.37.6).
I get the warning when I try to install a guest OS in "VB 3.2.12" running slackware64-current ...
Quote:
There is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
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"
And still
Quote:
Failed to open a session for the virtual machine Slackware12.0.
The virtual machine 'Slackware12.0' has terminated unexpectedly during startup with exit code 1.
Result Code:
Any location I can download kernel-xen-2.6.36 for RHEL 5 Update6, 32bit machine.
View 1 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]....
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 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?
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 RelatedI installed Slackware 13 in VirtualBox 3.1 (seehere)When I'm logged in as a normal user, I get a mesage that Intel *** (sound device) doesn't work anymore and I hear no sound.But it works very fine when I'm logged in as root.
View 4 Replies View RelatedI went to create a windows XP in my virtualbox and this pops up
Please install the virtualbox-ose-dkms package and execute 'modprobe vboxdrv' as root.
is this a safe download? its never asked me too do this before.
I've been getting this error when trying to upgrade packages with slapt-get:
Failed to download: Incomplete download
Not sure what's going on. I tried to use --clean and tried to use a different mirror, but still getting the error.
I just rebuild the kernel for slackware 13, everything works, but root file system which is ext3 is mounted as ext2. Normally I've build ext3, ext4 and so on as modules, not in the kernel... but if I do this, then the kernel mounts the file system as ext2, which is build in the kernel. I also modified rc.modules so I can make sure that ext3,ext4,jbd are loaded, but it doesnt work.
View 2 Replies View Relatedwhere to download Guest Additions Virtualbox for Fedora 14 ?
View 4 Replies View RelatedWhen 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?
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 Relatedwhen 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
I updated my system to the latest version - 5.5. After that I could not install VirtualBox. I was thinking, trying to fix, googling... it over for hours... Finally I found the reason. VirtualBox installer searches for the source kernel at /lib/modules/2.6.18-194.17.4.el5/build, and it can not. Look into /lib/modules, I have some kernels such as:
- 2.6.18-194.17.4.el5
- 2.6.18-194.17.4.el5debug
- 2.6.18-194.17.4.el5xen
... and more old ones.
At that time, I booted on 2.6.18-194.17.4.el5 kernel. But inside that directory, there is no build or source (directory/ file). Then I looked into 2.6.18-194.17.4.el5debug, and it had. So I typed: ln -s /lib/modules/2.6.18-194.17.4.el5debug/build /lib/modules/2.6.18-194.17.4.el5/build
Actually, Slack64 runs just fine under VirtualBox on my old HP under WinXP, But the installer for Slack86 won't boot under VirtualBox on my Toshiba Netbook under Win7 starter. I tried updating the 13.1 install I have on there, but I get the same kernel panic when I try to reboot that. It always bails just as it is switching over to the new kernel. The dump fills my screen so I can't see the actual error. How can I capture that initial startup log? Slack86 runs just fine on my old Compac Armada 1700 (266PII 92M/12G), but that's a very different environment.
View 10 Replies View RelatedI have an ISO of 13.37, I have selected the ISO as the booting medium in the Virtual Box and I do get uptil the screen where one is supposed to select the source media. Because I am installing from an ISO what option I am supposed to select out of the 6 present there?
View 4 Replies View RelatedThe latest release of VirtualBox (3.1.6) corrects most of the problems that I had with Slackware and KDE. If you have been avoiding VirtualBox or KDE because of those issues you might want to take another look.The only problem that I'm having now is that I have to click somewhere on the desktop to get a proper display when switching VirtualBox into "seamless" mode. The rest of the window display issues appear to be fixed and full screen mode also works correctly.
View 2 Replies View RelatedI downgraded a computer a couple of weeks ago from -current to 13.1. At that point in time the USB support in my Virtualbox stopped working. Since then I have installed Virtualbox on my wife's laptop, which also runs 13.1, and the USB support doesn't work there either. So I tried it on yet another 13.1 box that I have lying around no USB support. Then I upgraded the latter box to -current and USB works! Given that sequence of events, I'm pretty sure this is a Slackware 13.1 problem rather than a Virtualbox problem. what might be causing this?
View 8 Replies View RelatedHow 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