Skip to content

aws-nitro: Separate guest kernel module loading, updates#549

Open
tylerfanelli wants to merge 4 commits intocontainers:mainfrom
tylerfanelli:awsnitro-init-modules
Open

aws-nitro: Separate guest kernel module loading, updates#549
tylerfanelli wants to merge 4 commits intocontainers:mainfrom
tylerfanelli:awsnitro-init-modules

Conversation

@tylerfanelli
Copy link
Member

No description provided.

Nitro enclaves do not allow user input, so it remains unclear if
debugging the init binary would be possible. Strip debug symbols to
shrink the binary size.

Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
Start the debug output proxy immediately after the enclave has booted
(if debug mode is enabled).

Change the debug enclave argument to instead represent enabling
application output, as nothing has to be done by the enclave VM if debug
output is enabled. In this case, output will be printed to the console,
which libkrun will already be connected to and forwarding data to/from.

Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
The krun-nitro-eif-ctl tool allows users to configure the kernel modules
loaded within their enclave. This is done through a directory
`/root` in the initrd. Read this directory and load each
module into the enclave kernel within the bootstrap process.

Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
@tylerfanelli
Copy link
Member Author

cc @jakecorrenti

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant