<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/scripts/runqemu, branch dunfell-23.0.1</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=dunfell-23.0.1</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=dunfell-23.0.1'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2020-03-29T19:04:10+00:00</updated>
<entry>
<title>runqemu: Change nfs to mount via TCP</title>
<updated>2020-03-29T19:04:10+00:00</updated>
<author>
<name>He Zhe</name>
<email>zhe.he@windriver.com</email>
</author>
<published>2020-03-27T07:33:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2b8dd4ab6dd1d9b2ba791fe346098554613b91d1'/>
<id>urn:sha1:2b8dd4ab6dd1d9b2ba791fe346098554613b91d1</id>
<content type='text'>
Since kernel commit b24ee6c64ca7 ("NFS: allow deprecation of NFS UDP protocol"),
NFS UDP has been disabled by default due to the potential data corruption caused
by fragmentation during high loads. So now we cannot boot up with nfs mode and
default kernel.

We'd better turn to use TCP accordingly.

(From OE-Core rev: 73a54595d8ddf237d685ea9cb46df0cecac0280d)

Signed-off-by: He Zhe &lt;zhe.he@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: support multiple NICs</title>
<updated>2020-03-21T22:39:00+00:00</updated>
<author>
<name>Adrian Freihofer</name>
<email>adrian.freihofer@siemens.com</email>
</author>
<published>2020-03-17T15:26:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2f6a47c4d4dc24135b69ed01e193740c24f269e8'/>
<id>urn:sha1:2f6a47c4d4dc24135b69ed01e193740c24f269e8</id>
<content type='text'>
Emulating more than one network interface with runqemu is a bit tricky,
but possible. For example, the following leads to an emulated device with
eth0 and eth1:

QB_NETWORK_DEVICE_prepend = " \
    -device virtio-net-device,mac=52:54:00:12:34:03 \
"

or

QB_NETWORK_DEVICE_append = " \
    -device virtio-net-pci,mac=52:54:00:12:34:03 \
"

When booting Qemu with two NICs, the kernel does not know which
interface the specified ip=192.168.7.... command line argument
should be applied. This delays the boot process for a very long
time and a guest wihtout IP configuration.

This add two new configuraton parameters to runqemu:
QB_CMDLINE_IP_SLIRP and QB_CMDLINE_IP_TAP to explicitely specify the ip=
kernel command line arguments for tap and slirp mode.

Note: Simply adding "::eth0" broke some builds on the Yocto autobuilder.

(From OE-Core rev: 59bfdc331c1494c05ab38804b281878a1f571f6d)

Signed-off-by: Adrian Freihofer &lt;adrian.freihofer@siemens.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: Add network bridge support</title>
<updated>2020-01-10T21:18:23+00:00</updated>
<author>
<name>Joshua Watt</name>
<email>jpewhacker@gmail.com</email>
</author>
<published>2020-01-08T19:48:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=08220028e52992dcba667fc97bf3afe8be1949fb'/>
<id>urn:sha1:08220028e52992dcba667fc97bf3afe8be1949fb</id>
<content type='text'>
Qemu supports attaching the virtual machine to an existing network
bridge interface via the qemu-bridge-helper program (as long as the
system is correctly configured to give the user permissions). Add
support for runqemu to do this also via the "bridge=&lt;INTERFACE&gt;"
argument. Note that for this to work correctly, the host
qemu-bridge-helper must be used, not the one that might have been built
by qemu-native. In order for qemu to correctly find this program, a
qemu-oe-bridge-helper program has been added to qemu-helper-native, and
runqemu will use this helper as the bridge helper. The helper will look
for the host qemu-bridge-helper first by looking in the
QEMU_BRIDGE_HELPER environment variable, then by search common paths
where the helper is installed.

(From OE-Core rev: 9e7b38c61c6b84b7f137c733ac5da9414025693d)

Signed-off-by: Joshua Watt &lt;JPEWhacker@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: add virtio block device</title>
<updated>2020-01-06T23:54:39+00:00</updated>
<author>
<name>Maxim Uvarov</name>
<email>maxim.uvarov@linaro.org</email>
</author>
<published>2020-01-04T20:08:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9ac151b744d9305f777430f08e871ea6cba75efc'/>
<id>urn:sha1:9ac151b744d9305f777430f08e871ea6cba75efc</id>
<content type='text'>
Implement new QB_DRIVE_TYPE="/dev/vdb" which falls back
to virtio block device emulated by qemu.
That is needed to support following qemu command line:
-drive id=disk0,file=%s,if=none,format=%s \
  -device virtio-blk-device,drive=disk0'

Real use case is arm64 emulation with qemu with atf+optee+uboot,
so that uboot driver sees this disk and able to load from it.

(From OE-Core rev: 4d72cd395b2dd40dde1f3809e3ab255938e6a7a1)

