<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/scripts/runqemu, branch daisy-11.0.3</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=daisy-11.0.3</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=daisy-11.0.3'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2014-03-21T12:05:54+00:00</updated>
<entry>
<title>runqemu: Add option for custom BIOS directory</title>
<updated>2014-03-21T12:05:54+00:00</updated>
<author>
<name>Ricardo Neri</name>
<email>ricardo.neri-calderon@linux.intel.com</email>
</author>
<published>2014-03-20T19:35:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=68acafd7dc18f23707c95c90e871395ded81f84b'/>
<id>urn:sha1:68acafd7dc18f23707c95c90e871395ded81f84b</id>
<content type='text'>
Add support to specify a directory for custom BIOS, VGA BIOS and
keymaps as supported by qemu (-L option). Even though this can be
done through qemuparams, having this option provides better user
experience by not having to specify a long and cluttered path along
with other qemuparams that the user might want to specify.

This new options assumes first that the path provided is relative to
OECORE_NATIVE_SYSROOT and will check whether it exists before proceeding.
If not, it will treat the provided path as absolute. This provides
the user flexibility to use BIOS binaries generated inside or outside
the OE build environment.

(From OE-Core rev: d302f5683dd736ac4cd4b601a046d22000d41e68)

Signed-off-by: Ricardo Neri &lt;ricardo.neri-calderon@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: Use readlink instead of realpath</title>
<updated>2014-02-25T21:29:53+00:00</updated>
<author>
<name>Saul Wold</name>
<email>sgw@linux.intel.com</email>
</author>
<published>2014-02-25T18:30:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e47afff7d812c74f8091d85facfdf34d6a1b698e'/>
<id>urn:sha1:e47afff7d812c74f8091d85facfdf34d6a1b698e</id>
<content type='text'>
(From OE-Core rev: 5a4b5c6b8ebd5f8d29888aafcd9608e03717bcd5)

Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: Ensure ROOTFS path is absolute</title>
<updated>2014-02-21T16:09:08+00:00</updated>
<author>
<name>Saul Wold</name>
<email>sgw@linux.intel.com</email>
</author>
<published>2014-02-20T20:55:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=425dc69bc7b9ea0f8ca886c442e37bba4f76ec8f'/>
<id>urn:sha1:425dc69bc7b9ea0f8ca886c442e37bba4f76ec8f</id>
<content type='text'>
There is a problem if a relative path is passed to the kernel for NFS usage
that it will not correctly find it, so ensure that the ROOTFS path is absolute.

