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.
I am running Lenny and using VirtualBox OSE 1.6.6. In order to try squeeze I installed it in a VM. I tried to install Guest Additions also, but i get this error:
VirtualBox 1.6.6 Guest Additions installation Building the VirtualBox Guest Additions kernel module... Building the shared folder support kernel module... Unable to build the kernel module.
I checked what /var/log/vboxadd-install.log had to say:
/usr/src/linux-headers-2.6.32-5-common/include/net/neighbour.h:115: error: variably modified a at file scope /tmp/vbox.0/utils.c: In function 'sf_path_from_dentry:
I tried with 3 versions of the kernel 2.6.32-5-686,2.6.32-5-484,2.6.32-3-686 but I cannot get it to work using any of them. Also I tried to install version 2.6.30-2-686 but I couldn't since synaptic said that it Depends: linux-kbuild-2.6.30 but it is not installable.
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:
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/184.108.40.206-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?
OpenSUSE installed in a Virtualbox Virtual Machine and I want to set a shared folder.
1 - Set up a Virtual Machine and install OpenSUSE 11.2
2 - Create a shared folder on host (HostFolder)
3 - Setup the shared folder in Virtualbox Via the Virtual Machine details or via Devices > Shared Folders...
4 - Install dependencies for running the Virtualbox installer You need to install the right development kernelpackage for your machinetype (use 'zypper search -i kernel' to see what's installed) sudo zypper make gcc kernel-source kernel-hosttype/default-devel
5 - Run the Virtual Machine and go to Devices > Guest Additions This mounts an iso image in your OpenSUSE guest.
6 - Open a root terminal and run
cd /usr/src/linux make oldconfig && make prepare && make scripts && make dep cp ../linux-obj/$HOSTTYPE/default/Module.symvers . make prepare
* A commenter on previously mentioned thread says this step is unnecessary but it doesn't work without on my system. I suggest trying step 7 first and returning to step 6 if that fails. *
7 - Run ./VirtualboxLinux yourhosttype .run from the mounted iso image.
8 - Create shared folder in OpenSUSE (GuestFolder)
9 - Test with sudo mount -t vboxsf HostFolder /home/user/GuestFolder It works? Great! Let's set up the system so it automounts for your regular useraccount instead of root-only access.
10 - Add this line to /etc/fstab HostFolder /home/user/GuestFolder vboxsf defaults,uid=1000,gid=1000 0 0
11 - It works for me but if it still doesn't automount after a reboot; sudo mount -a
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 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 (220.127.116.11) 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'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.
I'm trying to install the Virtual Box Guest Addition for my openSUSE 11.3 VM, but I'm having some problems. The Virtual Box manual says I need to install the kernel-default-devel package, so I did that, but it also says :
Make sure that your running kernel (uname -a) and the kernel packages you have installed (rpm -qa kernel*) have the exact same version number. Proceed with the installation as described above.So I ran both commands and here is the output :
edgar@linux-t7uc:/> uname -a Linux linux-t7uc 2.6.34-12-default #1 SMP 2010-06-29 02:39:08 +0200 i686 athlon i386 GNU/Linux edgar@linux-t7uc:/> rpm -qa kernel*
the devel packages are version 18.104.22.168-0.7.1 and the kernel is version 2.6.34-12. How do I install the correct version of the kernel-default-devel and kernel-devel package with zypper? I thought maybe the versions could be compatible somehow, so I tried to install the Guest Addition and here's the result :
edgar@linux-t7uc:/media/VBOXADDITIONS_4.0.4_70112> sudo sh ./VBoxLinuxAdditions.run root's password: Verifying archive integrity... All good. Uncompressing VirtualBox 4.0.4 Guest Additions for Linux.........
This has got me stumped. I expected to do /etc/init.d/vboxdrv setup after the upgrade from 11.3 to 11.4 but the command fails. The log is (it seems to repeat so I only quote the final bits to make it fit into the wordcount limit):
Code: make KBUILD_VERBOSE=1 -C /lib/modules/22.214.171.124-1.2-desktop/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
I have Ubuntu running as a Virtualbox, and every time it upgrades the kernel, the Guest Additions stop working.The install process in Linux requires using a virtual CD, running scripts from the command line, etc.Is there any way to keep the guest additions constantly working even when the kernel is upgraded? Can they be installed as Ubuntu packages instead of installing off the virtual CD?
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 installed a Fedora 14 guest on a Fedora 14 host with Virtualbox, then i run these commands on the guest:yum install kernel-devel kernel-headersbut if i try to install the virtualbox-guest additions on the guest, is still complains about that it's unable to find the kernel source directory?Ha anyone succeded installing the guest additions on a guest Fedora 14?
I had a lot of trouble installing Guest Additions within the Fedora 13 Guest on a Linux host. I had to mount the vboxGuestadditions.iso from the Device --> CD/DVD Devices menu. Then I located the appropriate package for my system. In my case it was the AMD64 Linux version.I ran this as administrator in Terminal. I used the "bash" command followed by the package name. This was after CDing the the appropriate directory. The packaged installed, I then rebooted and it worked fine. (Something that would make this easier is to load a script into nautilus that would allow me to open a locatation as administartor at the open window. I'm sure there is something in Fedora to do this but I couldn't find it in a hurry so I used the command line way).
Experienced that building the vbox guest additions (on the binary/non-free vbox) on a slackware --current guest (with windows *and* linux as a host) fails now with the new kernel's just released in --current?
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).
I get this when trying to launch a VB after making one with wizzard.
I have been having some problems with virtualbox starting. So here is the issue: When I start a VM I get the following: 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. reinstall the kernel module by executing
I am seeing quite a few entries about the usb. I am not sure if that is common or if its unrelated. I am running x86 11.3, and virtualbox 4.0.4 I have tried to uninstall, and even go back to 3.2
I just up-graded to the latest version of the stable 11.4 64bit kernel on my laptop and it appears that the repositories have not compiled the VirtualBox driver module for the current kernel ... When I make /vboxdrv setup the message is:
Recompiling VirtualBox vboxadd kernel module, NOT. It has been packaged
I think this means that the installed module will not recompile has it was packaged. My kernel version is the lattest :
And my VirtualBox was installed from the Virtualization repos (126.96.36.199-1) even made the Vendor change and all. The version Before the lattest (4.0.4-1.6) did not work either. With the same problem. It is very easy to install VirtualBox from the Sun site and every time there is a Kernel up-date one can always make /etc/vboxdrv setup.
I've just installed clean copies of both VirtualBox v4.0.8 and Fedora 15. Now I have followed the instructions here : [url] to install the latest VBox guest additions.
Each time I try I get the following message:
The headers for the current running kernel were not found. If the following module compilation fails then this could be the reason. The missing package can be installed with yum install kernel-devel-188.8.131.52-32.fc15.i686.PAE.
However, if I run that command I am told there is no such package available. The guest addition installer continues seemingly OK, but after a restart they are not loaded.
I've just moved to Fedora from Ubuntu due to major issues with its new version.
I have installed Virtualbox PUEL in 64-bit 11.3. This is a fresh install. My computer has an onboard nvidia 8300GS graphics card. I do not think this is related to the issue. I added the virtualbox repository and installed the program via yast. when I type "VirtualBox" in the terminal I get the following output:
I'm trying to build the kernel module for dvbhdhomerun. The problem is the linux kernel headers provided by Debian do not have the dvb header files. Trying to set up my own kernel source tree to use is not working out so well.
I'm following the instructions in the Debian section here: [URL] ....
My first try compiled, but the modules ender up under /lib/modules/3.2.51/extra instead of /lib/modules/3.2.0-4-amd64/extra. Why?
I tried to start over, but noticed this while running apt-get source linux-image-3.2.0-4-amd64:
Code: Select allReading package lists... Done Building dependency tree Reading state information... Done Picking 'linux' as source package instead of 'linux-image-3.2.0-4-amd64' NOTICE: 'linux' packaging is maintained in the 'Svn' version control system at: svn://svn.debian.org/svn/kernel/dists/trunk/linux/
The failure to verify the signature has me concerned, but beyond that, what do I do about the different version number when compiling and installing the kernel modules?
I'm trying to set up a netbook I purchased that has a lot of more recent hardware, and so I'm having to compile some kernel modules on my own. I've installed Debian on this particular system, and so the version of gcc that was used to compile the kernel is older than the one currently in the repos. Now, I've installed the version I need, but can't remember how to specify building the modules in question with said version.
I've done this in the past, and recall temporarily changing some variable to use the different version, but it's been a while and I just can't remember. Is there an easier way to do this on the fly for any compilation? Or is changing a variable necessary? If there is no way to explicitly specify gcc version used prior to a compilation, could someone remind me of the variable I need to change to use x.x.x version?
pretty comfortable at the command line and in kde. found 2 'supplementary kernel drivers' for virtualbox at slackbuild (thank you heinz!). followed the how-to at slackbuild and built and installed both packages, but additions weren't working. (i thought they were standalone) noticed the 'supplemental' in their description, and so installed the guest additions for linux from vbox site. additions still not working. at this point i start restarting my slackware vm, and redoing everything in various sequences. finally, additions work! but i'm not sure why! critical pieces and sequence for getting guest additions working once i have slackware installed?
I use CentOS under VirtualBox. There are Guest Additions, but for Ubuntu are virtualbox-ose-guest-utils and virtualbox-ose-guest-x11 There are GA replacements, better than GA (no problem with AppArmor). Are CentOS replacements ?