linux/poky.git/meta/conf/machine/include/qemuboot-x86.inc, branch master-uninative

conf/machine: move tune files to architecture directories

2021-08-18T16:01:06+00:00

Move all of the tune files found in conf/machine/include into their respective architecture directories in that same location. All references to these will need to be updated. So, change the relevant ones for this tree in this commit as well. For the ARM tunes, nest them one further into armv8a, armv8m, etc. and rename some to make them uniform with the rest of the tunes. (From OE-Core rev: b6f15209bcfff953cce69da97a93f9ddff141ced) Signed-off-by: Jon Mason Signed-off-by: Richard Purdie

Convert to new override syntax

2021-08-02T14:44:10+00:00

This is the result of automated script conversion: scripts/contrib/convert-overrides.py converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie

qemu-x86: Add commandline options to improve boot

2021-05-13T17:09:10+00:00

To try and help with the inermittent rcu stalls and boot issues with qemu add some kernel commandline options commonly used with qemu instances which were suggested may help. (From OE-Core rev: d75cb16ecb3a55fd7631bf7720663e4b196421ee) Signed-off-by: Richard Purdie

qemuboot-x86: Switch to IvyBridge and q35 instead of pc

2021-05-13T17:09:10+00:00

Move from 1996 to 2009 by swapping machine 'pc' for 'q35'. Also move to a CPU which is SMP capable and doesn't have tsc bugs. IvyBridge matches what we're using on the autobuilder. The intent here is to try and improve on some of the intermittent autobuilder issues we're seeing. I'm told that nobody else runs with config this old and it could well be contributing to our issues. Having reliable testing is key to the project and justifies updating this IMO. (From OE-Core rev: 6d9f25782bd585e89c5aaf7046266c848f1e581b) Signed-off-by: Richard Purdie

qemu: Set SMP to 4 cpus for arm/x86 only

2021-05-13T17:09:10+00:00

Only qemux86* and qemuarm* support SMP with our current configurations so rework qemu SMP enabling to account for that and only use it on the architectures where it works. (From OE-Core rev: ee371325ce651cc113e43bdeb5d8986d5b84a3f4) Signed-off-by: Richard Purdie

qemuboot: Add QB_RNG variable

2020-09-24T21:32:49+00:00

RNG passthru has been enabled on all qemu machines but its being added to each one of them, with this patch its turned into QB variables which defaults to host passthru, yet it can be overridden if needed via machine or config metadata if needed. (From OE-Core rev: 26dd24506ef36088e17f999ce5489dc4b72194e8) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

qemu: uprev v4.2.0 -> v5.0.0

2020-06-23T11:31:03+00:00

Major update after v4.2. Changes: - os_find_datadir() was changed after the v4.2 release causing v5.0 to not find the bios and not boot the image. Fix is sent to upstream qemu. See: qemu/find_datadir.patch - v5.0 binary had host contamination for dynamically linked libraries, "--extra-ldflags='${LDFLAGS}'" in EXTRA_OECONF resolved the issue - bluetooth code was removed: qemu.git$ git show 1d4ffe8dc7 hence removed PACKAGECONFIG[bluez] - -show-cursor qemu option is now deprecated, updated scripts/runqemu to use updated option instead - added PACKAGECONFIG definitions - added qemu-ptest to conf/distro/include/ptest-packagelists.inc - increased support for ARM architecture, cpu and board - removed patches merged upstream and refreshed existing ones Testing: Build core-image-minimal against the machines in openembedded-core/meta/conf/machine and succesfully booted with qemu v5.0 Ran qemu-ptest on x86-64 and arm64 with identical results: PASS: 1166 SKIP: 0 FAIL: 0 (From OE-Core rev: ee9ec9e344541c1ccd9b9b8e3b8c1e00d008ad85) Signed-off-by: Sakib Sajal Signed-off-by: Joe Slater Signed-off-by: Richard Purdie

qemux86: drop resolution setting via uvesafb

2020-02-18T23:53:54+00:00

I am not sure if this has ever worked, but uvesafb is a really outdated (VBE from the 1990s), awkward (needs v86d) and limited (no support for high resolutions) way to do it. The specific reason 640x480-32 was introduced (ages ago) was to force 32 bit mode with vmware driver, as 16bit had rendering issues. The modern, supported option is video=... kernel parameter documented here: https://wiki.archlinux.org/index.php/kernel_mode_setting#Forcing_modes_and_EDID https://github.com/torvalds/linux/blob/master/Documentation/fb/modedb.rst which can be passed directly to runqemu and doesn't require special kernel modules. Sato under X will continue to use 640x480 as that is hardcoded into xorg.conf under qemu. (From OE-Core rev: 1cf26f69fd89b43be24cd1232c43e5050b9d718a) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

qemux86: do not add vga=0 to kernel parameters

2020-02-18T23:53:54+00:00

This was added ages ago to enable GL passthrough with vmware driver, and is no longer relevant, as std or virgl is used instead nowadays. Original commit: commit 072545b1111c5efb66289a4866897429f5fcd969 Author: Richard Purdie Date: Wed Jan 21 17:40:51 2009 +0000 scripts/poky-qemu-internal: Add support for GL passthrough in qemux86 images (From OE-Core rev: 857078ba8eda153f4a097683db551a7d310ecc01) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

qemu: switch to '-vga std' emulated hardware from vmware/cirrus for x86/mips

2019-09-01T21:33:07+00:00

This is the qemu default since qemu 2.2, is generally supported better, and is recommended by upstream. It also has already been in use for arm/risc and ovmf. Additional information: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13466 https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/ '-vga virtio' emulated hardware remains in use when virgl is enabled via a runqemu override. Also, adjust the error whitelist, as there is a number of new messages coming from the drivers that are not actual errors. (From OE-Core rev: 73cb104f3307736f4922f2e0c9648f9b2d3b3b6b) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie