Fedora Linux Support Community & Resources Center
  #1  
Old 19th February 2010, 11:32 AM
denisk Offline
Registered User
 
Join Date: Oct 2005
Location: Croatia
Age: 45
Posts: 17
linuxfedorafirefox
VirtualBox - Failed to start virtual machine

Hi,

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.
Any Ideas?
Reply With Quote
  #2  
Old 19th February 2010, 03:18 PM
josercl Offline
Registered User
 
Join Date: Feb 2009
Posts: 1
linuxsafari
i had exactly the same issue but using PAE kernel, it has something to do with vboxnetflt and vboxnetapd modules not being loaded correctly with modprobe, i had to install them manually with insmod

just run:
insmod /lib/modules/`uname -r`/extra/VirtualBox-OSE/vboxnetflt.ko
insmod /lib/modules/`uname -r`/extra/VirtualBox-OSE/vboxnetadp.ko
Reply With Quote
  #3  
Old 19th February 2010, 04:44 PM
denisk Offline
Registered User
 
Join Date: Oct 2005
Location: Croatia
Age: 45
Posts: 17
linuxfedorafirefox
thanks for the reply,
The script /etc/sysconfig/modules/VirtualBox-OSE.modules from my post does exactly that except it uses modprobe instead of insmod, but the result is same: Invalid module format

here's the script

# User is advised to run this on upgrades
/sbin/modprobe -r -b vboxnetflt &>/dev/null ||:
/sbin/modprobe -r -b vboxdrv &>/dev/null ||:
/sbin/modprobe -r -b vboxnetadp &>/dev/null ||:

/sbin/modprobe -b vboxdrv
/sbin/modprobe -b vboxnetflt
/sbin/modprobe -b vboxnetadp

---------- Post added at 05:44 PM CST ---------- Previous post was at 05:25 PM CST ----------

oops, sorry jose, you are right. insmod works!

but I could swear that it didn't work this morning . In the meantime I completely reinstalled VirtualBox and rebooted the machine.

Thanks again.
Reply With Quote
Reply

Tags
failed, machine, start, virtual, virtualbox

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Virtual Machine Manager cannot start VM ceach Using Fedora 2 14th December 2009 02:44 PM
Virtual Machine Manager: Cannot create virtual machine chris_flow Using Fedora 0 30th November 2009 03:57 PM
Virtual Machine Manager error when add a new virtual machine bizar Using Fedora 3 1st November 2009 10:37 PM
Virtual disk images (virtual box - virtual machine manager) beaker_ Using Fedora 0 2nd July 2009 01:19 PM
VirtualBox or VM Ware or Virtual Machine Mgr or....? Silverarrow Using Fedora 23 25th September 2008 09:46 AM


Current GMT-time: 02:55 (Tuesday, 16-09-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat