Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Mar 2005 19:48:08 -0600
From:      Vladimir Egorin <vladimir@math.uic.edu>
To:        Doug Ambrisko <ambrisko@ambrisko.com>
Cc:        Julian Elischer <julian@elischer.org>
Subject:   Re: fixing Vmware 2 port for 5.x and 6.x.. kmem _alloc_pageable
Message-ID:  <20050303014808.GA19265@math.uic.edu>
In-Reply-To: <200503020553.j225r3OL008922@ambrisko.com>
References:  <42242DC5.2070401@elischer.org> <200503020553.j225r3OL008922@ambrisko.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 01, 2005 at 09:53:03PM -0800, Doug Ambrisko wrote:
	> Julian Elischer writes:
	> | Well I have it compiling but when running
	> | it fails with:
	> | 
	> | julian@jules:vmware
	> | Setting TMPDIR=/var/tmp.
	> | VMware Workstation PANIC: NOT_IMPLEMENTED F(566):1081
	> | VMware Workstation PANIC: NOT_IMPLEMENTED F(566):1081
	> | VVMware Workstation PANIC: NOT_IMPLEMENTED F(566):1296
	> | AIO panic loop
	> | Mware Workstation PANIC: AIO: NOT_IMPLEMENTED F(566):1081
	> | julian@jules:
	> | 
	> | I am guessing that, since this DID work before
	> | the new linux base libraries are expecting to use AIO
	> | and maybe we don't support it?
	> 
	> vmware/linux has a bug.  Linux libs changed the call breaking
	> vmware.  There are source programs to patch the vmware binaries.
	> Do a google search for vmware-any-any-update, build and run against
	> you vmware bin.
	> 
	> Doug A.

Do you know if the same recipe would work for vmware3 ?  
The port used to work on -CURRENT until about Feb 13, 
but since then pushing the "power on" button in vmware
instantaneously reboots the machine.   I did reinstall
vmware port after upgrading.

Thanks,

-- 
Vladimir



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050303014808.GA19265>