Here is Antti&#x27;s response for rumprun:
<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10719055" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10719055</a><p>That works even on bare metal if the network works.  Similarly, there are remote system calls that can be used for netstat and such.  I don&#x27;t think there is a good way to secure them in many environments at this point, but adding spipe might not be too hard.
<a href="https:&#x2F;&#x2F;github.com&#x2F;rumpkernel&#x2F;rumpctrl" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rumpkernel&#x2F;rumpctrl</a><p>There is also frankenlibc where you can run the application as an actual userland process (but still with the rump kernel) under a variety of operating systems.  I think applications that run on one (frankenlibc or rumprun) should be able to run on the other without changes (other than build related).
<a href="https:&#x2F;&#x2F;github.com&#x2F;justincormack&#x2F;frankenlibc&#x2F;" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;justincormack&#x2F;frankenlibc&#x2F;</a><p>I&#x27;m not sure if NetBSD&#x27;s kernel debugger or crash dumps work with rump kernels at this point.  I haven&#x27;t played with them myself yet, just keeping an eye on what other folks are doing.  And yes, hypervisors also have debugging tools.