openembedded-core.git/scripts/runqemu-internal, branch danny Mirror of openembedded-core scripts/runqemu-internal: Fix lock races 2013-03-27T17:25:05+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2013-03-20T22:58:30+00:00 f1a126f2b0f419b2de573e2367d41d8ccc28b346 There are two problems here. Firstly the grep command is unanchored so pid 345 will match against 12345 and so on. The second issue is that there are several context switched between attempting the lock and then writing the pid to it. Between the two issues, there were issues appearing on the autobuilder due to these conflicts. This patch replaces the mechanism with flock on fd 8 which should be a safer mechanism to use. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
There are two problems here. Firstly the grep command is unanchored so
pid 345 will match against 12345 and so on.

The second issue is that there are several context switched between attempting
the lock and then writing the pid to it.

Between the two issues, there were issues appearing on the autobuilder due
to these conflicts. This patch replaces the mechanism with flock on fd 8
which should be a safer mechanism to use.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu: Improve error handling/exit codes 2013-03-27T17:24:44+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2013-03-20T11:48:53+00:00 22a54741167dd6cc011a1b98787c82cc992158ed runqemu-internal is sourced so should be returning with an error code in case of errors. runqemu needs to deal with this. This patch fixes up the various error paths so we're consistent and get a sane exit status for runqemu which helps a lot in its use in the qemu runtime testing on the autobuilder. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
runqemu-internal is sourced so should be returning with an error code in
case of errors. runqemu needs to deal with this.

This patch fixes up the various error paths so we're consistent and get
a sane exit status for runqemu which helps a lot in its use in the qemu
runtime testing on the autobuilder.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu: allow multiple unfs instances to run simultaneously 2012-10-04T13:10:40+00:00 Scott Garman scott.a.garman@intel.com 2012-10-03T22:13:53+00:00 94eef772c283170d19ba92c8de0054cd093fc487 A miscalculation in the way the port numbers of mountd and nfsd are created was causing conflicts when starting multiple instances of qemu using userspace nfs. Thanks to Rudolf Streif for proposing this fix! Fixes [YOCTO #1969] Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
A miscalculation in the way the port numbers of mountd and nfsd
are created was causing conflicts when starting multiple instances
of qemu using userspace nfs.

Thanks to Rudolf Streif for proposing this fix!

Fixes [YOCTO #1969]

Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu-internal: don't append an empty element to PATH 2012-09-28T08:14:01+00:00 Scott Garman scott.a.garman@intel.com 2012-09-26T18:02:27+00:00 1f7f590369eaa76dc970c9cffd1f0db53ce08c00 Bitbake fails to run when an empty element exists in $PATH. Avoid creating this situation when $CROSSPATH is not set. This fixes bug [YOCTO #3101] Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
Bitbake fails to run when an empty element exists in $PATH. Avoid
creating this situation when $CROSSPATH is not set.

This fixes bug [YOCTO #3101]

Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
runqemu: work with tap device names that end with a colon 2012-09-24T10:24:47+00:00 Scott Garman scott.a.garman@intel.com 2012-09-21T22:06:02+00:00 85ed217b603a86113dda11d952850e8ceed30795 On Fedora systems (and likely others), ifconfig returns interface names that end with a colon. Make sure we strip the colon off the tap device name before using it. This fixes [YOCTO #3028] Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
On Fedora systems (and likely others), ifconfig returns interface
names that end with a colon. Make sure we strip the colon off the
tap device name before using it.

This fixes [YOCTO #3028]

Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
qemux86-64: Support for KVM, paravirt and virtio added 2012-09-21T05:21:14+00:00 Cristian Iorga cristian.iorga@intel.com 2012-09-19T07:06:55+00:00 cbb6431b3ee9128ea15c9ae0a19e7d2998ffc561 KVM, paravirtualization and virtio drivers are now activated in runqemu using the kvm option flag for qemux86-64. Host CPU features are also exported to guest OS (Yocto Linux). Usage example: runqemu qemux86-64 core-image-x11 kvm Implements [YOCTO #2550]. Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
    KVM, paravirtualization and virtio drivers are now activated
    in runqemu using the kvm option flag for qemux86-64.
    Host CPU features are also exported to guest OS (Yocto Linux).
    Usage example: runqemu qemux86-64 core-image-x11 kvm

    Implements [YOCTO #2550].

Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
qemux86: Support for KVM, paravirt and virtio added 2012-09-21T05:21:14+00:00 Cristian Iorga cristian.iorga@intel.com 2012-09-19T07:06:54+00:00 a35d03e2eb905de4eadc9c7df5b50bff1fb7f897 KVM, paravirtualization and virtio drivers are now activated in runqemu using the kvm option flag for qemux86. Host CPU features are also exported to guest OS (Yocto Linux). Usage example: runqemu qemux86 core-image-x11 kvm Implements [YOCTO #2550]. Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
KVM, paravirtualization and virtio drivers are now activated
in runqemu using the kvm option flag for qemux86.
Host CPU features are also exported to guest OS (Yocto Linux).
Usage example: runqemu qemux86 core-image-x11 kvm

Implements [YOCTO #2550].

Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
runqemu-internal: New qemu calls it qemu-system-i386 for x86 2012-09-10T12:01:31+00:00 Khem Raj raj.khem@gmail.com 2012-09-07T08:01:17+00:00 b1ccf0202ba66f9be76463df177f11719ab589e8 New qemu calls the x86 system emulator to be qemu-system-i386 which is consistent now so change it in scripts Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
New qemu calls the x86 system emulator to be qemu-system-i386
which is consistent now so change it in scripts

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
scripts/runqueue-internal: Drop enable-gl option 2012-08-20T15:43:12+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2012-08-20T15:07:13+00:00 b6bc580f1cf56c2e771e87dfeadbb1e5d8416fce This is no longer necessary since we've dropped the GL passthrough patches. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
This is no longer necessary since we've dropped the GL passthrough patches.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
runqemu: support booting ramfs-based images 2012-08-17T17:04:09+00:00 Scott Garman scott.a.garman@intel.com 2012-08-13T20:20:38+00:00 b09c45f017da71ff966004752f8e926ea00ac451 Added support for booting ramfs-based images (e.g, poky-tiny) which do not have block device support. This fixes [YOCTO #2612]. Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
Added support for booting ramfs-based images (e.g, poky-tiny) which
do not have block device support.

This fixes [YOCTO #2612].

Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>