<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/scripts/runqemu-internal, branch fido-13.0.1</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=fido-13.0.1</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=fido-13.0.1'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2015-09-18T18:22:24+00:00</updated>
<entry>
<title>runqemu: Handle device names like tapX@NONE</title>
<updated>2015-09-18T18:22:24+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2015-08-09T07:05:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=78b2eaa5163d61e051e0511a6223c344d1b1c2eb'/>
<id>urn:sha1:78b2eaa5163d61e051e0511a6223c344d1b1c2eb</id>
<content type='text'>
ip list can return devices in the form tapX@NONE. If it does so,
ensure we handle that case correctly. Newer distros appear to do
this in some cases.

[YOCTO #8129]

(From OE-Core master rev: 6459dde380febce24d2c355d441d9cb3b14409b9)

(From OE-Core rev: a6709ac54bb9ac79692c3c6faadaace11b8f33f4)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Joshua Lock &lt;joshua.lock@collabora.co.uk&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu-internal: set mutual exclusiveness for serial and nographic options</title>
<updated>2015-06-28T08:44:19+00:00</updated>
<author>
<name>Jagadeesh Krishnanjanappa</name>
<email>jkrishnanjanappa@mvista.com</email>
</author>
<published>2015-06-16T10:48:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9c245f1d7919e5c8109a8f06f02b894e02f61cba'/>
<id>urn:sha1:9c245f1d7919e5c8109a8f06f02b894e02f61cba</id>
<content type='text'>
Use "-nographic" option only if "serial" option is not
specified. Otherwise we get below error when
'runqemu &lt;kernel_image&gt; &lt;rootfs_image&gt; serial' is executed,

(snip)
QEMU 2.2.0 monitor - type 'help' for more information
(qemu) qemu-system-aarch64: -serial stdio: cannot use stdio by multiple
character devices
-- CUT --

(From OE-Core rev: 8b0527951ab71c4a4dc4d1238cd9e9e60a6eb5ee)

(From OE-Core rev: c3a44794de957b216aaea19da371657194c86fc3)

Signed-off-by: Jagadeesh Krishnanjanappa &lt;jkrishnanjanappa@mvista.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu-script: define console for qemuarm NFS booting</title>
<updated>2015-06-28T08:44:19+00:00</updated>
<author>
<name>Jagadeesh Krishnanjanappa</name>
<email>jkrishnanjanappa@mvista.com</email>
</author>
<published>2015-06-16T10:48:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d3959f672a31b498179d0cc3e83705e5f8349a78'/>
<id>urn:sha1:d3959f672a31b498179d0cc3e83705e5f8349a78</id>
<content type='text'>
Add console=ttyAMA0,115200 as one of the boot parameters
for qemuarm, in order to print bootlog messages on the
console.

(From OE-Core rev: 2d2db8f517ea719f097c957559175a07ecee82ad)

(From OE-Core rev: 7113153c50e0d9bb04c6b422be2c75152f3105c9)

Signed-off-by: Jagadeesh Krishnanjanappa &lt;jkrishnanjanappa@mvista.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu-internal: add support to boot arm64 qemu target via NFS</title>
<updated>2015-06-28T08:44:19+00:00</updated>
<author>
<name>Jagadeesh Krishnanjanappa</name>
<email>jkrishnanjanappa@mvista.com</email>
</author>
<published>2015-06-16T10:48:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e9c47914f2f0b0da33623afe2c6ef07640323381'/>
<id>urn:sha1:e9c47914f2f0b0da33623afe2c6ef07640323381</id>
<content type='text'>
Add required boot parameters inorder to boot arm64 qemu
target via NFS

(From OE-Core rev: 0b614317b38b933a4845cd006b0ad734adfa559d)

(From OE-Core rev: 4311b8f59b2a551f2928a4705d4e85901a39995e)

Signed-off-by: Jagadeesh Krishnanjanappa &lt;jkrishnanjanappa@mvista.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu-internal: Add cpio support for qemux86 so that we can boot poky-tiny images</title>
<updated>2015-03-20T11:03:50+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2015-03-19T11:33:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fd2823d13b2d2e6436be895bd6034c185225edb6'/>
<id>urn:sha1:fd2823d13b2d2e6436be895bd6034c185225edb6</id>
<content type='text'>
poky-tiny generates cpio.gz images, add support for these so we can boot
them using runqemu.

(From OE-Core rev: fdd2e0c1baa80106d26236cb734e0d9a98e3fdac)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: Specify rootfstype to qemu to avoid QA warnings</title>
<updated>2015-02-21T22:05:37+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2015-02-21T07:57:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=68f4dcae68f0f99625f9de019eadc4e22d88777e'/>
<id>urn:sha1:68f4dcae68f0f99625f9de019eadc4e22d88777e</id>
<content type='text'>
With the change to ext4 filesystems for qemu, we get boot warnings from where
it tried to mount the ext4 fileystem as ext2 and ext3 first.

Avoid these by specifying the rootfs type directly on the kernel commandline
for ext* images.

(From OE-Core rev: ad9f54a5014f2d997165d0cfd6ad7c05e62f315b)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu-internal: get rid of annoying but harmless error message</title>
<updated>2015-02-03T14:53:53+00:00</updated>
<author>
<name>Chen Qi</name>
<email>Qi.Chen@windriver.com</email>
</author>
<published>2015-01-29T05:44:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f14e96a9cc7b0be01b31e0cff032181482b45751'/>
<id>urn:sha1:f14e96a9cc7b0be01b31e0cff032181482b45751</id>
<content type='text'>
If tap0 interface has been created by other users on the system, we would
get error messages when using runqemu. Error messages are like below.
     Acquiring lockfile for tap0...
     touch: cannot touch ‘/tmp/qemu-tap-locks/tap0.lock’: Permission denied
     /buildarea2/chenqi/poky/scripts/runqemu-internal: line 139: /tmp/qemu-tap-locks/tap0.lock: Permission denied
     flock: 8: Bad file descriptor

The system can still boot up because runqemu would try to create a new tap
interface. So the error message above is harmless, yet somewhat annoying.

This patch fixes the above problem. With this patch, the output would be as
follows.

Acquiring lockfile for tap0...
Acquiring lockfile for /tmp/qemu-tap-locks/tap0.lock failed
Setting up tap interface under sudo
Acquiring lockfile for tap1...
Running qemu-system-arm...

(From OE-Core rev: 039c57257c4180b0688fc2ec1b03948276009b04)

Signed-off-by: Chen Qi &lt;Qi.Chen@windriver.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu-internal: increase memory for qemuarm64</title>
<updated>2014-12-25T08:27:13+00:00</updated>
<author>
<name>Kai Kang</name>
<email>kai.kang@windriver.com</email>
</author>
<published>2014-12-25T08:19:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e3a623bfe39fda16420d2042647af75877bb6f70'/>
<id>urn:sha1:e3a623bfe39fda16420d2042647af75877bb6f70</id>
<content type='text'>
Increase memory to 512M for qemuarm64. The original size 126M can't make
task testimage pass, neither 256M.

[YOCTO #7102]

(From OE-Core rev: 93979b2d025cf318fd0d867ed730721c7594d33b)

Signed-off-by: Kai Kang &lt;kai.kang@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu-internal: Fix qemu networking for qemuarm64</title>
<updated>2014-12-23T10:18:19+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2014-12-22T10:13:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e1858932f98c1ec192479b9a5dcad7b39cbd97ec'/>
<id>urn:sha1:e1858932f98c1ec192479b9a5dcad7b39cbd97ec</id>
<content type='text'>
This brings qemuarm64 into feature parity with the other qemu machines
and enables the automated testing on the autobuilder.

(From OE-Core rev: 31e259f2f2a83c26b8a62b6d7dbca010c6db16bf)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>runqemu: add qemuarm64 support.</title>
<updated>2014-12-23T10:18:18+00:00</updated>
<author>
<name>Kai Kang</name>
<email>kai.kang@windriver.com</email>
</author>
<published>2014-12-18T08:51:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f78f9d7adb25d1c422b6e6f3371f1092c16157e3'/>
<id>urn:sha1:f78f9d7adb25d1c422b6e6f3371f1092c16157e3</id>
<content type='text'>
Update scripts runqemu and runqemu-internal to support to boot
qemuarm64.

(From OE-Core rev: 2f020b53bdb8c262e432bc4df35101fa990c460c)

Signed-off-by: Kai Kang &lt;kai.kang@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
