| Summary: | linux-yocto cant boot in qemu when cpu=host | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Kernel | Reporter: | Khem Raj <raj.khem> |
| Component: | linux-yocto | Assignee: | Stefan Stanacar <sstncr> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | sgw, sstncr |
| Version: | 1.6 | ||
| Target Milestone: | 1.6 | ||
| Hardware: | x86 | ||
| OS: | x86_64 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Khem Raj
2014-03-13 01:34:30 UTC
I think that the right fix to use -cpu host is to include paravirt kernel config for qemux86-64. (this isn't needed for -cpu kvm64 as it is now) Note that it is enabled for qemux86 but not for x86-64. The is what we currently have in linux-yocto-3.10.bb: KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc" KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc" That change has been inherited from recipe to recipe since: http://git.yoctoproject.org/cgit.cgi/poky/commit/meta/recipes-kernel/linux/linux-yocto_3.4.bb?id=e6149ec6c4c14d3a939022cdc29ac94dced836dd The reason for that commit was that on AB some qemux86-64 failed to shutdown because of the old host kernel. But that's more than a year old commit, and the ABs are now on newer kernels. So if we want kvm and -cpu host on a host with kernel >=3.8 we should enable that config back. No objection from me. Have you tested a change? Could you do so and submit a patch? Patch sent - tested that the image behaves good - without kvm - with kvm (and the default cpu=kvm64) and - with kvm and Khem's change to runqemu (cpu=host) Have a look on the ML. Btw, I've sent the change for the new linux-yocto-3.14 only, if that matters to anyone. |