Date: Sat, 25 Nov 2000 10:11:10 -0800 From: Bill Schoolcraft <bill@wiliweld.com> To: Krzysztof Parzyszek <kparz@iastate.edu> Cc: Tim McMillen <timcm@umich.edu>, freebsd-questions@FreeBSD.ORG Subject: Re: VMware for FreeBSD ? Message-ID: <3A2000BE.AB11581F@wiliweld.com> References: <Pine.SOL.4.10.10011240040001.19690-100000@joust.gpcc.itd.umich.edu> <3A1E015F.5588E6E5@wiliweld.com> <20001124023630.B7169@buchanan-181-249.stures.iastate> <3A1ECB09.FDF4CDB8@wiliweld.com> <20001124155657.A10072@buchanan-181-249.stures.iastate> <3A1F1471.B5A7F7D4@wiliweld.com> <20001124211929.A12645@buchanan-181-249.stures.iastate> <3A1F5CEC.DF2DDD63@wiliweld.com> <20001125012627.A44419@buchanan-181-249.stures.iastate>
next in thread | previous in thread | raw e-mail | index | archive | help
Krzysztof Parzyszek wrote: > > Ok, I have figured something out. VMware stores its configuration > files in /etc/vmware/ I was able to force vmware to display this > message by putting a file `not_configured' in that directory. > Removing it brought the usual behavior back (i.e. it was working > again). My next guess would be to look for file `not_configured' > in the vmware config directory and remove it. > > As I said, in my case vmware stores it's config stuff in > /etc/vmware (it is itself a symbolic link). > > $ ls -l /etc/vmware/ > total 1 > -rw-r--r-- 1 root wheel 344 Oct 20 02:52 config > lrwxr-xr-x 1 root wheel 21 Oct 19 12:17 vmware -> /usr/local/etc/vmware > > If you don't have the file `config', here are contents of mine. If you use > it, make sure the directories are valid. > > $ cat /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/lib" > vmnet1.HostOnlyAddress = "192.168.1.1" > vmnet1.HostOnlyNetMask = "255.255.255.0" > > I hope this helps. Yes that did. "NOW", I can open the VMware Workstation but I get two error screens. The second error screen appears after I close the first error screen GUI. Upon running the `vmware` command from a terminal window in both KDE and Gnome the error states: (first error screen) CANNOT OPEN VMWARE WORKSTATION EXECUTABLE FILE. POSSIBLY AN ISTALLATION ERROR. MODULE 10 INITIALZATION SUCCEEDED. (second error screen) CANNOT OPEN /dev/tty0 NO SUCH FILE OR DIRECTORY. VIRTUAL TERMINAL INITIALZATION FAILED. PERHAPS YOUR KERNEL IS NOT CONFIGURED FOR VIRTUAL TERMINAL SUPPORT. The strange thing is that I can see the VMware workstation in the background, the error gui's are on top of the normal VWware workstation. It disappears along with the last error window though. The next command line error occurs when I was trying to run the `vmware-wizard` command from within a terminal window in KDE. (I tried all this is gnome too, same stuff) (begin command) [root@FreeBSD /etc/vmware]--> vmware-wizard Application initialization failed: no display name and no $DISPLAY environment variable. Could you share what your `echo $DISPLAY` says ? The complaint that /dev/tty0 seems to be a Linux related error for as the error states I have no /dev/tty0, nor can I find the file that has that value set. Thanks. -- Bill Schoolcraft PO Box 210076 San Francisco, CA 94121 "UNIX, A Way of Life !!!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A2000BE.AB11581F>