runqemu: add ability to skip using an existing tap device

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 <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Garman
2014-02-15 11:04:47 -08:00
committed by Richard Purdie
parent b448cf77d9
commit 46bc59d87d

View File

@@ -178,6 +178,10 @@ else
USE_PRECONF_TAP="no"
for tap in $POSSIBLE; do
LOCKFILE="$LOCKDIR/$tap"
if [ -e "$LOCKFILE.skip" ]; then
echo "Found $LOCKFILE.skip, skipping $tap"
continue
fi
echo "Acquiring lockfile for $tap..."
acquire_lock $LOCKFILE
if [ $? -eq 0 ]; then
@@ -214,7 +218,7 @@ else
fi
else
echo "Using preconfigured tap device '$TAP'"
echo "If this is not intended, use flock on $LOCKFILE.lock to make runqemu skip $TAP."
echo "If this is not intended, touch $LOCKFILE.skip to make runqemu skip $TAP."
fi
cleanup() {