Yale Zhang yzhang1985@gmail.com writes:
- What's the best design: whole system VM (qemu) or process VM (qemu &
wine)?
Process VM:
- easier to incorporate 3D acceleration at API level
- uses less memory
- better performance (e.g. no need for MMU translation when accessing
memory)
- much better integration with host OS
- needs to maintain custom Windows API implementation (Wine)
Whole system VM:
- simpler, more unified to implement
- much better support for apps that are dependent on new, proprietary,
obscure Windows libraries, interfaces (moot because Office, Matlab, etc will soon be available for ARM)
Given the aims of only running legacy applications and games, it seems a foregone conclusion that Wine's process VM approach is best. Comments?
I think you underestimate the complexity of doing the emulation at the API level. You should first make it work by running the whole process under the emulator; once you get this right, then you can start thinking about running some parts natively.