Tag Archives: virtualbox

Description and temporary solution of VirtualBox 5.0. X unable to connect to Internet after installation

Operating system: win7 64 bit ultimate

VirtualBox version: 5.0.0 ~ 5.0.4 (the latest version)

Fault phenomenon:

After installing VirtualBox, you can’t connect to the Internet. Disable virtualboxndis6 bridged networking driver in the network card properties, and disable the network startup. The system can access to the Internet

Start the virtual machine and find that there is no adapter available in bridge mode (because it is disabled by us)

Re enable ndis6 driver (host computer can’t be connected to the Internet), add bridge mode network card to the virtual machine, and start the virtual machine. At this time, the host computer can also be connected to the Internet, but we can’t open a virtual machine every day for networking

Online search, the information is 5.0 version of the network support for win10 is very poor, engineers are trying to solve the problem of win10 compatibility, win7, win8 also some people respond to network related problems, some people reply to the problem to continue to use ndis5 driver method, try to solve the problem

Methods: download a version of VirtualBox 5.0 (version 5.0.4 tested by myself), uninstall the installed version 5.0 (upgrade directly to cover the untested version, and uninstall the software generally will not lose the built virtual machine. For the sake of security, you should choose whether to back up the system first), open the CMD command line, Install program with parameters: virtualbox-x.x.x-yyy- Win.exe -msiparams NETWORKTYPE=NDIS5

Then the normal graphical interface installation will be opened. After the installation, the network card properties will be displayed. The bridge driver name has no ndis6

We look forward to the official solution of ndis6 and the early use of a better driver

Reference:

https://www.virtualbox.org/ticket/14457

https://forums.virtualbox.org/viewtopic.php?f=6& t=68980

Resolve VirtualBox error: “fat: no bootable medium found!”

I was installing win10 virtual machine with VirtualBox in unbuntu16.04. I encountered the above problems, and the solutions on the Internet were all wrong. Similar to the following question.

My solution is to put the IOS files you need to load forward as far as possible when allocating the CD-ROM ports, followed by. DVI.

The problem of personal test can be solved.

fatal:No bootable medium found! System halted

It means

Fatal: not found in boot! Crash

First, the system may be forced to shut down before the installation is completed

The second root operation is to delete system files

Third, improper use habits, should let the system shut down normally rather than directly point x forced shutdown

Reason: the image file system could not be found, and the image file could not be found
in the system

In fact, it’s very simple. Select the corresponding system, and then click settings. Operate according to the figure below, click OK, and then start