From: "Richard W.M. Jones" <rjones@redhat.com>
To: Richard Weinberger <richard@nod.at>
Cc: "user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] How to reliably kill all vmlinux processes for a single VM?
Date: Tue, 13 Aug 2013 12:06:51 +0100 [thread overview]
Message-ID: <20130813110651.GX5918@redhat.com> (raw)
In-Reply-To: <520A0F35.8000905@nod.at>
On Tue, Aug 13, 2013 at 12:49:25PM +0200, Richard Weinberger wrote:
> Am 13.08.2013 12:36, schrieb Richard W.M. Jones:
> > In particular I'm having a problem where it looks as if vmlinux is
> > sending a signal to its parent process on shutdown.
>
> Really?
> If so, why does it not kill my shell if I run it directly?
I've no idea. Perhaps you never send SIGTERM to the vmlinux process,
or maybe this is just a very strange bug. Although it happens
reliably in two tests from the test suite, it doesn't happen in any of
the other tests (about 100 of them).
Perhaps I'm wrong about the nature of the bug and the signal is coming
from somewhere else. Is there a way that a process inside the guest
could send a signal to a process on the host? (I would hope not, but
have to ask in case something in the guest is going rogue).
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2013-08-13 11:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 17:48 [uml-devel] How to reliably kill all vmlinux processes for a single VM? Richard W.M. Jones
2013-08-12 7:37 ` richard -rw- weinberger
2013-08-12 8:15 ` richard -rw- weinberger
2013-08-12 8:53 ` Richard W.M. Jones
2013-08-13 10:36 ` Richard W.M. Jones
2013-08-13 10:49 ` Richard Weinberger
2013-08-13 11:06 ` Richard W.M. Jones [this message]
2013-08-13 12:04 ` Richard W.M. Jones
2013-08-13 12:25 ` Richard W.M. Jones
2013-08-15 17:34 ` richard -rw- weinberger
2013-08-15 18:01 ` Richard W.M. Jones
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=20130813110651.GX5918@redhat.com \
--to=rjones@redhat.com \
--cc=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.