| Summary: | Qemu error messages not clear when command line is corrupted. | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Jon Mason <jon.mason> |
| Component: | core | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher, paul, randy.macleod, richard.purdie |
| Version: | 3.3 | ||
| Target Milestone: | 6.2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Jon Mason
2021-05-21 18:01:42 UTC
Richard thinks that this was due to broken test code in the build, i.e. kvm clock related. Let's use this bug to fix a reporting issue: Qemu error messages not clear when command line is corrupted. This was triggered by a corrupted version of this change: -QB_CPU_x86 = "-cpu IvyBridge -machine q35" -QB_CPU_KVM_x86 = "-cpu IvyBridge -machine q35" +QB_CPU_x86 = "-cpu IvyBridge,-kvmclock -machine q35" +QB_CPU_KVM_x86 = "-cpu IvyBridge,-kvmclock -machine q35" -QB_CPU_x86-64 = "-cpu IvyBridge -machine q35" -QB_CPU_KVM_x86-64 = "-cpu IvyBridge -machine q35" +QB_CPU_x86-64 = "-cpu IvyBridge,-kvmclock -machine q35" +QB_CPU_KVM_x86-64 = "-cpu IvyBridge,-kvmclock -machine q35" with IvyBridge-kvmclock missing the comma. We need better log output for broken commands like this. Adding better error reporting is more of an enhancement, IMO. It's less urgent so lower importance to Medium. |