Date: Thu, 12 Oct 2000 14:32:16 -0400 (EDT) From: Vivek Khera <khera@kciLink.com> To: "Akinori MUSHA" <knu@idaemons.org> Cc: freebsd-ports@FreeBSD.org, ak@freenet.co.uk, freebsd-emulation@FreeBSD.org Subject: Re: ports/20624: vmware vmmon module locks kernel Message-ID: <14822.944.440041.256906@onceler.kciLink.com> In-Reply-To: <86itr5dzyu.wl@daemon.local.idaemons.org> References: <200009160902.CAA78123@freefall.freebsd.org> <14814.12057.18444.238865@onceler.kciLink.com> <86itr5dzyu.wl@daemon.local.idaemons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "AM" == Akinori MUSHA <knu@idaemons.org> writes: AM> I thought you meant vmware2 since someone assigned your PR to me to AM> handle. I'm sorry I cannot be of much help, but please contact AM> ak@freenet.co.uk, the vmware 1.x port maintainer, who must have an AM> environment to test your patch. Also you may want to consult AM> freebsd-emulation to find testers. (both CC'ed) Ok... I figured out how to make vmware1 work on FreeBSD. Ugly hack follows. 1) cd /usr/ports/vmware; make install 2) cd ../vmware2; make 3) pushd /usr/local/lib/vmware/lib/modules; rm *.ko; popd 4) cp work/vmware-distrib/vmmon-only/*.ko /usr/local/lib/vmware/lib/modules 5) cp work/vmware.sh /usr/local/etc/vmware.sh Now it works. Basically, you need the kernel modules from the newer VMware. The ones that come from the vmware1 port lock up the FreeBSD 4.1 kernel. I don't know how to automate this process. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14822.944.440041.256906>