Virtual machines, development boards, notebooks connected to each other

Compared to the feeling of heartbreak, the Development Board mounted virtual machine in the file system has been working normally, do not know how, today is how they are not successful, wasted fast two hours to fix, finally found is a very funny problem, Perhaps recently modified a network configuration file so that my virtual machine can be online cause my auto eth3 into a ifupidown eth3 and can not be edited, how the Cup, the current personal think for this reason caused by the mount is not successful.

Now let's share with you how to kill this Ifupidown, hang-na ...

1. Modify/etc/dbus-1/system.d/networkmanager.conf (requires root permission to modify system files)

The following red words, if you deny, change the
<policy context= "Default" >
<allow own= "Org.freedesktop.NetworkManager"/>

<allow own= "Org.freedesktop.NetworkManagerSystemsettings"/>
<allow send_destination= "Org.freedesktop.NetworkManager"/>

<allow send_destination= "Org.freedesktop.NetworkManagerSystemsettings"/>
</policy> If you are afraid of anything else, you can replace all of the deny in this file with allow

2. Restart Dbus

Sudo/etc/init.d/dbus Restart OK, now look at my network, finally normal

3, three mutual ping

Now, let's share with you my three-way setup process:

Development tools: 2440 Development Board, host system Win7, virtual machine system ubuntu9.10, crossover network cable One (remember is the crossover cable Oh, learning to calculate should know, I have been confused why some people must use a router to achieve the Development Board and Virtual machine and host network interoperability. But take my this way has a flaw, is the physical network port is occupied, and the wireless card must be disabled, so is the computer can not surf the internet ah, whining ... ）

Note: Disable all but the physical network card, and use the crossover cable, the following one or two steps is the key OH

<1> set up your virtual machine as a bridge, this will not be mentioned, I believe it is an embedded people should know it

<2> set up the virtual Machine Network Editor: Edit->virtual Networks editor->host Virtual network MAPPING->VMNET0 for your computer's physical network card, as shown in the figure:

<3> the next step is to set the host's IP

IP of the virtual machine:

Development Board of the Ip:ifconfig eth0 192.168.1.17

<4> Network Interoperability testing, can be seen three are beautiful and interconnected, the cause of the incident I will not give you screenshots