linux/poky.git/scripts/runqemu-internal, branch 1.8_M2

runqemu-internal: increase memory for qemuarm64

2014-12-25T08:27:13+00:00

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 Signed-off-by: Richard Purdie

runqemu-internal: Fix qemu networking for qemuarm64

2014-12-23T10:18:19+00:00

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

runqemu: add qemuarm64 support.

2014-12-23T10:18:18+00:00

Update scripts runqemu and runqemu-internal to support to boot qemuarm64. (From OE-Core rev: 2f020b53bdb8c262e432bc4df35101fa990c460c) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

runqemu-internal: add "console=ttyS0" to ramfs image kernel parameters

2014-05-21T08:09:02+00:00

We need this kernel command parameter so that when we start a ramfs image, we can actually get some output. Although we can make this happen by specifying the 'bootparams' for the 'runqemu' command, it's better to make this the default behaviour. (From OE-Core rev: 3d202594bb92fe75cd70f81345e64c2179b52c32) Signed-off-by: Chen Qi Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

runqemu: add ability to skip using an existing tap device

2014-02-17T15:37:17+00:00

Support the sitauation where a user could have another VM running which uses tap devices. To prevent runqemu from trying to use the same tap device, runqemu will skip using a tap device if it finds a filename tapX.skip within its lock directory. This fixes [YOCTO #5815] (From OE-Core rev: 2e490f3b08176b20fe41c64cf17ecf3b5af61f39) Signed-off-by: Scott Garman Signed-off-by: Richard Purdie

runqemu: enforce right CPU type for qemux86/x86-64

2014-02-13T17:53:30+00:00

Set in accordance with qemu machines configs. Fixes [YOCTO #5817]. (From OE-Core rev: 0e5cfef90ff762b33da6dc301dfc9cb3947c8a02) Signed-off-by: Cristian Iorga Signed-off-by: Richard Purdie

scripts/runqemu-internal: use -cpu core2duo for qemux86-64

2014-01-28T18:01:47+00:00

Now that the tune for qemux86-64 changed to core2-64 we need to tell the emulator to use a proper CPU model. With the default setting of qemu64 we'll get things like: root@qemux86-64:~# smart --help traps: python[758] trap invalid opcode ip:7f2af01f6be7 sp:7fff49466ef0 error:0 in strop.so[7f2af01f5000+6000] Illegal instruction If the tune for qemux86 changes, that needs to be updated too. (From OE-Core rev: e6ade33a6f52434e884dd97549b8ac731347d9ad) Signed-off-by: Stefan Stanacar Signed-off-by: Richard Purdie

runqemu, runqemu-internal: Allow slirp for NFS and KVM use

2014-01-28T00:52:36+00:00

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 Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

runqemu: Use the newer unfs3 for serving user space nfs

2014-01-28T00:52:35+00:00

This new version correctly handles the 64bit ext3 / ext4 issues we were seeing with the older unfs-server which did not handle 64bit file systems correctly, producing the duplicate cookies. [YOCTO #5639] (From OE-Core rev: 2a59d55f712bbd79b1edf3ccb90ccabf609c9f0d) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

runqemu: Allow user to set -vga option with qemuparams

2013-12-20T12:26:30+00:00

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 Signed-off-by: Saul Wold Signed-off-by: Richard Purdie