Many people say that virtual machines are not easy to manage because we don't have a good grasp of the use of virtualization techniques. Today, we'll look at three Linux VMware Workstation usage tips.
VMware Workstation Use Tips First, the realization of VMware Bridge wireless network card, no longer limited to the use of NAT
Environment: Host for Ubuntu8.04_amd64,vmware workstation 6.0.x
The use of VMware under Ubuntu (in fact, in the case of Linux as a host) has been the subject of two recognized problems: one is the problem of a sound card; the other is the problem of bridging the wireless network card. On the solution online discussion is much more, but by the way I have not been able to solve the online, plagued me for a long time (so I have been using NAT way to share Wi-Fi with host hosts, but some applications have problems). About bridging the wireless network card problem I finally figured out and solved today, write here so as not to let more later people waste time.
Problem Description: Use VMware under Linux, if the host is using a wireless network card, the client network card if the use of bridge can not connect. According to the VMware Forum, the result is that if the host is Windows, there is no problem, because the driver supports the wireless card as the AP mode of work, under Linux 99%. After practice, I find that it can be solved, and it takes two steps:
1, modify one of the files, and then recompile. Related patch files are attached.
2, the client's network card configuration is not selected bridge, but according to VMware Run config when the hint is the wireless network card bridge on which device, the corresponding selection of custom (note: Not selected bridged bridge mode, otherwise impossible to connect.) It was a mistake that I had made with other people in the past. , and then select the appropriate device from the Drop-down list, such as Vmnet2 is bridged to wlan0 on my machine, so select Vmnet2.
Second, host for Linux, client also for Linux, how to switch virtual terminals in the client?
Host and client are Linux situations, if you want to switch virtual terminals in the client, what to do? If you still use CTRL+ALT+F1-F7 you will find that you can only switch the host, if you want to switch in the client to use ctrl+alt+ space, loosen the space and then press F1-F7 (note: Ctrl+alt can not loose), which can be switched to the corresponding virtual terminal in the client.
Third, how to increase the virtual network card?
In Linux as a host, unlike Windows host will automatically all the virtual network card built, but generally only built 2-3 virtual network card, such as Vmnet0, Vmnet1, Vmnet8, if there are two bridges will have vmnet2. If you want to build an experimental network is often not enough, but also need other virtual network card to do?
Method is: (To add vmnet5 as an example)
Modify the/etc/vmware/locations file at the beginning of the file:
Answer Networking Yes
Answer Vnet_0_interface Eth0
Answer Vnet_8_nat Yes
Answer Vnet_8_hostonly_hostaddr 192.168.63.1
Answer Vnet_8_hostonly_netmask 255.255.255.0
Answer Vnet_1_hostonly_hostaddr 192.168.95.1
Answer Vnet_1_hostonly_netmask 255.255.255.0
Add the other vmnet. If NAT service is required, it is defined as answer Vmnet_5_nat Yes and added directly if NAT is not required:
Answer Vnet_5_hostonly_hostaddr 192.168.64.1
Answer Vnet_5_hostonly_netmask 255.255.255.0
After/etc/init.d/vmware restart, you can find that/dev/vmnet5 already exists, and the new VMNET5 interface can be found after ifconfig.
The above is the entire content of this article, I hope to help you learn, but also hope that we support the cloud habitat community.