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

A two-way isolation between Realm and RMM #165

Open
jinbpark opened this issue Aug 31, 2023 · 0 comments
Open

A two-way isolation between Realm and RMM #165

jinbpark opened this issue Aug 31, 2023 · 0 comments
Labels
question Further information is requested

Comments

@jinbpark
Copy link
Collaborator

jinbpark commented Aug 31, 2023

A modern secure hypervisor offers a capability to isolate VM (Realm) from VMM (RMM) (i.e., host hyp can't corrupt guest) I think this capability gets really important in confidential computing.

If with memory encryption, it's trivial to get this capability, because, in AMD for example, all confidential VMs are encrypted with per-VM key that only hardware knows. And when the host hypervisor tries to access other VM's page, it's going to get decrypted by a mismatched key (host has a different key), achieving that kind of isolation.

However, when it comes to the CCA spec without memory encryption, it's still unclear to me how CCA offers this isolation at the platform level. (Maybe, without memory encryption, it doesn't offer such isolation? RMM spec doesn't state that clearly.)
For example, through RSI_REALM_CONFIG, RMM can write something into Realm memory space, which can be viewed as breaking VM<->VMM isolation. (Actually, not that good example though)

@jinbpark jinbpark added the question Further information is requested label Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant