Vmware Server installation notes for Linux and Windows

Normal07.8 Pound 02falsefalsefalseEN-USZH-CNX-NONEMicrosoftInternetExplorer4 Linux and Windows Vmware Server Installation Notes 1. Install VMware Server under Linux

Tar package installation: (Assuming the installation package is placed in the /tmp directory

# cd/tmp

# tarzxvf VMware-server*.tar.gz Enter the decompression directory # cdvmware-server-distrib Enter the decompressed directory and run the install command # ./vmware-install .pl Ok. The installation process is to set the path information, network information, etc., basically all of the default can be, or can be modified according to the actual situation. The easiest problem in the installation process is to choose the kernel step. The step requires you to select the source file directory of the kernel. If the source file of the kernel is not installed on this machine, it seems that you cannot install the vmware server. I am in several cases. The version of Linux has been installed on this, and several times it has been unsuccessful in the installation of life and death! All because of the kernel problem! The installations have been installed on Redhat EL5 in recent times, and they are all running smoothly! Basically, all the way to enter the button to complete the installation! I have been using version 1.0.8 recently, this version is still stable! Temporarily too lazy to change ~~~~ Recently playing other virtual machine software ~~~~ Tar package uninstall: # vmware-uninstall.pl Rpm package installation: (assuming the installation package is placed in the /tmp directory) # cd/tmp # Rpm –ivh After the VMware-server*.rpm installation is complete, run the configuration file. # vmware-config.pl Ok. The configuration process is the same as the tarball installation. Rpm package uninstall: # rpm -e VMware-server* 2, start and stop vmware service # service vmware start # service vmware stop 3. Use VMware Server Console: Under Linux graphical interface console: Create a new terminal window: Enter # vmware command , you can open the vmware console window, the method is basically the same as windows. Use console under windows: Select Localhost, click OK to access the local virtual machine. Select Remote host, fill in Hostname: If it is a Windows host, fill in the IP directly; if it is a Linux host, fill in the IP: Port Username: Fill in the username of the login host system Password: User password Common view port command: Use the command in the terminal under Linux # netstat –nat Windows under the dos command line #netstat -a FAQ: 1: When accessing a remote host fails, sometimes it may be blocked by the firewall ~~~ Try to turn off the windows firewall. 2: Sometimes the virtual machine can't be started. In addition to checking whether the port is started by using the netstat command, it is also necessary to check whether several services related to vmware are started! Whether it is under Windows or under Linux, some services will automatically close when they fail. If the restart still does not solve the problem! If it is under linux, you can choose to re-execute #vmware-config.pl and reconfigure all settings. If it still doesn't work, restart the machine. If it still can't be solved, then delete the software directly and reinstall it! Be careful not to delete the installed virtual machine! The default is not deleted! 3: Sometimes after the virtual machine is copied or moved, if there is an error that cannot open the .vmx file, check the directory permissions. If it still doesn't work, you can click the button Defragment in the hard disk settings in the virtual machine settings to reassemble the hard disk! If it still fails, you can only see the RP value, haha ​​~~~ 3, and sometimes, when you first create a virtual machine, the allocated disk space is small! Space is taking up when you use it! This kind of situation is generally no way to solve it, only reload! However, it seems that if you have not done a snapshot, you can modify the size of the .vmx file by command! I have not tried it yet! The last time I encountered this problem, I just caught up with a snapshot, and I got a virtual machine to try again someday! Ha ha! I rarely encounter situations where space is not enough, so I can't remember to do this test!