linux/poky.git/scripts/runqemu, branch yocto-2.4.4

runqemu: Add workaround for APIC hang on pre 4.15 kernels on qemux86

2018-01-06T10:13:57+00:00

On pre 4.15 host kernels, an APIC window emulation bug can cause qemu to hang. On 64 bit we can use the x2apic, for 32 bit, we just have to disable the other timer sources and rely on kvm-clock. [YOCTO #12301] (From OE-Core rev: 04646ed7edf020b73c6639a1a7445252cf7aad5e) Signed-off-by: Richard Purdie (cherry picked from commit 82e67b82ea8e12aa0b7b9db1d84fec0436dec71b) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

runqemu: print command search result when not found

2017-12-04T17:24:00+00:00

This makes debug easier. (From OE-Core rev: b99ba567cd8089a9a3ca01704f6ba6c42d390e9f) Signed-off-by: Robert Yang Signed-off-by: Ross Burton (cherry picked from commit a453639e19fb2a9f9fb63fddd0b3ee26c0116d91) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

runqemu: Also specialcase resolution of '.' to the file's location

2017-12-04T17:24:00+00:00

Similarly to handling "../", handle "." to resovle to the qemuconf file's current directory. (From OE-Core rev: 9870247d0dc33357988d9636c8ff8db35490752e) Signed-off-by: Richard Purdie (cherry picked from commit 33418ed064fe9cff5b4803f09135a81d9170c189) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

runqemu: Improve relative path handling in qemuconf files

2017-12-04T17:23:59+00:00

If a variable starts with "../", its likely its a path and we want to set it to an absolute path relative to the qemuconf file. This means we don't have to use bitbake as often to figure out variables. (From OE-Core rev: 61c449857f056d7c6c29530aa11bf8353b113638) Signed-off-by: Richard Purdie (cherry picked from commit dfc7940900d798aa47716288338107e1d46a3972) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

runqemu: Ensure we process all tap devices

2017-12-04T17:23:59+00:00

The regexp in the script misses some tap devices, e.g. we see output like: runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap25.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap26.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap27.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap28.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap40.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap41.lock failed: [Errno 11] Resource temporarily unavailable What happened to tap29 to tap39? The issue is was we were missing devices with '0' in the number, like "10:" and so on in the output from "ip link". (From OE-Core rev: ec1481f7ad6f2b3d1420027327510bec94dd66a8) Signed-off-by: Richard Purdie (cherry picked from commit 6447697a48e3b693ee38806bc2ba07c2a65c2bc8) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

runqemu: correct rootfs setup to boot an ide hddimg

2017-12-04T17:23:55+00:00

vm_drive variable is malformed when the drive type is an ide device. (From OE-Core rev: 02dbf124328eebdfdf62402588a41719953a22bf) Signed-off-by: Thomas Perrot Signed-off-by: Richard Purdie (cherry picked from commit 88d7b17871fe8340ab7fd5c901d3a535ae098c3e) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

scripts/runqemu: Don't print error messages about tap file locks

2017-08-30T10:14:26+00:00

Errors like: runqemu - ERROR - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock failed: [Errno 11] Resource temporarily unavailable are not really fatal errors. Change these to info messages instead so people look later in the log for the real errors. (From OE-Core rev: fac12de72bda1e864e71538be07d6c6f6e987498) Signed-off-by: Richard Purdie

runqemu: Use virtio to mount cdrom drives

2017-08-23T11:06:52+00:00

The IDE driver in the kernel is fragile and in 4.12 is causing backtraces. To unblock 4.12 kernel merging use the virtio CD driver instead to mount iso images which should be faster and more stable. (From OE-Core rev: f59e729f98ef9b506b0cfdc415567e03ec87f2a9) Signed-off-by: Richard Purdie

image: Convert vmdk/vdi/qcow2 to strict CONVERSION_CMD types

2017-07-30T07:46:20+00:00

The vmdk/vdi/qcow2 IMAGE_FSTYPEs predate wic. As such, they provide some similar underlying functionality in order to produce a "disk" image that in turn can be converted into different formats that various hypervisor types work with. They do not however provide the ability for other disk image types to be converted into these same output types. Furthermore, they are less flexible than what wic does provide. This drops the old style vmdk/vdi/qcow2 types and re-introduces them under the CONVERSION_CMD framework. The equivalent of vmdk is now wic.vmdk and so forth for the other types. (From OE-Core rev: 929ba563f1bc7195c4981b8e139c432b2cc388ea) Signed-off-by: Tom Rini Signed-off-by: Richard Purdie

runqemu: chmod 0o777 for lockdir

2017-07-27T21:36:52+00:00

Multi-users may run qemu on the same host, all of them should be able to create or remove lock in lockdir, so set lockdir's mode to 0o777. Note, os.mkdir()'s mode is default to 0o777, but the current umask value is first masked out, so use os.chmod() to set it. (From OE-Core rev: 4a5d21dbdc88982c2c90e660811b84983eaebeb7) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie