On Mon, Aug 12, 2013 at 09:53:00AM +0100, Richard W.M. Jones wrote:
On Mon, Aug 12, 2013 at 10:15:24AM +0200, richard -rw- weinberger wrote:
Found the root cause, patch is on the way.
I can test patches if you CC me on them.
I'm still available to test patches :-) Didn't see anything on
Am 13.08.2013 12:36, schrieb Richard W.M. Jones:
On Mon, Aug 12, 2013 at 09:53:00AM +0100, Richard W.M. Jones wrote:
On Mon, Aug 12, 2013 at 10:15:24AM +0200, richard -rw- weinberger wrote:
Found the root cause, patch is on the way.
I can test patches if you CC me on them.
I'm still
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
On Sun, Aug 11, 2013 at 9:27 PM, Richard W.M. Jones rjo...@redhat.com wrote:
On Sun, Aug 11, 2013 at 09:05:08PM +0200, Geert Uytterhoeven wrote:
On Fri, Aug 9, 2013 at 10:43 PM, Richard W.M. Jones rjo...@redhat.com
wrote:
* UML is pretty fast! It's certainly faster (by a factor of 5) than
OK, I understand what's going wrong and how to reproduce the
signal-to-parent problem. It does look like a bug in vmlinux.
It happens if the init process (PID 1) inside the VM gets a segfault.
In libguestfs we can force that easily, as there is a test path for
exercising segfaults in our init
On Tue, Aug 13, 2013 at 01:04:01PM +0100, Richard W.M. Jones wrote:
OK, I understand what's going wrong and how to reproduce the
signal-to-parent problem. It does look like a bug in vmlinux.
It happens if the init process (PID 1) inside the VM gets a segfault.
To add an additional
