I think @Aitch is posting to help with understanding of ARM, news on ARM, and tools for setting up a platform to develop, build, and test using PC based technology. Once, you have built an OS for your ARM, then, you would "load" that newly developed OS into your ARM.
I don't think he was proposing that you create an emulator that will run on ARM. Remember, ARMs though powerful for their intended use, are NOT very powerful up against an Intel/AMD. So I believe he is suggesting that you use the much more powerful Intel/AMDs to develop your ARM's OS, then load it into your ARM.
Edited: 02/17/11 at 1:35PM EST
I think @Aitch and I are proposing the same thing here. Here it is:
- When you install the VM product on your Intel/AMD OS; say Puppy, then that Puppy is called THE VIRTUAL HOST! This means that it can allow you to create little virtual worlds on this host.
- Normally, creating a Virtual world, callled a Virtual Machine (VM) or Virtual client machine, let you start an Intel-based "virtual PC" which will boot another Operating system (lets say Windows).
- At this point you have Puppy as the Virtual Host, and Windows is being run in a VM on the Virtual Host.
- When the above is done, in the VM world we call the VM where Windows as running in an "emulated" area.
- So when you say "emulated" in this context, we VM people believe you mean that the VM where Windows is running is an Intel "emulated" virtual machine. To us, emulated means a particular kind of VM.
- Lastly, above I purposely used the word 'Normally" for this reason. Normally says Intel for a VM, BUT SOME VM Host products will let you create other "EMULATED" VMs for example, I can create an emulated ARM, or I can create an emulated SMP 64bit PC or I can create an emulated 16bit PC, or I created an emulated ...
- Remember, I am "emulating" some hardware device virtually; and then I will run some OS on that virtual hardware device by starting it from the command line on the Puppy console (in this case).
- Understanding this terminology helps you communicate accurately what you mean.
Hi @Aitch
KQemu AND Xen require Intel based processors which have the Virtual Assist Hardware built-in, so that it can achieve near native speeds. Also, Linux must be generated with KVM active so that it will allow KQemu and Xen to take advantage of the hardware assist features so that near-native speeds are reached.
As I remember, most 64bit AMDs have this hardware assist. With Intel, though, you must check the CPU number and "stepping" to insure you have a PC capable of VM near-native speed.
Hope this helps