From owner-freebsd-questions Thu Oct 17 10:55:17 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62EF437B401 for ; Thu, 17 Oct 2002 10:55:16 -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 9914A43E97 for ; Thu, 17 Oct 2002 10:55: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 g9HHsh3m090949; Thu, 17 Oct 2002 13:54:43 -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 g9HHs75u090919; Thu, 17 Oct 2002 13:54:07 -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 g9HHsZ1f094226; Thu, 17 Oct 2002 13:54:36 -0400 (EDT) (envelope-from mjoyner2@hq.dyns.cx) Message-ID: <3DAEF95B.9000400@hq.dyns.cx> Date: Thu, 17 Oct 2002 13:54:35 -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 Cc: questions 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-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, after some research last night, there is apparantly no way to trap cpuid calls. :( Anyone out there know anyway to trap the simd enabling instruction in vmware? 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-questions" in the body of the message