Re: vmware2 and simd instructions

2002-10-21 Thread soralx
> From what I have gathered doing web seaches, the cpuid opcode is *not* > trappable. :( What's the problem then? The guest OS should get proper info from the CPUID instruction. Can you test that? What does CPU info program show about the CPU in a guest OS? The problem is in VMWare - it has some w

Re: vmware2 and simd instructions

2002-10-19 Thread soralx
>>>is there anyway to lie to vmware2 about the processor installed? or a >>>patch to vmmon to have it lie to the guest os about the processor >>>installed? >>yes >Please enlighten us. >I would like to have more than ancient stuff running in my vmware2 I assume "to lie to vmware2 about the processo

Re: vmware2 and simd instructions

2002-10-18 Thread wolf
Please enlighten us. I would like to have more than ancient stuff running in my vmware2 [EMAIL PROTECTED] wrote: is there anyway to lie to vmware2 about the processor installed? or a patch to vmmon to have it lie to the guest os about the processor installed? yes 17.10.2002; 19:32:37 [SorAlx

Re: vmware2 and simd instructions

2002-10-18 Thread wolf
Please enlighten us. I would like to have more than ancient stuff running in my vmware2 [EMAIL PROTECTED] wrote: is there anyway to lie to vmware2 about the processor installed? or a patch to vmmon to have it lie to the guest os about the processor installed? yes 17.10.2002; 19:32:37 [SorAlx

Re: vmware2 and simd instructions

2002-10-17 Thread soralx
> is there anyway to lie to vmware2 about the processor installed? or a > patch to vmmon to have it lie to the guest os about the processor > installed? yes 17.10.2002; 19:32:37 [SorAlx] http://cydem.zp.ua/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the

vmware2 and simd instructions

2002-10-16 Thread wolf
is there anyway to lie to vmware2 about the processor installed? or a patch to vmmon to have it lie to the guest os about the processor installed? -- Michael Joyner FreeBSD System Administrator http://manhattan.hq.dyns.cx/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebs