I have installed the source rpms on CentOS 5.5 due to virtualbox upgrade not functioning. (the old one that comes with centos works fine, however, I wanted to newer one.)
Whenever I run the driver installation script it fails with an indication that it could not find the sources.
How do I correct the issue with the system not seeing the installed source rpms?
2010/8/7 MGW-Discussions mailinglistmember@mgwigglesworth.net:
I have installed the source rpms on CentOS 5.5 due to virtualbox upgrade not functioning. (the old one that comes with centos works fine, however, I wanted to newer one.)
Whenever I run the driver installation script it fails with an indication that it could not find the sources.
How do I correct the issue with the system not seeing the installed source rpms?
You need to install correct kernel headers and source from package and then it just works.
please post full error messages and installed packages (for example in pastebin.ca link)
-- Eero, RHCE
Thanks for the reply.
How do I verify where the sources should be after the rpm install?
How do I install only the headers, since that phrase keeps popping up but like many things on the net, no one ever actually verifies the process for making sure you have them installed, nor how to do it in the first place?
Here is the listing of kernel release and available rpms where I downloaded them.
[sysadmin@comcserver1 tmp]$ uname -r 2.6.18-194.el5 [sysadmin@comcserver1 tmp]$ ls |grep kernel |grep 2.6.18-194.el kernel-2.6.18-194.el5.src.rpm
Looks like I am going to have to crack open these linux kernel books I have been putting off, now. :P
On Sat, 2010-08-07 at 19:06 -0400, MGW-Discussions wrote:
Thanks for the reply.
How do I verify where the sources should be after the rpm install?
How do I install only the headers, since that phrase keeps popping up but like many things on the net, no one ever actually verifies the process for making sure you have them installed, nor how to do it in the first place?
rpm -qa | grep kernel
Here is the listing of kernel release and available rpms where I downloaded them.
[sysadmin@comcserver1 tmp]$ uname -r 2.6.18-194.el5 [sysadmin@comcserver1 tmp]$ ls |grep kernel |grep 2.6.18-194.el kernel-2.6.18-194.el5.src.rpm
Look here that is *NOT* what you need!
I'm listing all of them to make sure you are up to date...of which you are not...
yum update kernel kernel-headers kernel-devel Reboot the Machine to make sure your on the newest kernel.
Now for VirtualBox Run This to Compile the driver as root: /etc/init.d/vboxdrv setup
Now your done...
John
JohnS wrote:
rpm -qa | grep kernel
Look here that is *NOT* what you need!
I'm listing all of them to make sure you are up to date...of which you are not...
yum update kernel kernel-headers kernel-devel Reboot the Machine to make sure your on the newest kernel.
Now for VirtualBox Run This to Compile the driver as root: /etc/init.d/vboxdrv setup
Now your done...
John
As I have already indicated, the process is not as seamless as everyone seems to think it is from a basic upgraded virtualbox.
Thanks for the rpm clue, however, I evidently already have the headers installed and the setup command still fails. I need to know what to set KERN_DIR to since that much be the piece that is breaking the process.
Here is the result of running the commands that you listed previously:
[sysadmin@comcserver1 tmp]$ sudo rpm -qa | grep kernel kernel-2.6.18-194.8.1.el5 kernel-devel-2.6.18-194.8.1.el5 kernel-headers-2.6.18-194.8.1.el5 kernel-2.6.18-194.el5
[sysadmin@comcserver1 tmp]$ sudo yum update kernel kernel-headers kernel-devel Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile * addons: mirrors.finalasp.com * base: centos.mirror.netriplex.com * extras: mirror.vcu.edu * rpmforge: apt.sw.be * updates: mirror.anl.gov Setting up Update Process No Packages marked for Update
So if the installed kernel is not a properly updated kernel, then why does it not wish to further upgrade?
Here is repolist: sudo yum repolist Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile * addons: mirrors.finalasp.com * base: dist1.800hosting.com * extras: mirror.vcu.edu * rpmforge: apt.sw.be * updates: mirror.anl.gov repo id repo name status addons CentOS-5 - Addons enabled: 0 base CentOS-5 - Base enabled: 2,599 extras CentOS-5 - Extras enabled: 333 pidgin Pidgin for RHEL/CentOS 5 - i386 enabled: 266 rpmforge Red Hat Enterprise 5 - RPMforge.net - dag enabled: 10,344 updates CentOS-5 - Updates enabled: 416 virtualbox RHEL/CentOS-5 / i386 - VirtualBox enabled: 9 repolist: 13,967
I have restarted a second time, after removing the virtualization group, and the module compile worked.
However, I am still unclear as to why the kernel-headers were installed and it was not detecting them.
Also, how would I have resolved this issue of invisible sources and headers if it had not just magically started working.
I also read just now, how the xen kernel, as installed with Virtualization, will not work well with VBox so maybe that was it, however, how would that cause the setup script not to see the installed sources and headers?
Do I need to restart the system when the headers and sources are installed?
Even though it is now working, I am still unclear why it wasn't, and why it is now resolved.
On Sun, Aug 8, 2010 at 9:01 AM, MGW-Discussions mailinglistmember@mgwigglesworth.net wrote:
Do I need to restart the system when the headers and sources are installed?
That is generally a good idea since the kernel, headers and devel rpms are installed all at the same time. Otherwise you won't be running the newly installed kernel as well.
HTH...
Mark
On Sun, 2010-08-08 at 12:01 -0400, MGW-Discussions wrote:
JohnS wrote:
I have restarted a second time, after removing the virtualization group, and the module compile worked.
Really? Maybe you were running the Xen Kernel?
However, I am still unclear as to why the kernel-headers were installed and it was not detecting them.
See above.
Also, how would I have resolved this issue of invisible sources and headers if it had not just magically started working.
As per your yum command they were already install, you just needed a reboot to the new kernel.
I also read just now, how the xen kernel, as installed with Virtualization, will not work well with VBox so maybe that was it, however, how would that cause the setup script not to see the installed sources and headers?
That is not true. I have machine that coexists with Xen and Kvm x86_64.
Do I need to restart the system when the headers and sources are installed?
Yes for newly installed kernels like Mark said.
Even though it is now working, I am still unclear why it wasn't, and why it is now resolved.
The reboot?
John
-
Eero Volotinen -
JohnS -
Mark -
MGW-Discussions