Page 1 of 1

vm not start due network interface problem

Posted: 17. Aug 2016, 19:57
by Iko Pender
previously i had a linux mint running on my thinkpad and i had a windows 10 guest system.
since i planned to install fedora, i exported the win10 creating an *.ova file.

after the fedora installation i have imported the *.ova file using the "reinitialize all network cards" option (i tried also without but the same).
It is the same notebook, even the interface names are the same as with the old mint installation
but when i try to start the virtual machine following error msg appears:

Could not start the machine because the following physical network interfaces were not found: wlan0 (adapter2)

can anyone help me with this issue?

thanks in advance,
iko

Re: vm not start due network interface problem

Posted: 17. Aug 2016, 20:04
by mpack
The hardware doesn't name devices, the OS does. So the fact that it's the same hardware doesn't say that the same named NIC is available on both. If VirtualBox is telling you that interface doesn't exist, I think you can be pretty sure that it doesn't exist.

It should be easy enough to fix: just go into the VM's network settings and bridge to a NIC that does exist.

Before saying more I'll wait for the VM log: With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.

Re: vm not start due network interface problem

Posted: 17. Aug 2016, 22:57
by Iko Pender
hi mpack, thanks for your support.
i found someone having the same issue: i had to disable usb support.
after that the vm just started as usual, and i could reenable the usb supprt after restart.
problem solved. thankx!!!

Re: vm not start due network interface problem

Posted: 18. Aug 2016, 07:55
by socratis
Iko Pender wrote:i found someone having the same issue: i had to disable usb support.
????
Unless your "wlan0 (adapter 2)" is a USB adapter, it does not compute. Even then, there is something missing from the story. Do you mind posting a link to that "someone" that had the same issue?