Date: Thu, 18 Mar 2004 09:00:23 +0100 From: Stefan Farrenkopf <sfarren@gwdg.de> To: emulation@freebsd.org Subject: Re: vmware3 problems on FreeBSD 4.9 Message-ID: <7480000.1079596823@sub00261.sub.uni-goettingen.de> In-Reply-To: <8430000.1079545827@sub00261.sub.uni-goettingen.de> References: <8430000.1079545827@sub00261.sub.uni-goettingen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, thanks to Mike, I could get vmware3 running now. I did not know that I need the "device tap" within my kernel configuration. As Mike told me, I added it and built a new kernel. To be sure that there's no confusion between my former vmware2 and the vmware3 installation I also deinstalled the vmware3 port and then removed what has been left in /dev and /usr/local/etc by hand. After I reinstalled vmware3 everything went fine. A big "thank you" to Mike again :) cheers, Stefan --On Wednesday, March 17, 2004 18:50:27 +0100 Stefan Farrenkopf <farrenkopf@mail.sub.uni-goettingen.de> wrote: > Hi, > > after all the discussion about vmware3 on 4.9 I thought it's wort to try > it. Here are the steps I made and at the end I describe the problem I > have now. > > I updated my source and applied the kernel patch, I also added VFS_AIO to > my kernel configuration file. > uname -a says now: FreeBSD 4.9-RELEASE-p4 > Then I removed vmware2 and installed vmware3 from the ports. > I answered no to netgraph binding and configured a private IP adress and > a netmask during the installation. Below you will find my config file > (/usr/local/etc/vmware/config): > > vmware.fullpath = "/usr/local/lib/vmware/bin/vmware" > wizard.fullpath = "/usr/local/lib/vmware/bin/vmware-wizard" > dhcpd.fullpath = "/usr/local/lib/vmware/bin/vmnet-dhcpd" > loop.fullpath = "/usr/local/lib/vmware/bin/vmware-loop" > libdir = "/usr/local/lib/vmware" > vmnet1.HostOnlyAddress = "192.168.254.1" > vmnet1.HostOnlyNetMask = "255.255.255.0" > > I added the following line to my /etc/sysctl.conf file: > kern.ipc.shm_allow_removed=1 > > Because of the new kernel I rebooted the machine. > > After I got back to a running system, I tried to run vmware with my > vmware2 configuration and with a new configuration where I pointed to the > existing disks (2 Virtual IDE drives). > I had a look at my vmware2 configuration and added the cdrom by hand > (/dev/adc0c). When I try to Choose this device from my /dev directory it > does not show up in the open dialog. There are instead only a few devices > with typical linux names (hda, ...). > > The main problem I have now: I don't have a working vmnet interface :( If > I PowerOn vmware it complains about the missing /dev/vmnet1. > I tried to restart the vmware components by executing > /usr/local/etc/rc.d/vmware stop/start and I had to realize that there's a > problem with the initialisation of vmnet1. Here's the output of > "vmware.sh start": > ifconfig: interface vmnet1 does not exist > and if I do a stop the same message appears. > > I removed the Host-only network interface from my vmware configuration > and bootet the win2k installation with success. I was able to install the > newer vmware tools, but I was not able to switch to full screen mode. If > I tried to nothing happened. > > Besides the missing network interface everything is fine, but without the > network I am not able to connect to the samba daemon and vmware is > useless for my application :( > > Any suggestions how to solve the problem? > > best wishes, > Stefan > > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to > "freebsd-emulation-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7480000.1079596823>