Signed-off-by: Maxim Uvarov &lt;maxim.uvarov@linaro.org&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: Add multiconfig support</title>
<updated>2020-01-01T10:46:16+00:00</updated>
<author>
<name>Joshua Watt</name>
<email>jpewhacker@gmail.com</email>
</author>
<published>2019-12-30T20:59:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=714eb4532b21b4e16bcd6e0975cfb887e93b08ce'/>
<id>urn:sha1:714eb4532b21b4e16bcd6e0975cfb887e93b08ce</id>
<content type='text'>
Users may want to run qemu against a specific multiconfig instead of the
base configuration, so give them the ability to specify which config
should be used with the MULTICONFIG environment variable.

(From OE-Core rev: fda5d9b64fa310173ad949540c54fd693c4f7d3a)

Signed-off-by: Joshua Watt &lt;JPEWhacker@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: handle tap device creation failure properly</title>
<updated>2019-12-15T09:10:46+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2019-12-09T10:59:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c64c5e0eda98e667de22074d6ea606c655519dc0'/>
<id>urn:sha1:c64c5e0eda98e667de22074d6ea606c655519dc0</id>
<content type='text'>
If we fail to run the command to generate the tap devices then we should
show a reasonable message and then exit, without showing a traceback.
"return 1" at this point in the code does nothing because the caller
doesn't check the return, so just use sys.exit().

(From OE-Core rev: 47e40fdd7dd58bde4e017e2375c16450fcb14eca)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: log parameters correctly within testimage</title>
<updated>2019-12-15T09:10:46+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2019-12-09T10:59:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4955fe19abfde0fd9b4fe5e1f82fd2a148e5db01'/>
<id>urn:sha1:4955fe19abfde0fd9b4fe5e1f82fd2a148e5db01</id>
<content type='text'>
It is not a good idea to mix logging and calls to print() - if the
output is being captured the result can be that the two types of output
are not recorded contiguously; this could be observed if an error
occurred running runqemu from inside testimage:

---------- snip ----------
ERROR: core-image-minimal-1.0-r0 do_testimage: Output from runqemu:
runqemu - INFO - Continuing with the following parameters:

runqemu - INFO - Setting up tap interface under sudo
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
runqemu - ERROR - Setting up tap device failed:
Command '('sudo', '/home/paul/poky/poky/scripts/runqemu-ifup', '1000', '1000', '/home/paul/poky/poky/build/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin')' returned non-zero exit status 1.
Run runqemu-gen-tapdevs to manually create one.
runqemu - INFO - Cleaning up
KERNEL: [/home/paul/poky/poky/build/tmp/deploy/images/qemux86-64/bzImage--5.2.20+git0+bd0762cd13_dd25a04fc5-r0-qemux86-64-20191205213021.bin]
MACHINE: [qemux86-64]
FSTYPE: [ext4]
ROOTFS: [/home/paul/poky/poky/build/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.ext4]
CONFFILE: [/home/paul/poky/poky/build/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.qemuboot.conf]
---------- snip ----------

What we should see here is the KERNEL, MACHINE, etc. lines appearing
immediately after the "Continuing with the following parameters:" line
as they do when you run runqemu directly. If we put all of the lines
through the logger instead then it works properly.

(From OE-Core rev: ca64a3d490fbe1bf87c9f1dd6d87a1ecdeba8325)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: add options that enable virgl with the SDL frontend</title>
<updated>2019-11-22T23:13:06+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2019-11-18T14:28:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=221e94e6d38bf03d348ea1f4eb922fa22a7f502e'/>
<id>urn:sha1:221e94e6d38bf03d348ea1f4eb922fa22a7f502e</id>
<content type='text'>
(From OE-Core rev: c2564c7554a664ed26e010c67080fc784cff682a)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: Remove disabling of high resolution timer</title>
<updated>2019-10-15T13:16:11+00:00</updated>
<author>
<name>Joerg Vehlow</name>
<email>joerg.vehlow@aox-tech.de</email>
</author>
<published>2019-10-11T06:03:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7ed5aa23c796b8593a4bf66f1b36ffbc69a27496'/>
<id>urn:sha1:7ed5aa23c796b8593a4bf66f1b36ffbc69a27496</id>
<content type='text'>
The option 'highres=off' sneaked itself into the runqemu script for all
configurations, where the root filesystem type is not 'cpio' or 'cpio.gz'.
See: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13590

(From OE-Core rev: 3ecb6744402332f1ad143eb1eb6a94143e1700c8)

Signed-off-by: Joerg Vehlow &lt;joerg.vehlow@aox-tech.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: unset another environment variable for 'egl-headless'</title>
<updated>2019-10-15T13:16:10+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex.kanavin@gmail.com</email>
</author>
<published>2019-10-11T11:47:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8c4a9f5b6571b95e66dd6153289dc43ea085c18a'/>
<id>urn:sha1:8c4a9f5b6571b95e66dd6153289dc43ea085c18a</id>
<content type='text'>
Some host distributions (opensuse for example) are using 'pkgconf',
which, unlike the original pkg-config, appends PKG_CONFIG_SYSROOT_DIR
to every directory from the .pc file.

(From OE-Core rev: 2d5ecc560dcfbaaaff307f8367d789d8c7e00dcf)

Signed-off-by: Alexander Kanavin &lt;alex.kanavin@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
