From owner-freebsd-current@FreeBSD.ORG Thu Mar 3 01:48:10 2005 Return-Path: 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 A302516A4CE for ; Thu, 3 Mar 2005 01:48:10 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37DCD43D31 for ; Thu, 3 Mar 2005 01:48:09 +0000 (GMT) (envelope-from vladimir@math.uic.edu) Received: from cat.math.uic.edu (c-24-12-126-199.client.comcast.net[24.12.126.199]) by comcast.net (rwcrmhc11) with SMTP id <2005030301480801300qd8pse>; Thu, 3 Mar 2005 01:48:08 +0000 Received: (qmail 21991 invoked by uid 31415); 3 Mar 2005 01:48:08 -0000 Date: Wed, 2 Mar 2005 19:48:08 -0600 From: Vladimir Egorin To: Doug Ambrisko Message-ID: <20050303014808.GA19265@math.uic.edu> References: <42242DC5.2070401@elischer.org> <200503020553.j225r3OL008922@ambrisko.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200503020553.j225r3OL008922@ambrisko.com> User-Agent: Mutt/1.5.8i cc: Current cc: Julian Elischer Subject: Re: fixing Vmware 2 port for 5.x and 6.x.. kmem _alloc_pageable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 01:48:10 -0000 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