-
-
Notifications
You must be signed in to change notification settings - Fork 51
Open
Description
I haven't had the time to properly diagnose this issue and I think it may have to do with libkrun itself rather than muvm, but I'm writing about it here and maybe someone can come and chime in how I'm holding it wrong.
The "main" muvm process, that is, the one that started the VM, always returns exit code 1, regardless of what happens inside the VM and how it exits. This is not the case for "child" processes, which only just request launching a process in the VM, as in those cases the status code is reported as it should be.
I'm seeing this behavior on muvm 0.3.1 with libkrun 1.10.1, I haven't tried tried master for either (yet).
Metadata
Metadata
Assignees
Labels
No labels