Date: Wed, 21 Jul 2004 07:58:53 +0100 From: Ben Paley <ben@spooty.net> To: Scott Long <scottl@freebsd.org> Cc: Robert Watson <rwatson@freebsd.org> Subject: Re: vmnet.ko missing - but it's there! - vmware and crashes Message-ID: <200407210758.53856.ben@spooty.net> In-Reply-To: <40FDA3D9.7070806@freebsd.org> References: <200407202355.41867.ben@spooty.net> <40FDA3D9.7070806@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 20 July 2004 23:59, Scott Long wrote:
> Recompile the vmnet.ko binary from source and see if that helps.
I remade the whole thing, in the end, and now at least I'm not getting crashes
(at least, I think I remade the module... I did make and make install and so
on in /usr/ports/emulators/vmware3/ , but I couldn't see how to compile
vmnet.ko on its own).
On boot I still get this:
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
Jul 21 07:41:04 potato kernel: vmmon: Module vmmon: registered with major=200
minor=0 tag=$Name: build-570 (3.2.x mvm) $
vmnet1: Ethernet address: 00:bd:51:0a:00:01
Jul 21 07:41:04 potato kernel: vmmon: Module vmmon: initialized
VMwareStarting apache2.
mysqld rtc.
I guess the link_elf line doesn't look good, is it connected?Vmware starts ok,
then when I try to boot the vm I get this:
Could not query bridging status on /dev/vmnet1: Invalid argument
Failed to configure ethernet0.
in a dialog, and this from the console:
linux: pid 718 (vmware): ioctl fd=10, cmd=0x8940 ('\x89',64) is not
implemented
linux: pid 718 (vmware): ioctl fd=10, cmd=0x89f9 ('\x89',249) is not
implemented
Jul 21 07:43:59 potato kernel: vmmon: Vmx86_ReleaseVM: unlocked pages: 0,
unlock
ed dirty pages: 0
Thanks a lot for your help,
Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407210758.53856.ben>