Date: Thu, 17 Oct 2002 13:54:35 -0400 From: wolf <mjoyner2@hq.dyns.cx> To: Q <q_dolan@yahoo.com.au> Cc: questions <questions@freebsd.org> Subject: Re: vmware2 and SIMD instructions Message-ID: <3DAEF95B.9000400@hq.dyns.cx> References: <3DAE160C.2070905@hq.dyns.cx> <3DAE18CA.9020609@yahoo.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DAEF95B.9000400>