[]FreeBSD Sharing network set up under vmware Vmware FreeBSD5.3 installed in the software installed because of the port (port is a great invention) , Very simple. However, after installing the software End, set up the network, and the problem for a long time. Online help, discovered Many people have asked this kind of question, some people here do not provide the answer handy, but themselves. Following is the prepared The memorandum. 1, started the process of setting up the network interface. In FreeBSD, the operating system will be automatically activated when it /usr/local/etc/rc.d/001.vmware.sh Script months through /usr/local/etc/vmware/config the configuration file to set up a network interface, the interface Named : vmnet1. It should pay attention to the following : 1) vmware need aio, if_tap, netgraph, ng_ether, ng_bridge these kernel module, Either they are translated into a kernel, or to set up NO_MODULES=YES not /etc/make.conf (translated as He modules can accelerate the process of editing kernel). 2) I vmware3.2.1 in the process of installing the first /usr/local/etc/rc.d/001.vmare.sh 26 acts : networking=. In the script of this operation will result in a "-eq" computation wrong. I think I might be What place does not set, the port may be wrong. However, no matter what names the grindstone. Networ read : King=1. 3) in accordance with pkg-message Thus, the installed in /etc/sysctl.conf : kern.ipc.shm_allow_rem Oved=1, otherwise there will be a "shared memory segment : Invalid argument.Failed Didtinction attach t O initialize SVGA device. "Mistake. 4) In addition, the launch will include vmware carrying the script and vmmon_up.ko vmnet.ko, three rtc.ko Kernel modules. Here, the most successful one. At this moment, if you look at the use ifconfig, should be able to see this vmnet1 The network interface. You do not see that needs attention is vmnet1 IP addresses, and because IP addresses only vmware this vmnet1 Software can be "invisible" to see, it does not use ifconfig to set up IP addresses. I tried to do after you do not know what will be the consequences. 2, the vmware is how to set up the network. Vmware /usr/local/etc/vmware/config to basically set up through the network. Said "basic" In fact, it is because there are other ways, it seems that in FreeBSD to no avail. In configure document, the network set up (We instructive to worry about) has four lines : Vmnet1.Bridged = "yes" Vmnet1.BridgeInterface = "rl0" Vmnet1.HostOnlyAddress = "0.0.0.0" Vmnet1.HostOnlyNetMask = "255.255.255.0" . " "Vmnet1 front of the installed network interface is intended to indicate which, if you want to set up a number of interface Can copy some of this wealth, for instance into vmnet0, vmnet2 : :. But vmnet1 particularly important. It is one VMware is running the DHCP network interface; Vmware on the other hand, because if you set up the ethernet adapter Host Bridge, or when the only choice, then it is also the acquiescence vmnet1. Vmware operation of the illusions you in your journey began when vmware to set up the network is : 1) If you choose the Bridge, vmware bear ~/.vmware/config According to the document : Vmnet1.Bridged = "yes" Vmnet1.BridgeInterface = "rl0" To set up. 2) If you choose only the Host, based on : Vmnet1.HostOnlyAddress = "0.0.0.0" Vmnet1.HostOnlyNetMask = "255.255.255.0" To set up. 3) If you choose the custom option and then under /dev/vmnet1 : vmnet1.Bridged = "yes" Vmnet1.BridgeInterface = "rl0" Vmnet1.HostOnlyAddress = "0.0.0.0" Vmnet1.HostOnlyNetMask = "255.255.255.0" To set up. This is a very good understanding of the meaning of a few lines that do not have an interpretation. 3, how to set up access to the Internet which allow vmware With the above foundation, like the other understood. FreeBSD to the commencement of operation of /usr/local/etc/ Rc.d/001.vmware.sh vmnet1 have a good set up for us. Although the operation will be in operation when ~/.vmwar vmware E/config paper, but since the start of vmnet1 set up good, you can not change your approach to fit RO Otazky things? So if you choose custom and choose /dev/vmnet1 in vmware, then in /usr/local/et C/vmware/config directly to place it well. Now and then talk about the different meanings three models (vmnet1 example). 1) Bridge : For example, you say vmnet1 and rl0, fxp0 is an equal and the network can use the DH CP services, NAT services. This is a model used by ordinary people the most. You have fully equivalent to another machine with Like your FreeBSD in the same LAN. Configure the document was like this : Vmnet1.Bridged = "yes" Vmnet1.BridgeInterface = "rl0" Vmnet1.HostOnlyAddress = "0.0.0.0" Vmnet1.HostOnlyNetMask = "255.255.255.0" It may be that you only need to change "rl0" and the network adapter bridging the equipment used to read your name on it. However, we must note is : vmnet1.HostOnlyAddress = "0.0.0.0" that the word "0.0.0.0." This Custom+/dev/vmnet1 : to be installed in the vmware installed. If you choose : the bridge is here so you should set up an effective IP addresses, like the Host mode only, I do not know why, said vmware - Ming said. I first method is used. 2) Host vmnet1 only mode : This is another subset of the network, not in a sub-network with FreeBSD 。 Vmnet1.Bridged = "NO" Vmnet1.BridgeInterface = "" Vmnet1.HostOnlyAddress = "192.168.21.1" Vmnet1.HostOnlyNetMask = "255.255.255.0" 3) custom in this model : 1) has said. 4, the final run my operation : 1) Delete ~/.vmware/config paper, because there is no use, it may make trouble. 2) /usr/local/etc/vmware/config installed : Vmnet1.Bridged = "yes" Vmnet1.BridgeInterface = "rl0" Vmnet1.HostOnlyAddress = "0.0.0.0" Vmnet1.HostOnlyNetMask = "255.255.255.0" 3) amend section 26 /usr/local/etc/rc.d/001.vmware.sh re : networking=1 4) restart machines (FreeBSD). 5) start vmware, wow! ! ! ! ! []FreeBSD Sharing network set up under vmware [quote][i] Note from the original "newsim" [/i] released : Vmware FreeBSD5.3 installed in the software installed because of the port (port is a great invention) , Very simple. However, after installing the software End, set up the network, and the problem for a long time. Online help, discovered Many people have asked this kind of question, some of the answers? . . . . . . . . . [/quote] Em03 em03 : : : : : : em03 []FreeBSD Sharing network set up under vmware Newsim greatly, Hello. There are two questions to ask on the vmware! I used to the freebsd 4.10, vmware 3.x series of ports is installed, normal, the Internet can be. No. 1 : at the beginning of the installation of the document must add /etc/sysctl.conf Kern.ipc.shm_allow_reoved=1 otherwise would occur when loading on the power svga wrong! No. 2 : I will stop when the vmware hits full-screen images in full-screen, then soft lockup, do not want to switch (I can only engage in the context used in the virtual machine, freebsd is a missile). Still operating machinery can be seen, but the keyboard, mouse, all the ineffective Is there a solution? Note : I was CLIENT virtual, vmtools also installed! []FreeBSD Sharing network set up under vmware In fact, I do not necessarily understand the vmware. On the full-screen, full-screen death since I once, coupled with the terrorist /usr/local/share/doc/vmware description of the situation, I no longer dared to use the full screen. Another problem you, I do not know how the case. In /usr/local/share/doc/vmware/Hints.FreeBSD is this : - Full screen text mode does not work. Don 't ever do it! - Full screen mode GPU will work, but you have to be careful eg When running a DOS prompt on MS Windows. Hitting Alt+Enter will crash VMware before you can say "Chuck!" []FreeBSD Sharing network set up under vmware Ports can be installed directly now! In which catalog? []FreeBSD Sharing network set up under vmware The plan here is not []FreeBSD Sharing network set up under vmware Newsim, is FreeBSD 5.3 ACPI and vmware3 conflict? I originally was using the 4.10, the installation vmware3 no problem, but now acpi start in 5.3 above, sometimes mainframe virtual lock. Are we can use to close acpi vm? Newsim you installed over the shorter version 4.X not, would there be this problem? []FreeBSD Sharing network set up under vmware I also installed is not even installed! Have to make, make install following is the result, we look to help, thank you! # Make install Installing for vmware3-3.2.1.2242_10,1 ===>; ===>; Vmware3-3.2.1.2242_10,1 depends on file : /dev/rtc-not found ===>; Verifying install for /dev/rtc in /usr/ports/emulators/rtc ===>; Building for rtc-2004.02.24.1_4 "/usr/src/sys/conf/kmod.mk", Line 215 : warning : duplicate script for target "@" ignored Make : not specified 't know how to make/tools/vnode_if.awk. Stop *** Error code 2 Stop in /usr/ports/emulators/rtc. *** Error code 1 Stop in /usr/ports/emulators/vmware3. *** Error code 1 Stop in /usr/ports/emulators/vmware3. 3Q! []FreeBSD Sharing network set up under vmware Acpi closed without you? ? First make deinstall before reopening option 2 Without ACPI Make install again! []FreeBSD Sharing network set up under vmware ACPI closed the set back on the past, what are the consequences ah? I have not installed and not installed after the operation that! 3Q! []FreeBSD Sharing network set up under vmware Oh really not what I and ACPI is now installed on the issue rather than the use of the findings and issues like the previous one! Please! Help! [ Closed window ]