Here is Antti's response for rumprun: https://news.ycombinator.com/item?id=10719055 https://news.ycombinator.com/item?id=10719055 That works even on bare metal

Here is Antti's response for rumprun: https://news.ycombinator.com/item?id=10719055 https://news.ycombinator.com/item?id=10719055 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't think there is a good way to secure them in many environments at this point, but adding spipe might not be too hard. https://github.com/rumpkernel/rumpctrl https://github.com/rumpkernel/rumpctrl 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). https://github.com/justincormack/frankenlibc/ https://github.com/justincormack/frankenlibc/ I'm not sure if NetBSD's kernel debugger or crash dumps work with rump kernels at this point. I haven't played with them myself yet, just keeping an eye on what other folks are doing. And yes, hypervisors also have debugging tools.