[yocto] genericx86 vs qemux86

[Takashi Matsuzawa]

Hello, thank you for your reply.


I wondered vmware or virtuaobox, etc. are doing something already so that the environment looks like a real PC.  You can run commercial OS like Windows on it and they are no particularly built for the emulation environment.


On the other hand, qemux86* builds are 'safe' version that means limitation in its performance (hardware acceleration, etc.)?

So, if virtualization platform provides what intel-core* builds expects, then I will see a better performance with them, rather thatn qemu* builds.
Or qemu* builds provide particular features that suites well with VM, other thna its 'safe' behavior?

That is my concern.



________________________________
From: Burton, Ross <ross.burton at intel.com>
Sent: Saturday, February 4, 2017 8:20 AM
To: Takashi Matsuzawa
Cc: yocto at yoctoproject.org
Subject: Re: [yocto] genericx86 vs qemux86


On 3 February 2017 at 23:16, Takashi Matsuzawa <tmatsuzawa at xevo.com<mailto:tmatsuzawa at xevo.com>> wrote:
Sorry, I am still a bit confused with genericx86 and qemux86 targets.  What is their difference and which one to choose.
Both are x86 target and maybe genericx86 has more support for PC hardware?  qemux86 has v86d?
genericx86 is from poky and qemux86 is from openembeded?

qemux86 is specifically for use in qemu, so it targets a CPU that qemu is good at executing and has the virtualised hardware drivers in.  genericx86 is an attempt at a "all purpose" x86 machine that runs most places acceptably.

My recommendation would be to use qemux86 (-64) for virtual environments and a machine from meta-intel (intel-corei7-64 or intel-core2-32) for real hardware.  The genericx86 machine, being part of poky, is basically for QA purposes and if you are targetting Intel hardware then the Intel BSPs are better.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170204/5d6ece4c/attachment.html>