nitro: Add CID-specific vsock ports, shutdown status reader, signal handling proxy, device modularization #517
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
In the scenario that multiple containers are running with krun-nitro, hardcoded vsock port identifiers within the host's CID namespace will result in collision since only one VM can use a single port at a time. To avoid this, identify vsock port numbers based on an enclave's CID, which is guarenteed to be unique. This can help reduce collisions. Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
tylerfanelli
requested review from
MatiasVara,
jakecorrenti,
mtjhrc and
slp
as code owners
tylerfanelli
changed the title
tylerfanelli
force-pushed
the
nitro-shutdown
branch
2 times, most recently
from
982adc0 to
164e707
Compare
We're defining a "device" as an outside service provided by libkrun-nitro to a nitro enclave. At time of writing, this includes the arguments writer, network proxy, and output proxy. Most device proxies will likely have the same behavior. That is, they run for the lifetime of the enclave and must exit when either signaled internally (within the enclave) or externally (by libkrun-nitro itself). Given this shared behavior, implement a DeviceProxy trait that will allow proxies to share this behavior. Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
To organize each the configurable device proxies provided to an enclave, collect them all into one list. Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Besides the standard launch environment arguments written to the enclave, device proxy configuration arguments can also be written (if the proxy itself is enabled). Along with the launch environment, also add enclave arguments to the writer from the device proxy list. Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Delegate all device proxy management to the device list, which can spawn and manage multiple threads to provide device proxy services. Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Upon application exit, the enclave will open a vsock connected to the host and write a 4-byte buffer (corresponding to the application's return code) to the enclave. This also serves as the "shutdown signal" to the host, indicating that the enclave is exiting. Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Organize all of the device proxies into one module. Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
tylerfanelli
force-pushed
the
nitro-shutdown
branch
from
164e707 to
f37d333
Compare
Member
jakecorrenti
left a comment
jakecorrenti
left a comment
There was a problem hiding this comment.
left notes for future reference
tylerfanelli
force-pushed
the
nitro-shutdown
branch
from
f37d333 to
7ccd43b
Compare
With long-running applications (e.g. web servers), users will usually terminate the process by sending a SIGTERM signal to the application. Since processes running within enclaves are not controlled by the host OS, the host OS cannot directly send a signal for them to terminate. Implement a signal forwarder (via vsock) for krun-nitro applications. This is done by adding a signal handler device proxy within the enclave that reads 4-byte messages via vsock. These messages are interpreted as signals from the host to the krun-nitro application. In effect, this allows host signals to be forwarded to a nitro enclave. At present, only SIGTERM is supported to signal applications running within enclaves to gracefully shut down. Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
tylerfanelli
force-pushed
the
nitro-shutdown
branch
from
7ccd43b to
06ef780
Compare
jakecorrenti
approved these changes
Jan 22, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.