From owner-freebsd-emulation Wed Oct 16 19:42:17 2002 Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 808BA37B401 for ; Wed, 16 Oct 2002 19:42:15 -0700 (PDT) Received: from dsl-64-128-185-9.telocity.com (dsl-64-128-185-9.telocity.com [64.128.185.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E2FD43E42 for ; Wed, 16 Oct 2002 19:42:14 -0700 (PDT) (envelope-from mjoyner2@hq.dyns.cx) Received: (from root@localhost) by dsl-64-128-185-9.telocity.com (8.12.6/8.11.5) id g9H2flI8054288; Wed, 16 Oct 2002 22:41:47 -0400 (EDT) (envelope-from mjoyner2@hq.dyns.cx) Received: from ip-24.internal (ip-34.internal [192.168.2.34]) by hq.dyns.cx (8.12.6/8.11.5av) with ESMTP id g9H2et5u054249; Wed, 16 Oct 2002 22:40:57 -0400 (EDT) (envelope-from mjoyner2@hq.dyns.cx) Received: from hq.dyns.cx (localhost [127.0.0.1]) by ip-24.internal (8.12.6/8.12.6) with ESMTP id g9H28A1f091087; Wed, 16 Oct 2002 22:08:10 -0400 (EDT) (envelope-from mjoyner2@hq.dyns.cx) Message-ID: <3DAE1B8A.9070209@hq.dyns.cx> Date: Wed, 16 Oct 2002 22:08:10 -0400 From: wolf User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: Q , emulation Subject: Re: vmware2 and SIMD instructions References: <3DAE160C.2070905@hq.dyns.cx> <3DAE18CA.9020609@yahoo.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org well cat /compat/linux/proc/cpuinfo doesn't show simd. :) whenever a guest os tries to enable SIMD, it crashes the guest os. This makes vmware2 on a modern processer usesless for anything but an operating system that is *not* simd aware, eg, no w2k, xp, newer linux, newer *bsd, etc. There is some stuff in ports/emulators/vmware2/work/vmware-distrib/vmmon-only/linux/hostif.c for cpuid, trying to figure out how to badly hack it now.... to see if a) it trashes my system (host), b) causes my kernel to panick, c) freaks vmware out, d) is ignored, or least likely e) causes simd instructions to be not-reported. Seems like something or other could be masked in there to hide that one capability P.S. please use reply-all when replying, your post didn't make it to the list. Q wrote: > As a guess, without trying it. I would suspect that you needed to trick > vmware2 into thinking the host processor doesn't support it. The guest > OS should then see the same capabilities that vmware2 thinks it is being > hosted on. > > There is probably something in the linux "/proc" that vmware uses to > report the cpu capabilities. If you hack the linux emulation to exclude > simd from that list then it might work. > > Why do you need to exclude it anyway? > > Seeya...Q > > wolf wrote: > >> Is there anyway to prevent the vmware2 from detecting SIMD capabilities >> on a processor? maybe have it lie to the guest OS about the processer >> installed? >> > > -- Michael Joyner FreeBSD System Administrator http://manhattan.hq.dyns.cx/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message