Hi, On Monday, August 17, 2020 at 2:24:17 PM UTC-4 Alex Merritt wrote:
> Hello! > > If one were to make changes to both Firecracker and OSv (e.g., in the > para-virt interfaces) what options are there for debugging guest kernel > state? I understand booting OSv alternatively on KVM/QEMU would make > inspection possible, but doing so requires changes I wish to test to be > implemented in QEMU. > > Folks working on Firecracker tell me it does not have a gdbserver > implementation like QEMU does, thus this path is not possible, currently. > > How do you / would one go about debugging OSv behavior as a guest within > Firecracker? > I am afraid your only true debugging option on Firecracker is old-fashioned (:-) printf/log statements to the console. Alternatively, you can also use the monitoring and tracing mechanisms OSv provide - https://github.com/cloudius-systems/osv#debugging-monitoring-profiling-osv. Maybe others have better ideas. > > Thanks, > Alex Merritt > -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osv-dev/2f963164-bd43-478a-84d3-dc18b8f7a330n%40googlegroups.com.
