FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 05-31-2012, 02:28 PM
Paul Smith
 
Default VirtualBox cannot start on F17

Dear All,

I have just installed F17 (clean installation), and when I start my
virtual machine through VirtualBox, I get the following error:

Failed to open a session for the virtual machine WindowsXP.
Failed to open/create the internal network
'HostInterfaceNetworking-eth0' (VERR_INTNET_FLT_IF_NOT_FOUND).

Additional information:

# rpm -q VirtualBox-4.1
VirtualBox-4.1-4.1.16_78094_fedora17-1.x86_64
#

Any ideas?

Thanks in advance,

Paul
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 05-31-2012, 06:19 PM
Rohan Sheth
 
Default VirtualBox cannot start on F17

On Thu, May 31, 2012 at 7:28 AM, Paul Smith <phhs80@gmail.com> wrote:
> 'HostInterfaceNetworking-eth0' (VERR_INTNET_FLT_IF_NOT_FOUND).

As a first guess, can you try going to the VM settings -> Network and
if one of your adapters are in bridged mode try selecting the
"correct" adapter to link it to. Since the network interface rename
in Fedora I assume eth0 is no longer valid?

-Rohan
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 
Old 05-31-2012, 08:01 PM
Paul Smith
 
Default VirtualBox cannot start on F17

On Thu, May 31, 2012 at 7:19 PM, Rohan Sheth <rohan@rohansheth.com> wrote:
>> 'HostInterfaceNetworking-eth0' (VERR_INTNET_FLT_IF_NOT_FOUND).
>
> As a first guess, can you try going to the VM settings -> Network and
> if one of your adapters are in bridged mode try selecting the
> "correct" adapter to link it to. *Since the network interface rename
> in Fedora I assume eth0 is no longer valid?

Thanks, Rohan. You were absolutely right: The problem became fixed by
adjusting the

VM settings -> Network

settings.

Paul
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
 

Thread Tools




All times are GMT. The time now is 09:14 AM.

VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org