![]() As for CPU-Z's detection of cores it's most likely quite simple. But if you take notice it STILL says it's a Core2 Duo E6400, it reports the family, model, stepping etc the same for both host and guest, and all other info such as cache. The guest inside isn't 100% as fast as the host (naturally) which means the timing is off and it shows to be a slower CPU. As for the speed settings it's most likely a timing issue. VMWare has actually the selection where you can choose how many cores you want to run in a single guest. ![]() The reason your host shows to be dualcore and the guest to be single core is most likely (not sure here tho) because the guest runs as a single CPU system. VirtualPC for Mac (PPC) worked in a similiar way, emulating the x86 instruction set and translated it so it can be run on the PowerPC instruction set. I can emulate an Alpha instruction set (IA-32) quite well too. Bochs can for example emulate a true 386 CPU even if you got a Core2 system. It uses the host processors capabilities and forwards the instructions to the guest, with some exceptions since a lot of handles has to be emulated in the guest, and not all instructions can be virtualised without too much speed penalty.Ī real CPU emulator is for example Bochs which can emulate an entire instruction set regardless of your host CPU (since you can run Bochs on a various of platforms). Do you want to run a 386? or a Pentium Pro. A simple evidence for that is that if it were to emulate a CPU you would be able to choose which instruction set to emulate. VirtualPC (or VMWare) does not emulate the CPU.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |