Date: Fri, 03 Nov 2000 16:01:25 +0100 From: "Georg-W. Koltermann" <gwk@sgi.com> To: freebsd-emulation@freebsd.org Cc: vns@delta.odessa.ua Subject: -stable vmware2 port on 4.1-RELEASE Message-ID: <3A02D345.285902FC@sgi.com>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
Hi,
with the vmware2 port of 4.1-RELEASE I had occasional lockups of my
machine, so I felt like upgrading to a newer version of the port.
On ftp.freebsd.org I could only find newer versions of the port targeted
at (5.0) -current and -stable. I picked -stable, since most of the time
one can use a -stable port on the latest -RELEASE version of FreeBSD.
This time I ran into problems: vmware2 would not install, "make install"
aborted and complained about a missing packing list. I corrected that
problem by moving pkg-comment pkg-descr pkg-message pkg-plist into
pkg/COMMENT pkg/DESCR etc.. Now the install complained about an
existing /etc/vmware. Well, that was only a symlink, so I removed it.
Now the install worked.
After rebooting (just to be sure the new modules are loaded) I could not
start vmware. It said linux procfs was not mounted (it actually WAS
mounted). The problem was with the check in the /usr/local/bin/vmware
script, it checked /proc/cpuinfo not /compat/linux/proc/cpuinfo. I
changed the hashbang at the start of the script to /compat/linux/bin/sh
so that the script ran in linux mode to get around that problem.
Now starting a VM in vmware said /dev/vmnet1 was not configured. I
checked the /usr/local/etc/rc.d/vmware.sh script and found that the new
version is considerably different from my old version. It loads the
if_tap module instead of the vmnet module, and also does some magic
about "sysctl -w net.link.ether.bridge_refresh". I commented out the
sysctl stuff and put a line for loading vmnet in place of loading
if_tap. Now, when configuring the vmware environment by
/usr/local/etc/rc.d/vmware.sh I could see that the vmnet1 device was
actually configured ok, but on staring the VM I still got vmnet1 not
configured. By digging further I found that the new install script
creates a /dev/vmnet1 node in /compat/linux, with some very cryptic
minor number. I removed the /compat/linux/dev/vmnet1 so that the VM
would talk directly to the FreeBSD /dev/vmnet1, and bingo, now it
worked.
Question: Do you think this setup could work reliably, or would you
rather warn me about using it?
Question: Were you aware that the -stable vmware2 port would not work on
4.1-R? Would you be willing to put a compatibility note or even a
warning message somewhere during installation, so that people who try to
use that combination are warned (maybe even include a link to this
post)?
Regards,
Georg.
--- vmware.sh Fri Nov 3 14:31:37 2000
+++ /usr/local/etc/rc.d/vmware.sh Fri Nov 3 14:54:51 2000
@@ -39,14 +39,15 @@
suffix=smp
fi
-exec >/dev/null
+#exec >/dev/null
case $1 in
start)
kldload ${vmware_libdir}/modules/vmmon_${suffix}.ko
if [ $networking -eq 1 ]; then
- sysctl net.link.ether.bridge_refresh && bridge="_bridge"
- kldload if_tap.ko
+# sysctl net.link.ether.bridge_refresh && bridge="_bridge"
+# kldload if_tap.ko
+ kldload ${vmware_libdir}/modules/vmnet.ko
if [ ! -e $dev_vmnet1 ]; then
echo "$dev_vmnet1 does not exist!" >&2
echo "Your VMware installation seems broken. Please reinstall VMware port." >&2
[-- Attachment #2 --]
begin:vcard
n:Koltermann;Georg-W.
tel;cell:+49-171-3040144
tel;fax:+49-89-46107-395
tel;work:+49-89-46108-395
x-mozilla-html:FALSE
url:http://www.sgi.de
org:SGI;PSO
adr:;;Am Hochacker 3;Grasbrunn;;85630;Germany
version:2.1
email;internet:gwk@sgi.com
title:Consultant
x-mozilla-cpt:;0
fn:Georg-W. Koltermann
end:vcard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A02D345.285902FC>