Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supporting development mode for no confidential hardware environments? #570

Open
jinbpark opened this issue Dec 12, 2024 · 2 comments
Open

Comments

@jinbpark
Copy link

Hi, I have a question as to whether SVSM, in the current form, is supporting a kind of simulation mode for no confidential hardware . (e.g., confidential container offers an option to explore its features without confidential hardware- blog article)

It might be allowing other engineers to explore and try out SVSM, without SEV-SNP hardware. As SVSM currently relies on VMPLs for isolation, such (simulation) feature would require developing SW-based isolation that mimics VMPLs but provides no security guarantees.

After a few research, it seems that SVSM doesn't have such a feature. Am I correct? If so, do you have a plan to develop it?

@kraxel
Copy link

kraxel commented Feb 18, 2025

#614 is a baby step into that direction. It allows booting svsm in qemu without sev.

How to load the firmware and handle context switches between firmware/os and svsm is an open and non-trivial question though.

@deeglaze
Copy link
Contributor

How to load the firmware and handle context switches between firmware/os and svsm is an open and non-trivial question though.

We could have a clean handoff and use DICE for the initial attestation.

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

No branches or pull requests

3 participants