[OE-core] [PATCH 1/1] runqemu: add ability to skip using an existing tap device
Scott Garman
scott.a.garman at intel.com
Sat Feb 15 19:04:47 UTC 2014
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]
Signed-off-by: Scott Garman <scott.a.garman at intel.com>
---
scripts/runqemu-internal | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
index f9ca380..d317dfd 100755
--- a/scripts/runqemu-internal
+++ b/scripts/runqemu-internal
@@ -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() {
--
1.8.3.2
More information about the Openembedded-core
mailing list