<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/scripts/runqemu-internal, branch dora</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=dora</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=dora'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2013-09-22T11:19:41+00:00</updated>
<entry>
<title>runqemu: set qemuarm memory size back to 128MB</title>
<updated>2013-09-22T11:19:41+00:00</updated>
<author>
<name>Laurentiu Palcu</name>
<email>laurentiu.palcu@intel.com</email>
</author>
<published>2013-09-20T08:06:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=405be52d26d39d94c1682c1b3d3c93f7a9593bfd'/>
<id>urn:sha1:405be52d26d39d94c1682c1b3d3c93f7a9593bfd</id>
<content type='text'>
The following commit, 6ccd4d6, increased the RAM size for qemu machines
to 256MB due to some smart sanity tests failing on autobuilder because
more memory was needed.

Unfortunately this leads to various, potentially dangerous, issues like
the one observed during sudoku-savant project compilation:

collect: relinking
collect2: error: '_ZNK6sudoku5ClearINS_6SquareEEclERS1_' was assigned to
'board.rpo', but was not defined during recompilation, or vice versa
board.o:(.rodata+0x8): undefined reference to
`sudoku::Clear&lt;sudoku::Square&gt;::operator()(sudoku::Square&amp;) const'
board.o:(.rodata+0x20): undefined reference to
`sudoku::Clear&lt;sudoku::Sequence&gt;::operator()(sudoku::Sequence&amp;) const'
board.o:(.rodata+0x34): undefined reference to `typeinfo for
sudoku::Action&lt;sudoku::Sequence&gt;'
...AND THE LIST CONTINUES...
collect2: error: ld returned 1 exit status
make: *** [sudoku-savant] Error 1

After some tests, I found that the maximum amount of memory needed for
sudoku to compile properly is 146MB(!?!).

My attempts to create a simpler test case (using templates), in order to
replicate and isolate the issue failed. All the tests compiled just
fine.

So, my guess is that this problem is certainly memory related but the
cause might be hidden in any of the following: qemu versatile hw model,
in the kernel or, highly unlikely but not impossible, the toolchain
itself. The reason I don't really think the cause is in the toolchain is
the fact that the compilation completes just fine for 128MB on qemuarm but
also on other qemu machines (with 256MB of memory).

Since this issue might need lots of time to have a proper fix, I'll revert back
to using 128MB for qemuarm for the time being.

[YOCTO #5133]

(From OE-Core rev: 06605bd6ddd4d6a788e1a107dcf15dde1027c094)

Signed-off-by: Laurentiu Palcu &lt;laurentiu.palcu@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: set memory size to 256M for most qemu machines</title>
<updated>2013-09-02T17:02:59+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2013-09-02T10:35:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6ccd4d6a9d3910b6e729fe2d00056d8d325403c8'/>
<id>urn:sha1:6ccd4d6a9d3910b6e729fe2d00056d8d325403c8</id>
<content type='text'>
Set memory size to 256M for qemuarm, qemux86, qemux86-64, qemumips,
qemumips64, and qemuppc.

This allows the smart automated tests to run on machines with a GUI
environment (such as Sato) running at the same time, for which 128M is
too limiting. Setting this in runqemu allows users manually using
runqemu to avoid the same out-of-memory issues under similar conditions
using smart, on-target compilation or other uses.

Fixes [YOCTO #5045].

(From OE-Core rev: fe5dfdece98692f8fa731c8d11c907a272266ea5)

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-internal: provide more info if a preconfigured tap is used</title>
<updated>2013-08-30T15:23:47+00:00</updated>
<author>
<name>Chen Qi</name>
<email>Qi.Chen@windriver.com</email>
</author>
<published>2013-08-28T02:52:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5bffc4ff4dde35d2ceb21242c1372113406369ff'/>
<id>urn:sha1:5bffc4ff4dde35d2ceb21242c1372113406369ff</id>
<content type='text'>
We should provide the user more information if a preconfigured tap
is used. This is because the user might have manually set up the tap
interface to be used by other qemu binaries.

So at a minimum, we should let the user know how to make runqemu skip
that tap interface.

[YOCTO #5047]

(From OE-Core rev: ec08d92641cc51c567cc3745937b1839d3faa095)

Signed-off-by: Chen Qi &lt;Qi.Chen@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu-internal: don't bring down preconfigured tap interface</title>
<updated>2013-08-30T15:23:47+00:00</updated>
<author>
<name>Chen Qi</name>
<email>Qi.Chen@windriver.com</email>
</author>
<published>2013-08-28T02:52:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a78bf1ce7bc41ff96f17c532179be517d6474978'/>
<id>urn:sha1:a78bf1ce7bc41ff96f17c532179be517d6474978</id>
<content type='text'>
runqemu-ifup and runqemu-ifdown should be pairs. If we're using a
preconfigured tap interface, the runqemu-ifdown should not be invoked
to bring it down.

(From OE-Core rev: f60f215f74b5fe5a43943c9d3ccdbe0fa06b7828)

Signed-off-by: Chen Qi &lt;Qi.Chen@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu-internal: fix to start X correctly in live images</title>
<updated>2013-08-16T10:14:35+00:00</updated>
<author>
<name>Chen Qi</name>
<email>Qi.Chen@windriver.com</email>
</author>
<published>2013-07-23T02:58:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a7e8f83cbe1eca9f16af2b05c6cad327f80a5ffa'/>
<id>urn:sha1:a7e8f83cbe1eca9f16af2b05c6cad327f80a5ffa</id>
<content type='text'>
The QEMUOPTIONS for ISOFS was not complete, leading to failures when
trying to start X in live images.

This patch fixes this problem.

[YOCTO #4103]
[YOCTO #4884]

(From OE-Core rev: 08947869917dc5a9dfff05b0ee19279f60cf6d2b)

Signed-off-by: Chen Qi &lt;Qi.Chen@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>scripts/runqemu: Add support for 'qemumicroblaze' machine</title>
<updated>2013-07-10T08:41:51+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan.rossi@xilinx.com</email>
</author>
<published>2013-07-04T07:47:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f6538c3b649e19088e0f396f84061086c3cc786a'/>
<id>urn:sha1:f6538c3b649e19088e0f396f84061086c3cc786a</id>
<content type='text'>
* Add support to boot the 'qemumicroblaze' machine in
  qemu-system-microblazeel
* Use the specific machine model for a MicroBlaze system 'petalogix-ml605'
* Use the DTB generated from the kernel build as the DTB for boot
* Force use of initrd rootfs (either in ext or cpio formats)

(From OE-Core rev: 2c164a5dfc877d180ef58d46c063573621297929)

Signed-off-by: Nathan Rossi &lt;nathan.rossi@xilinx.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>scripts/runqemu: Add support for 'qemuzynq' machine</title>
<updated>2013-07-10T08:41:51+00:00</updated>
<author>
<name>Nathan Rossi</name>
<email>nathan.rossi@xilinx.com</email>
</author>
<published>2013-07-04T07:47:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=41563388edbe7f7559070c37c4f5cefd4cf37a96'/>
<id>urn:sha1:41563388edbe7f7559070c37c4f5cefd4cf37a96</id>
<content type='text'>
* Add support to boot the 'qemuzynq' machine in qemu-system-arm
* Use the specific machine model for Zynq 'xilinx-zynq-a9'
* Use the DTB generated from the kernel build as the DTB for boot
* Force use of initrd rootfs (either in ext or cpio formats)

(From OE-Core rev: 1e4b1d95e1f47654e928f38cd091ffe272689844)

Signed-off-by: Nathan Rossi &lt;nathan.rossi@xilinx.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: Replaced "stty sane" with saved stty settings</title>
<updated>2013-05-30T19:59:08+00:00</updated>
<author>
<name>Andrei Dinu</name>
<email>andrei.adrianx.dinu@intel.com</email>
</author>
<published>2013-05-28T08:59:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ff9573f9317c2159b5f1705081d4b472cf717196'/>
<id>urn:sha1:ff9573f9317c2159b5f1705081d4b472cf717196</id>
<content type='text'>
stty manual says :

"sane - Resets all modes to reasonable values for interactive terminal use."

But reasonable isn't the most viable solution, because we want to keep the
original stty settings before running runqemu. Saving the stty settings and
setting them at the end of the runqemu script solves the terminal
settings differences after the script ran.

[Yocto #4512]

(From OE-Core rev: 93e0ae68d2c1827370f4f9e95c2f0b7f98ba2cb8)

Signed-off-by: Andrei Dinu &lt;andrei.adrianx.dinu@intel.com&gt;
[Added filename info in commit subject - sgw]
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>SLiRP support in runqemu</title>
<updated>2013-05-24T13:14:40+00:00</updated>
<author>
<name>Andrei Dinu</name>
<email>andrei.adrianx.dinu@intel.com</email>
</author>
<published>2013-05-20T13:16:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=52c9f6650f4c8fb06636f03803005054aa520191'/>
<id>urn:sha1:52c9f6650f4c8fb06636f03803005054aa520191</id>
<content type='text'>
runqemu script now takes argument "slirp" in order to
run networking on the qemu machine, without root privileges.

changed the runqemu-internal script in order not to activate
the tap devices if the option is set.

[YOCTO #1474]

(From OE-Core rev: fa7fd7b1cbcfbd01af1949d2ea09b880a0ae0175)

Signed-off-by: Andrei Dinu &lt;andrei.adrianx.dinu@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: Replace use of ifconfig with ip</title>
<updated>2013-05-15T21:09:47+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2013-05-13T05:42:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4520feca657ac543267b4c8840e57bb32baf18c3'/>
<id>urn:sha1:4520feca657ac543267b4c8840e57bb32baf18c3</id>
<content type='text'>
ifconfig and its ilk (net-tools package) is deprecated in favour of iproute2 package
and is now removed by many distro's e.g. Archlinux. So we replace ifconfig with ip utility

(From OE-Core rev: c19e5d19ae8e6e6eb9b37549d80765b8315f79a4)

Signed-off-by: Khem Raj &lt;raj.khem@gmail.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>
</feed>
