From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: QEmu Script Error Checking
Date: Tue, 11 Oct 2011 11:02:27 -0700 [thread overview]
Message-ID: <4E9484B3.9010605@intel.com> (raw)
In-Reply-To: <4E9463A3.3090005@communistcode.co.uk>
On 10/11/2011 08:41 AM, Jack Mitchell wrote:
> I have run into the following issue where the tap device is in use due
> to the QEmu machine unexpectedly crashing. The error I recieve is here:
>
> http://i.imgur.com/5t9U1.png (appologies for the screenshot but it
> wouldn't let me copy the text)
>
> Is there any leaway for more robust error checking or a way to forcibly
> destroy the tap node to allow a new one to be created?
Hi Jack,
Since qemu is being run from a parent shell script (runqemu), if qemu
were to crash, I would think the parent shell script would continue on
and destroy the tap device normally. Might you be killing the runqemu
process instead of qemu itself?
I'm not sure if there is a way we could reliably force a cleanup of tap
devices when runqemu starts, because we need to support the case where
multiple instances of qemu sessions are running simultaneously (each
with their own tap device). Off the top of my head I think this would
make the state of tap devices non-deterministic.
Furthermore, we support a mode where an administrator can set up one or
more tap devices, allowing the runqemu user to not need sudo privileges.
So checking for the case where a tap device exists but no qemu process
is running wouldn't work.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-10-11 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 15:41 QEmu Script Error Checking Jack Mitchell
2011-10-11 18:01 ` Khem Raj
2011-10-11 18:02 ` Scott Garman [this message]
2011-10-12 10:12 ` Jack Mitchell
2011-10-12 17:52 ` Zhang, Jessica
2011-10-13 12:39 ` Jack Mitchell
2011-10-13 21:07 ` Zhang, Jessica
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E9484B3.9010605@intel.com \
--to=scott.a.garman@intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.