<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Installing VirtualBox on a PAE Kernel System</title>
	<atom:link href="http://systembash.com/content/installing-virtualbox-pae-kernel-centos/feed/" rel="self" type="application/rss+xml" />
	<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/</link>
	<description>Technology and System Administration</description>
	<lastBuildDate>Sun, 06 May 2012 22:45:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Hristosky</title>
		<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/comment-page-1/#comment-41877</link>
		<dc:creator>Hristosky</dc:creator>
		<pubDate>Wed, 20 Jul 2011 07:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/?p=301#comment-41877</guid>
		<description>You just saved me a ton of time, my friend! Big Thank You!</description>
		<content:encoded><![CDATA[<p>You just saved me a ton of time, my friend! Big Thank You!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sfystone</title>
		<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/comment-page-1/#comment-41770</link>
		<dc:creator>Sfystone</dc:creator>
		<pubDate>Sat, 11 Dec 2010 17:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/?p=301#comment-41770</guid>
		<description>I tried with this, but it still won&#039;t solve my problem. 
I do just follow the advice, and get a problem as this link is not available:
/lib/modules/build -&gt; ../../../usr/src/kernels/2.6.35.6-48.fc14.i686.PAE

Then I find that the kernel source file and kernel module don&#039;t match each other:
$ ll /usr/src/kernels/; ll /lib/modules/; ll /lib/modules/2.6.35.6-48.fc14.i686.PAE/ &#124;grep build
total 16
drwxr-xr-x. 22 root root 4096 Nov 19 14:58 2.6.35.6-45.fc14.i686
drwxr-xr-x. 22 root root 4096 Nov 15 00:04 2.6.35.6-48.fc14.i686
drwxr-xr-x. 22 root root 4096 Dec 8 17:08 2.6.35.9-64.fc14.i686
drwxr-xr-x. 22 root root 4096 Dec 8 15:19 2.6.35.9-64.fc14.i686.PAE
total 12
drwxr-xr-x. 7 root root 4096 Dec 8 16:50 2.6.35.6-45.fc14.i686
drwxr-xr-x. 6 root root 4096 Dec 8 16:50 2.6.35.6-48.fc14.i686
drwxr-xr-x. 6 root root 4096 Nov 27 23:38 2.6.35.6-48.fc14.i686.PAE
lrwxrwxrwx. 1 root root 50 Nov 27 23:17 build -&gt; ../../../usr/src/kernels/2.6.35.6-48.fc14.i686.PAE
lrwxrwxrwx. 1 root root 5 Nov 27 23:17 source -&gt; build

$ rpm -q kernel-PAE-devel
kernel-PAE-devel-2.6.35.9-64.fc14.i686
$ uname -r
2.6.35.6-48.fc14.i686.PAE

How can that be?
Since there&#039;s only one PAE for src and one for module, I simply make link as build -&gt; ../../../usr/src/kernels/2.6.35.9-64.fc14.i686.PAE

then fail as:
Starting VirtualBox kernel modules                         [FAILED]
  (modprobe vboxdrv failed. Please use &#039;dmesg&#039; to find out why)
dmesg shows: 
[ 1544.584690] vboxdrv: version magic &#039;2.6.35.9-64.fc14.i686.PAE SMP mod_unload 686 &#039; should be &#039;2.6.35.6-48.fc14.i686.PAE SMP mod_unload 686 &#039;

Now I get stuck. anybody know what&#039;s next?</description>
		<content:encoded><![CDATA[<p>I tried with this, but it still won&#8217;t solve my problem.<br />
I do just follow the advice, and get a problem as this link is not available:<br />
/lib/modules/build -&gt; ../../../usr/src/kernels/2.6.35.6-48.fc14.i686.PAE</p>
<p>Then I find that the kernel source file and kernel module don&#8217;t match each other:<br />
$ ll /usr/src/kernels/; ll /lib/modules/; ll /lib/modules/2.6.35.6-48.fc14.i686.PAE/ |grep build<br />
total 16<br />
drwxr-xr-x. 22 root root 4096 Nov 19 14:58 2.6.35.6-45.fc14.i686<br />
drwxr-xr-x. 22 root root 4096 Nov 15 00:04 2.6.35.6-48.fc14.i686<br />
drwxr-xr-x. 22 root root 4096 Dec 8 17:08 2.6.35.9-64.fc14.i686<br />
drwxr-xr-x. 22 root root 4096 Dec 8 15:19 2.6.35.9-64.fc14.i686.PAE<br />
total 12<br />
drwxr-xr-x. 7 root root 4096 Dec 8 16:50 2.6.35.6-45.fc14.i686<br />
drwxr-xr-x. 6 root root 4096 Dec 8 16:50 2.6.35.6-48.fc14.i686<br />
drwxr-xr-x. 6 root root 4096 Nov 27 23:38 2.6.35.6-48.fc14.i686.PAE<br />
lrwxrwxrwx. 1 root root 50 Nov 27 23:17 build -&gt; ../../../usr/src/kernels/2.6.35.6-48.fc14.i686.PAE<br />
lrwxrwxrwx. 1 root root 5 Nov 27 23:17 source -&gt; build</p>
<p>$ rpm -q kernel-PAE-devel<br />
kernel-PAE-devel-2.6.35.9-64.fc14.i686<br />
$ uname -r<br />
2.6.35.6-48.fc14.i686.PAE</p>
<p>How can that be?<br />
Since there&#8217;s only one PAE for src and one for module, I simply make link as build -&gt; ../../../usr/src/kernels/2.6.35.9-64.fc14.i686.PAE</p>
<p>then fail as:<br />
Starting VirtualBox kernel modules                         [FAILED]<br />
  (modprobe vboxdrv failed. Please use &#8216;dmesg&#8217; to find out why)<br />
dmesg shows:<br />
[ 1544.584690] vboxdrv: version magic &#8217;2.6.35.9-64.fc14.i686.PAE SMP mod_unload 686 &#8216; should be &#8217;2.6.35.6-48.fc14.i686.PAE SMP mod_unload 686 &#8216;</p>
<p>Now I get stuck. anybody know what&#8217;s next?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: som</title>
		<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/comment-page-1/#comment-40480</link>
		<dc:creator>som</dc:creator>
		<pubDate>Tue, 06 Jul 2010 14:47:33 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/?p=301#comment-40480</guid>
		<description>thanks man, solved my problems</description>
		<content:encoded><![CDATA[<p>thanks man, solved my problems</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: som</title>
		<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/comment-page-1/#comment-41579</link>
		<dc:creator>som</dc:creator>
		<pubDate>Tue, 06 Jul 2010 14:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/?p=301#comment-41579</guid>
		<description>thanks man, solved my problems</description>
		<content:encoded><![CDATA[<p>thanks man, solved my problems</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sonic</title>
		<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/comment-page-1/#comment-39739</link>
		<dc:creator>sonic</dc:creator>
		<pubDate>Sat, 12 Dec 2009 23:16:01 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/?p=301#comment-39739</guid>
		<description>Muchas gracias, me solucionaste mi problema. :D</description>
		<content:encoded><![CDATA[<p>Muchas gracias, me solucionaste mi problema. :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sonic</title>
		<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/comment-page-1/#comment-41578</link>
		<dc:creator>sonic</dc:creator>
		<pubDate>Sat, 12 Dec 2009 23:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/?p=301#comment-41578</guid>
		<description>Muchas gracias, me solucionaste mi problema. :D</description>
		<content:encoded><![CDATA[<p>Muchas gracias, me solucionaste mi problema. :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Trancozo</title>
		<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/comment-page-1/#comment-37804</link>
		<dc:creator>Roger Trancozo</dc:creator>
		<pubDate>Tue, 15 Sep 2009 15:38:22 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/?p=301#comment-37804</guid>
		<description>Com o RHEL5.3 - Linux 2.6.18-164.el5PAE - funcionou.
Muito obrigado.</description>
		<content:encoded><![CDATA[<p>Com o RHEL5.3 &#8211; Linux 2.6.18-164.el5PAE &#8211; funcionou.<br />
Muito obrigado.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Trancozo</title>
		<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/comment-page-1/#comment-41577</link>
		<dc:creator>Roger Trancozo</dc:creator>
		<pubDate>Tue, 15 Sep 2009 15:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/?p=301#comment-41577</guid>
		<description>Com o RHEL5.3 - Linux 2.6.18-164.el5PAE - funcionou.
Muito obrigado.</description>
		<content:encoded><![CDATA[<p>Com o RHEL5.3 &#8211; Linux 2.6.18-164.el5PAE &#8211; funcionou.<br />
Muito obrigado.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajitabh Pandey</title>
		<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/comment-page-1/#comment-37450</link>
		<dc:creator>Ajitabh Pandey</dc:creator>
		<pubDate>Sat, 22 Aug 2009 10:01:29 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/?p=301#comment-37450</guid>
		<description>That&#039;s because you must have installed kernel-devel instead of kernel-xen-devel. This will compile the module. But when you try to load the module, it will reboot the system and then you wont be able to boot it unless you boot in single user mode and then disable the vboxdrv init script. 

Xen and VirtualBox are incompatible (at least at the time of writing this). Someone filed bug with virtualbox but that was closed with the status as &quot;wont fix&quot;. So I guess you will need some other kernel and not xen.</description>
		<content:encoded><![CDATA[<p>That&#8217;s because you must have installed kernel-devel instead of kernel-xen-devel. This will compile the module. But when you try to load the module, it will reboot the system and then you wont be able to boot it unless you boot in single user mode and then disable the vboxdrv init script. </p>
<p>Xen and VirtualBox are incompatible (at least at the time of writing this). Someone filed bug with virtualbox but that was closed with the status as &#8220;wont fix&#8221;. So I guess you will need some other kernel and not xen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajitabh Pandey</title>
		<link>http://systembash.com/content/installing-virtualbox-pae-kernel-centos/comment-page-1/#comment-41576</link>
		<dc:creator>Ajitabh Pandey</dc:creator>
		<pubDate>Sat, 22 Aug 2009 10:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/?p=301#comment-41576</guid>
		<description>That&#039;s because you must have installed kernel-devel instead of kernel-xen-devel. This will compile the module. But when you try to load the module, it will reboot the system and then you wont be able to boot it unless you boot in single user mode and then disable the vboxdrv init script. 

Xen and VirtualBox are incompatible (at least at the time of writing this). Someone filed bug with virtualbox but that was closed with the status as &quot;wont fix&quot;. So I guess you will need some other kernel and not xen.</description>
		<content:encoded><![CDATA[<p>That&#8217;s because you must have installed kernel-devel instead of kernel-xen-devel. This will compile the module. But when you try to load the module, it will reboot the system and then you wont be able to boot it unless you boot in single user mode and then disable the vboxdrv init script. </p>
<p>Xen and VirtualBox are incompatible (at least at the time of writing this). Someone filed bug with virtualbox but that was closed with the status as &#8220;wont fix&#8221;. So I guess you will need some other kernel and not xen.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Database Caching 11/26 queries in 0.007 seconds using disk: basic

Served from: systembash.com @ 2012-05-21 09:25:33 -->
