VMware Network Configuration Instance Die WINDOWS HOST Linux Guest Preface: A case written in a VMware in the past few days, mainly about Linux Host Windows Guest (http://bbs.chinaunix.net/forum/Viewtopic.php ? T = 367907 & highlight = yunqing), suitable for friends who often run Linux and regard Windows as a secondary industry. After the release, the reaction was not big, and later found that the friends in the jar made Windows Host's race in Linux Guest, and there were many posts to talk about network problems, they didn't think so hard, I tried it, let the process write down hope Friends having problems with problems are helpful. Copyright Yunqing all, the first chinaunix.net, please include this line declaration text: I am using the VMware Workstation 4.52, the Host machine is running Windows XP Professional, if you are still making VMware Workstation 4.0 recommended to download an upgrade package, However, I don't think even if I don't do any problems. 1. Install VMware Workstation, very simple, all the way OK, I believe that most of the friends have already been installed. 2. Create a new Guest system. Choose a type. Because I do the most of the most problem, I choose Redhat Linux, choose Custom, and select Hostonly (if you have already installed, NAT or Bridge doesn't matter, change in the virtual machine properties. Hostonly is OK.) 3. Start the virtual machine after creating, insert the first disk where RH9 is installed. Choose custom installation, I only retain Gonme, X, and Graphical Internet, save installation space and time. 4. The installation process is smooth, no problem, restart the virtual machine after completion, found that when updating FSTAB, it is estimated that it is time to connect to the CDROM live floppy disk. Kill offs the virtual machine, change the settings, clear the AutoConnect When Power ON of the CD-ROM and floppy disk. Restart the virtual machine, no problem, enter the last setting, sound card, and graphical interfaces. 5. Follow the requirements of VMware-Tool in the virtual machine, better support for mouse and graphics. If you are on the graphical interface, you first switch to text mode. Right click on the desktop, open a terminal in the terminal: Su # / sbin / telinit 3 graphical interface disappears, knock back to the car, log in in text mode. Select VM-> Install VMware Tools in Windows VMware in Virtual Machine: Su Mount / DEV / CDROM / MNT / CDROM CD / TMP TAR ZXF / MNT/VMware-Linux-Tools.tar.gz CD VMware-Tools -distrib ./vmware-install.pl answer and sets the screen resolution, in addition to the resolution needs to be selected, it will be used directly. Return to the default graphical interface (Run Level 5) / Sbin / Telinit 5 6. Log in to the virtual machine, open a terminal: / sbin / ifconfig Discovery Eth0 does not come. do not panic.
------------ The following is Network settings --------------- 7. To Windows XP, view all network connections, you should find that more VMNet1 and VMNet8 are available in addition to the original NIC. If you look at the manual, you should know that VMNet1 is the interface of Hostonly, and VMNET8 is a network interface using NAT. Here we don't want to use VMware, you don't want to use his NAT so we know that VMNET1 will talk about IDEA before further operation: We will use the Hostonly network interface to connect virtual machines and hosts, then use Windows XP / 2000 The INTERNET connection sharing inside (actually a simple routing NAT) to allow the virtual machine to access the external network through the original NIC. So why don't you use a bridge? I have some discussion in the previous article (Linux Host Windows Guest), please refer to. However, the most real reason is that the bridge requires a different independent IP address different from the original host, which is more difficult for some cases (IP and Mac binding, network management disagree). OK, Let's Go (1) View the properties of your connection network card, select the Advanced tab, set to allow sharing, and set the allowed network interface to VMNET1, as shown below. (2) Insert a look at your VMNet1, look at the TCP / IP protocol settings, you have found that it has been automatically set to 192.168.0.1/255.255.255.0, as shown below. (3) The settings under Windows are completed, transferred to the virtual machine running Linux. Set your ETH0 IP address to static (if you don't have a static when install) (4) The settings under Windows are completed, transfer to the virtual machine running Linux. Set the IP address of your ETH0 to static (if there is no static when installing). Press Red Hat Icons -> System Settings -> Network (or other you understand) IP: 192.168.0.2 (or other address on this segment) NetMask: 255.255.255.0 Default Gateway: 192.168.0.1 DNS: Enter yourself DNS save settings.
