From owner-freebsd-current@FreeBSD.ORG  Wed Jul 21 16:02:17 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id E32EC16A4CF; Wed, 21 Jul 2004 16:02:17 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 92DC643D55; Wed, 21 Jul 2004 16:02:17 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i6LG1emP057294;
	Wed, 21 Jul 2004 12:01:40 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)i6LG1exo057291;
	Wed, 21 Jul 2004 12:01:40 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Wed, 21 Jul 2004 12:01:40 -0400 (EDT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Scott Long <scottl@freebsd.org>
In-Reply-To: <40FE8F81.7040409@freebsd.org>
Message-ID: <Pine.NEB.3.96L.1040721115940.56342A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: "freebsd -current@" <freebsd-current@freebsd.org>
cc: Ben Paley <ben@spooty.net>
Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jul 2004 16:02:18 -0000


On Wed, 21 Jul 2004, Scott Long wrote:

> > Additional ABI support: linux.
> > Starting cron.
> > Local package initialization:link_elf: symbol linux_ioctl_register_handler 
> > undefined
> > kldload: can't load /usr/local/lib/vmware/modules/vmnet.ko: No such file or 
> > directory
> 
> Is your linux.ko module out of date?  You have a mis-match somewhere
> here. 

Or, alternatively, the symbols exported by the Linux emulation module have
changed, and the VMware port hasn't caught up (or the local copy needs
updating).  Something is definitely out of sync, needless to say, but it
could be that the VMware module needs updating in the pseudo-vendor.

I've been wondering if we shouldn't bring the VMware modules into the base
source tree for some time -- the license is probably an issue, but VMware
is a valuable tool for development, and I'm amazed at how frequently and
accurately I shoot my feet due to stale versions of the module when I am
using it (such as when on travel and I need a debug target).  This isn't
just a property of failing to rebuild modules, but that the Linux
emulation code changes and the VMware modules need to be modified to take
that into account...

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Principal Research Scientist, McAfee Research