I installed CentOS however during package selection, I deselected every option because I don't need or want the bloated dependencies however now when I try and install a 3rd party RPM from Oracle (VirtualBox), it fails:[root@vbox ~]# cat /var/log/vbox-install.log ** Compiling vboxdrvMakefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.
View 2 RepliesI'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 installed CentOS however during package selection, I deselected every option because I don't need or want the bloated dependencies however now when I try and install a 3rd party RPM from Oracle (VirtualBox), it fails:
Code:
[root@vbox ~]# cat /var/log/vbox-install.log
** Compiling vboxdrv
[code]....
I'm trying to run OpenSUSE 11.2 on VirtualBox (ver3.0.8 on Ubuntu 9.10). The installation proceeds without a hitch, but when I try to login, the login manager (kdm?) complains that the login failed. When I go to the console, my login/password do no work there either. I've tried installing OpenSUSE 11.2 three times -- the first two times, it complained about the simplicity of my password -- and all three times I've run into this problem.Have other users encountered a similar problem? It doesn't seem like a VirtualBox-specific issue. Is the /etc/password being changed somehow?
View 5 Replies View Relatedi would like to install CentOS 5.3 on my VirtualBox?
View 1 Replies View RelatedI want to install a Centos 5.0 Virtualbox for Windows 7 x64. Can someone please let me know where I can go to get that, because I would like to have the virtualbox to further understand how LINUX works. I have taken a course in Redhat Enterprise Linux Computing Essentials, and I enjoyed using LINUX. So that is why I am searching for a 5.0 free download of Virtualbox.
View 8 Replies View RelatedI have 2 Centos 5.4 builds...one is x64 and the other on aother box is 32 bit...Both are running in virtual machines with version 3.1.4 Virtualbox.
I have tried on both versions to install the guest additions and on each the terminal comes up briely and then does not install...No error messages.
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.
I installed CentOS 5.5 this morning with zimbra 6.0.7. Everything seemed to go perfectly until at the end the following zimlets failed to install
com_zimbra_phone...failed.
com_zimbra_email...failed.
com_zimbra_dnd...failed.
com_zimbra_url...failed.
I installed zimbra successfully on Fedora 11 before. But I heard how stable CentOS is so I decided to switch. I read a lot online about how a lot of people have had zimbra on CentOS5 without any issues that were not easily solved. Zimbra appears to be working fine. I was able to add my domains, accounts, and send/receive email. So I'm not quite sure how important these zimlets are or if I even need them. But I'd like to know that the software is working the way it's supposed to. Since I'm new to Zimbra I want to make sure I get full exposure so I can learn it well.
I tried to install MATLAB 2010b on CentOS 5.3 but failed.
I mounted the DVD manually using the following lines
$ umount /dev/scd0
$ mount -t iso9660 /dev/scd0 /local
when I type $ sh /local/install
shell display the following
Preparing installation files .. Installing ...
and never move.
I noticed that the computer is reading the DVD. Then DVD light stop blinking and dim; and nothing happen.
in order to using the SR-IOV, according the guide HOW_SRIOV [Moderator edit: fixed link.]but i can't got the VFs.so i try to compile the driver :igb-2.4.13 and igbvf1.0.7.but i failed to install them.when i make install the igb-2.4.13 i got the errormsg:root@localhost src]# make installakefile:106: *** Linux kernel source not configured - missing version header file‚[root@localhost src]# i alreadly installed the kernel-headers-2.6.18-194.32.1.el5.x86_64.rpm .some system info maybe needed:Information for general problems.
== BEGIN uname -rmi ==
2.6.18-164.el5 x86_64 x86_64
== END uname -rmi ==
[code]....
after install virtualbox i have this error when i try to run it.
GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL) Aborted (core dumped).
Has anyone tried to install virtualbox on 9.04 Jaunty recently? [URL]. The links for vbox Jaunty are dead, and the apt-sources entry is apparently malformed...
$ cat virtualbox.list
deb [URL] jaunty contrib
During an "apt-get update":
Hit [URL] jaunty Release.gpg
Ign [URL] Translation-en_CA
Hit [URL] jaunty Release
W: Failed to fetch [URL] Unable to find expected entry contrib/binary-i386/Packages in Meta-index file (malformed Release file?)
I have ubuntu 11.04 with virtualbox installed. I have some old vmware virtual machines on an NTFS partition that I am able to successfully boot with virtualbox at my ubuntu desktop however, when I vnc into my desktop from a remote location and start up virtualbox and try to boot my virutal machines, I get:
Quote:
Failed to open a session for virtual machine.. the virtual machine has terminated unexpectedly during startup with exit code 0.
result code NS_ERROR_FAILURE 0x80004005
component: MACHINE
interface: IMACHINE
from googling this some people have indicated this means my username is not in the virtualbox user group, but I am logging in with the same username over vnc as I do when sitting at the machine where virtualbox works fine. the directory the machines are on is mounted, not sure why I can't boot them what else could be causing my problem? has anyone ever setup vnc4server on ubuntu and got virtualbox working?
So far failed to get either RHEL 6.0 Eval or Centos to install on Virtual Box.
Should it really be that difficult?
after upgrading VirtualBox from 3.0.x to VirtualBox-OSE-3.1.2-1.fc12.x86_64 VBox fails to start any virtual machine with error: Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
When I run
sudo /etc/sysconfig/modules/VirtualBox-OSE.modules
I get
FATAL: Error inserting vboxnetflt (/lib/modules/2.6.31.12-174.2.19.fc12.x86_64/extra/VirtualBox-OSE/vboxnetflt.ko): Invalid module format
FATAL: Error inserting vboxnetadp (/lib/modules/2.6.31.12-174.2.19.fc12.x86_64/extra/VirtualBox-OSE/vboxnetadp.ko): Invalid module format
Kernel is (obviously) kernel-2.6.31.12-174.2.19.fc12.x86_64, but same thing happens with any installed kernel, IE kernel-rt-2.6.31.12-1.rt20.1.fc12.ccrma.x86_64
I reinstalled VBox and kmods got rebuilt but the problem persists.
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 RelatedI 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'am using gentoo linux. After some system's updates VirtualBox stoped loading any virtual machine with error:
Code: Failed to open a session for the virtual machine. Virtual machine has terminated unexpectedly during startup.
Details:
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Machine
Interface: IMachine {99404f50-dd10-40d3-889b-dd2f79f1e95e} Kernel log
Code:
So, i've rebuilded all VirtualBox dependencies with safe flags, then i've recompiled most of the sys-* packages also with safe flags. However VirtualBox still doesn't work.
UPD: virtualbox-bin-3.1.4
UPD2: 3.1.6 and ose-versions crashes with same errors
I just ran into a weird problem with a CentOS 5.5 64-bit server running VirtualBox 3.2.8 (I would run Vmware Server 2.0.2 if not for the well known fact that Vmware doesn't care about its Server line anymore and it doesn't run on CentOS > 5.3 without major splits). I currently have two guests in that VirtualBox setup, a CentOS 5.5 64-bit and a Fedora 13 64-bit. The CentOS 5.5 guest shows less memory available than configured. If, for example, I give the virtual machine 512MB of memory the guest OS only recognizes 380MB. If I give it 768MB it only recognizes 637MB, and so on. I don't have that problem on the Fedora guest - 1024MB configured, 1024MB available.
View 13 Replies View RelatedWhen i try to create a virtual machine using the Windows 7 Enterprise Evaluation iso file, everything goes as planned untill i click on the start button. when i click on it i get two error messages. the first: Failed to open a session for the virtual machine Windows 7. The virtual machine 'Windows 7' has terminated unexpectedly during startup with exit code 1. 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
'/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. i have installed the DKMS package, but when i try to run the command stated in the error message, i get another error message in the terminal:
[code]...
i have to install the driver that is specified (vboxdrv) but i do not know where to find it.
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 had the elrepo kmod-r8168 driver running smooth for a while on my development box.
Yesterday, I did a clean install on it and when I tried to install the latest kmod-r8168 rpm, it failed to enable the networking support:
# yum --enablerepo=elrepo install kmod-r8168
The install performed all proper steps to disable the 8169 driver, I double checked to be sure.This is not a connectivity issue. If I remove the kmod-r8168 rpm, reboot the server and run the ifconfig eth0 up to activate the interface, everything works as expected. I use the latest kernel (2.6.18-194.26.1.el5 x86_64).
First, I performed a clean install, activated the eth0 and did a yum update, then installed the kmod-r8168 with yum. Then, I reinstalled the OS again, activated the eth0 and installed the kmod-r8168 on a 5.5 CD based kernel, same fail results. The only hiccup is: every time I start the box, I have to activate the eth0 interface (with default CentOS 8169 driver):
# ifconfig eth0 192.168.1.3
# ping -c 3 192.168.1.1 (no packets lost)
# ifconfig eth0 up
Once I do this, I have network connectivity.
I decided to take centos 5.5 for a testdrive. I download the live cd iso and attempted to boot the system via virtualbox on my mac os 10 system. I get the blue boot screen and choosing either the graphical boot or text boot gets me no where, the blue screen remains and nothing happens). Virtualbox is able to boot other linux systems fine so I am not sure if this is a centos issue or centos/virtualbox issue.
View 1 Replies View RelatedSubprocess failed. Error: RPM failed: installing package xen-4.0.0_21091_06-0.1.1.x86_64 needs 27MB on the /boot filesystemI seem not to be able to change the size of the /boot, but 11.2 loads okay but not 11.3There only 19MB left from 66 and I can't make it bigger, I hope there is someone thathas seen this. I would like to see some of the update with XEN.
View 1 Replies View RelatedI 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 am trying to learn about networking and am looking to set up a mini network between three bare bones Centos machines in Virtualbox. I set up the machines with a static IP. In the Virtualbox I am using NAT and have the IPs as follows
Centos-1
IP: 10.0.2.15
Gateway: 10.0.2.2
DNS: 10.0.2.3
Centos-2
IP: 10.0.2.16
Gateway: 10.0.2.2
DNS: 10.0.2.3
Centos-3
IP: 10.0.2.17
Gateway: 10.0.2.2
DNS: 10.0.2.3
On all machines i can ping google.com, and yum updates, but I can not ping any other machine. It says they are unreachable. NOt really sure what to do. Any help would be much appreciated.
I have installed a recent version of CentOS 5 (kernel is 2.6.18-128.el5) as VM in VirtualBox on a Windows 2008 server. When CentOS is totally idle, the CPU on the host (windows) machine is totally pegged from the VirtualBox process. I have read on some other forums that this is a problem with the clock running at 1000Hz and that recompiling the kernel configured with the clock at 100Hz will fix, or at least minimize the problem.
Has anyone else seen this problem? Can someone point me to a good set of instructions on rebuilding the kernel? I followed one set of instructions, but it wasn't for CentOS. After I building everything I was supposed to and copying files over the System.map* and vmlinuz* in the /boot directory (I think I screwed up that one), I went to modify the lilo.conf per the instructions, but I couldn't find it.
I installed centos 5.3 with last update in Virtualbox 3.06. Everything looks quite good except the unix time. It's very fast than normal. I even couldn't make ntpd work.
[Code]...
I also modified the menu.lst files as following: kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/vg00/lv00 rhgb quiet divider=10 But it still dosen't work. how to sync the local time in the virtualbox? It looks like a bug in current kernel as other linux with newer kernel don't have such problem.
I am running a Centos 5 x86_64 guest with VirtualBox 3.1.2.The virtio modules are loaded, but the virtual interface is not detected.Anyone else use the new virtio network drivers with virtual box and know how to get this to work?
View 1 Replies View Related