[YOCTO #2807]

(From OE-Core rev: 5722be0ddda4ec3c96c06b425e5c7e0194326253)

Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: enforce right CPU type for qemux86/x86-64</title>
<updated>2014-02-13T17:53:30+00:00</updated>
<author>
<name>Cristian Iorga</name>
<email>cristian.iorga@intel.com</email>
</author>
<published>2014-02-13T15:26:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a2a20adbfd03ed9f07a3aa38ee2c9a8d962d4bf9'/>
<id>urn:sha1:a2a20adbfd03ed9f07a3aa38ee2c9a8d962d4bf9</id>
<content type='text'>
Set in accordance with qemu machines configs.

Fixes [YOCTO #5817].

(From OE-Core rev: 0e5cfef90ff762b33da6dc301dfc9cb3947c8a02)

Signed-off-by: Cristian Iorga &lt;cristian.iorga@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu, runqemu-internal: Allow slirp for NFS and KVM use</title>
<updated>2014-01-28T00:52:36+00:00</updated>
<author>
<name>Jason Wessel</name>
<email>jason.wessel@windriver.com</email>
</author>
<published>2014-01-23T14:32:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2fedfdca12983cf3240dd7b22ae53d7ee3b2b372'/>
<id>urn:sha1:2fedfdca12983cf3240dd7b22ae53d7ee3b2b372</id>
<content type='text'>
The default slirp address for the NFS server is 10.0.2.2.  If not
using a tap interface this address must be used or the target system
cannot connect properly.  Also the ip=... kernel arguments need to be
set to dhcp when using slirp or the root NFS will not get setup
properly.

The call to cleanup() results in a routine which is not defined when
setting up the NFS because it is called before acquire() for the
locking of the tap interfaces, the solution being to simply not call
cleanup() that early.

When using slirp, kvm should not execute the vhost net checks because
the vhost net will not be configure or used.

(From OE-Core rev: 1ea04d87525f26c2cd32ba29c0f14c6226f60729)

Signed-off-by: Jason Wessel &lt;jason.wessel@windriver.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: Allow user to set -vga option with qemuparams</title>
<updated>2013-12-20T12:26:30+00:00</updated>
<author>
<name>Valentin Popa</name>
<email>valentin.popa@intel.com</email>
</author>
<published>2013-12-19T14:02:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=dd50c4d8a0cff2c4e0b8ff54d9ecf33d00301800'/>
<id>urn:sha1:dd50c4d8a0cff2c4e0b8ff54d9ecf33d00301800</id>
<content type='text'>
At the moment, the user cannot to set -vga other then vmware
(because "vmware" is set by default); and the first argument
in qemuparams has higher precedence.

(From OE-Core rev: 54a43397c48c974570e3eade55163eb766994a55)

Signed-off-by: Valentin Popa &lt;valentin.popa@intel.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: remove core-image-* whitelist</title>
<updated>2013-12-09T18:01:46+00:00</updated>
<author>
<name>Scott Garman</name>
<email>scott.a.garman@intel.com</email>
</author>
<published>2013-12-05T21:57:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fc0bb31aa73b8105206c58dff66297c8fb1d2b3b'/>
<id>urn:sha1:fc0bb31aa73b8105206c58dff66297c8fb1d2b3b</id>
<content type='text'>
Using a whitelist for image names to default to when none are
specified on the command line is no longer desired. Instead,
choose the most recently created image filename that conforms
to typical image naming conventions.

Fixes [YOCTO #5617].

(From OE-Core rev: 9f69e00200cdbd5ba2e46a54f33c29797816e43f)

Signed-off-by: Scott Garman &lt;scott.a.garman@intel.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: Use correct kvm CPU options for qemux86* with kvm</title>
<updated>2013-09-26T15:37:56+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2013-09-25T20:59:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b8819b02dc4ff29d678cc55887dfe6c2d109a67d'/>
<id>urn:sha1:b8819b02dc4ff29d678cc55887dfe6c2d109a67d</id>
<content type='text'>
The existing -cpu host option caused kernel panics when people attempted to use
the kvm option. After research and discussion, the best options appear to
be the kvm32/kvm64 cpu types so lets use these instead. These resolve
the kernel issues for me.

[YOCTO #3908]

(From OE-Core rev: bdc6d3be6ffa4ed358153f9c9332b632324f5833)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>scripts/runqemu: write temp file into correct location</title>
<updated>2013-09-24T16:57:03+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2013-09-24T10:52:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f79b21a57b31363ce249ec538c1e71de4ed9dfcb'/>
<id>urn:sha1:f79b21a57b31363ce249ec538c1e71de4ed9dfcb</id>
<content type='text'>
We want the temporary file to be written in /tmp not the current
directory.

(From OE-Core rev: fcb40c11998030eb5fce89ce5a9ca567870aafa9)

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>bitbake.conf: include machine name in DEPLOY_DIR_IMAGE</title>
<updated>2013-09-14T07:21:00+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2013-09-12T11:04:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6670be71f75c3d7e11362d7c9076ca4de75b50f4'/>
<id>urn:sha1:6670be71f75c3d7e11362d7c9076ca4de75b50f4</id>
<content type='text'>
This allows a clean seperation between image outputs from different
machines, and makes it possible to have convenience symlinks to make
the output ready to deploy.

This did require some surgery in runqemu; if explicit paths to the image
and kernel are not supplied then DEPLOY_DIR_IMAGE needs to be determined
from bitbake or set in the environment. However the script does try to
avoid requiring it unless it really is needed. Corresponding changes
were made in the automated testing code as well.

Based on an RFC patch by Koen Kooi &lt;koen@dominion.thruhere.net&gt;

(From OE-Core rev: 7e90261aec61f79680b5eaeaf5b18c7b795412a4)

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>
</feed>
