Dear Fedorians, I'm a new user of fedora 13 and I use a virtualbox installation on it.
Unfortunately the last two kernel upgrades (2.6.34.6-54 and 2.6.34.7-56) didn't correspond to an upgrade of the kernel modules necessary by virtualbox (vboxdrv, vboxnetflt, and vboxnetadp); this impedes the normal behavior of virtualbox.
Running yum update I simply get the message that everything is up to date.
dkms is installed and running and also the virtualbox repository is installed (it comes from http://www.virtualbox.org/wiki/Linux_Downloads).
The installed packages are:
kmod-VirtualBox-OSE-2.6.34.6-47.fc13.x86_64-3.2.6-1.fc13.5.x86_64 VirtualBox-OSE-3.2.6-2.fc13.x86_64 kernel-2.6.34.6-47.fc13.x86_64 kernel-2.6.34.6-54.fc13.x86_64 kernel-2.6.34.7-56.fc13.x86_64 kernel-devel-2.6.34.6-47.fc13.x86_64 kernel-devel-2.6.34.6-54.fc13.x86_64 kernel-devel-2.6.34.7-56.fc13.x86_64 kernel-headers-2.6.34.7-56.fc13.x86_64 dkms-2.1.0.1-1.fc12.noarch
I'm keeping all these kernels since in the older one virtualbox is working
what I'm doing wrong?
thanks for the help Walter
On 09/22/2010 12:01 PM, Walter Cazzola wrote:
Dear Fedorians, I'm a new user of fedora 13 and I use a virtualbox installation on it.
For what its worth, I'm running 2.6.34.7-56.fc13.x86_64 with upstream (i.e. cisco repository, not the OSE version) virtualbox with dkms - and have no problems whatsoever.
gene
On Wed, 2010-09-22 at 18:01 +0200, Walter Cazzola wrote:
Unfortunately the last two kernel upgrades (2.6.34.6-54 and 2.6.34.7-56) didn't correspond to an upgrade of the kernel modules necessary by virtualbox (vboxdrv, vboxnetflt, and vboxnetadp); this impedes the normal behavior of virtualbox.
Did you try running "service vboxdrv setup"? That should cause it to build kernel modules for the running kernel. I have to do this every time I do a kernel update.
--Greg
On Wed, 22 Sep 2010, Genes MailLists wrote:
On 09/22/2010 12:01 PM, Walter Cazzola wrote:
Dear Fedorians, I'm a new user of fedora 13 and I use a virtualbox installation on it.
For what its worth, I'm running 2.6.34.7-56.fc13.x86_64 with upstream (i.e. cisco repository, not the OSE version) virtualbox with dkms - and have no problems whatsoever.
I'm available to change to cisco version as well, do you have a yum repository to share?
Walter
On Wed, 22 Sep 2010, Greg Woods wrote:
On Wed, 2010-09-22 at 18:01 +0200, Walter Cazzola wrote:
Unfortunately the last two kernel upgrades (2.6.34.6-54 and 2.6.34.7-56) didn't correspond to an upgrade of the kernel modules necessary by virtualbox (vboxdrv, vboxnetflt, and vboxnetadp); this impedes the normal behavior of virtualbox.
Did you try running "service vboxdrv setup"? That should cause it to build kernel modules for the running kernel. I have to do this every time I do a kernel update.
unfortunately I can't do, when I try I get:
service vboxdrv setup
vboxdrv: unrecognized service
Walter
On 09/22/2010 01:04 PM, Walter Cazzola wrote:
On Wed, 22 Sep 2010, Greg Woods wrote:
On Wed, 2010-09-22 at 18:01 +0200, Walter Cazzola wrote:
Unfortunately the last two kernel upgrades (2.6.34.6-54 and 2.6.34.7-56) didn't correspond to an upgrade of the kernel modules necessary by virtualbox (vboxdrv, vboxnetflt, and vboxnetadp); this impedes the normal behavior of virtualbox.
Did you try running "service vboxdrv setup"? That should cause it to build kernel modules for the running kernel. I have to do this every time I do a kernel update.
unfortunately I can't do, when I try I get:
service vboxdrv setup
vboxdrv: unrecognized service
Walter
Try
/etc/init.d/vboxdrv setup
If that works, then chkconfig has forgotten about VirtualBox, so
chkconfig --add vboxdrv
On 09/22/2010 01:03 PM, Walter Cazzola wrote:
On Wed, 22 Sep 2010, Genes MailLists wrote:
On 09/22/2010 12:01 PM, Walter Cazzola wrote:
Dear Fedorians, I'm a new user of fedora 13 and I use a virtualbox installation on it.
For what its worth, I'm running 2.6.34.7-56.fc13.x86_64 with upstream (i.e. cisco repository, not the OSE version) virtualbox with dkms - and have no problems whatsoever.
I'm available to change to cisco version as well, do you have a yum repository to share?
Walter
Oracle, not Cisco.
$ cat VirtualBox.repo [virtualbox] name=Fedora $releasever - $basearch - VirtualBox baseurl=http://download.virtualbox.org/virtualbox/rpm/fedora/$releasever/$basearch enabled=1 gpgcheck=1 gpgkey=http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc
On Wed, 22 Sep 2010, Steven Stern wrote:
Did you try running "service vboxdrv setup"? That should cause it to build kernel modules for the running kernel. I have to do this every time I do a kernel update.
unfortunately I can't do, when I try I get:
service vboxdrv setup
vboxdrv: unrecognized service
Try
/etc/init.d/vboxdrv setup
If that works, then chkconfig has forgotten about VirtualBox, so
chkconfig --add vboxdrv
unfortunately it doesn't:
/etc/init.d/vboxdrv setup
/etc/init.d/vboxdrv: Command not found.
Walter
On 09/22/2010 01:13 PM, Walter Cazzola wrote:
On Wed, 22 Sep 2010, Steven Stern wrote:
Did you try running "service vboxdrv setup"? That should cause it to build kernel modules for the running kernel. I have to do this every time I do a kernel update.
unfortunately I can't do, when I try I get:
service vboxdrv setup
vboxdrv: unrecognized service
Try
/etc/init.d/vboxdrv setup
If that works, then chkconfig has forgotten about VirtualBox, so
chkconfig --add vboxdrv
unfortunately it doesn't:
/etc/init.d/vboxdrv setup
/etc/init.d/vboxdrv: Command not found.
Walter
Try removing the OSE edition and installing from the Oracle repo.
Walter Cazzola wrote:
I'm a new user of fedora 13 and I use a virtualbox installation on it.
VirtualBox is not Fedora software.
Please post your message on the RPMFusion mailing list[1].
Off-topic: The problem is because you are using a kmod, which does not automatically update when you update the kernel. This is a problem with kmod. Tell RPMFusion to switch away from kmod/akmod completely and use DKMS.
[1] http://lists.rpmfusion.org/mailman/listinfo/rpmfusion-users
--- On Wed, 9/22/10, Walter Cazzola cazzola@dico.unimi.it wrote:
On Wed, 22 Sep 2010, Greg Woods wrote:
On Wed, 2010-09-22 at 18:01 +0200, Walter Cazzola
wrote:
Unfortunately the last two kernel upgrades
(2.6.34.6-54 and 2.6.34.7-56)
didn't correspond to an upgrade of the kernel
modules necessary by
virtualbox (vboxdrv, vboxnetflt, and vboxnetadp);
this impedes the
normal behavior of virtualbox.
Did you try running "service vboxdrv setup"? That
should cause it to
build kernel modules for the running kernel. I have to
do this every
time I do a kernel update.
unfortunately I can't do, when I try I get:
>service vboxdrv setup vboxdrv: unrecognized service
Do you have the dkms package installed on your system? With it a new vbox kernel module should automatically be rebuilt when the kernel is updated. I have it installed on my Fedora 12 64-bit system and it works just fine. Of course, you'll need to have gcc, kernel-headers, includes, etc. for it to work.
This may help:
http://www.virtualbox.org/manual/ch02.html#id2649309
Also, installing the VirtualBox repo will help, too, but it's not necessary. I have it turned off on my system, since I only use VBox for testing and evaluating OSes and software. So, I don't really need the latest release.
B
On 09/22/2010 11:01 AM, Walter Cazzola wrote:
Dear Fedorians, I'm a new user of fedora 13 and I use a virtualbox installation on it.
Unfortunately the last two kernel upgrades (2.6.34.6-54 and 2.6.34.7-56) didn't correspond to an upgrade of the kernel modules necessary by virtualbox (vboxdrv, vboxnetflt, and vboxnetadp); this impedes the normal behavior of virtualbox.
Running yum update I simply get the message that everything is up to date.
hi,
seems which your machine don't have installed the kmod metapackage for VirtualBox-OSE: kmod-VirtualBox-OSE-3.2.6-1.fc13.8.x86_64 try the following 2 steps:
yum reinstall kmod-VirtualBox-OSE yum update
that will be install the kmod for the latest kernel if don't work use: yum install kmod-VirtualBox-OSE-2.6.34.7-56.fc13.x86_64-3.2.6-1.fc13.8 to manually install the kmod for the current kernel as the today
if the two first steps works, always when update the kernel look if a kmod for VirtualBox will be installed if isn't the case, wait one or two days to update the kernel, the kmod lags sometimes.
regards,
Gabriel
On Wed, 22 Sep 2010, Patrick Bartek wrote:
Do you have the dkms package installed on your system? With it a new vbox kernel module should automatically be rebuilt when the kernel is updated. I have it installed on my Fedora 12 64-bit system and it works just fine. Of course, you'll need to have gcc, kernel-headers, includes, etc. for it to work.
I've it but in the last two updates it didn't work, I don't know why. gcc, and headers are installed as well.
This may help:
I'll give a look
Also, installing the VirtualBox repo will help, too, but it's not necessary. I have it turned off on my system, since I only use VBox for testing and evaluating OSes and software. So, I don't really need the latest release.
this is also my case but if you update the kernel it is not working anymore since it doesn't recreate the modules.
Walter
Dear Gabriel,
On Thu, 23 Sep 2010, Gabriel Ramirez wrote:
seems which your machine don't have installed the kmod metapackage for VirtualBox-OSE: kmod-VirtualBox-OSE-3.2.6-1.fc13.8.x86_64 try the following 2 steps:
yum reinstall kmod-VirtualBox-OSE yum update
you perfectly got the sign, kmod-VirtualBox-OSE wasn't installed once installed everything is back at work as previously
Thanks
Walter
-
Gabriel Ramirez -
Genes MailLists -
Greg Woods -
Michael Cronenworth -
Patrick Bartek -
SternData -
Walter Cazzola