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

[Roadmap] Runtime Isolation. QEMU, Hyper-V, and Windows Sandbox #134

Open
gnh1201 opened this issue Aug 27, 2024 · 1 comment
Open

[Roadmap] Runtime Isolation. QEMU, Hyper-V, and Windows Sandbox #134

gnh1201 opened this issue Aug 27, 2024 · 1 comment
Labels
priority:low Don't worry roadmap A future plan

Comments

@gnh1201
Copy link
Owner

gnh1201 commented Aug 27, 2024

Summary

Some runtimes, such as legacy systems, experimental projects, or those with potential security vulnerabilities, need to be executed in isolated environments. Full virtualization and paravirtualization technologies play a crucial role in this. Examples of full virtualization include QEMU and Hyper-V, while Windows Sandbox serves as an example of paravirtualization. This issue will cover the necessity of runtime isolation, the characteristics of each technology, and potential use cases.

Related links

@gnh1201 gnh1201 added the roadmap A future plan label Aug 27, 2024
@gnh1201 gnh1201 added the priority:low Don't worry label Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:low Don't worry roadmap A future plan
Projects
None yet
Development

No branches or pull requests

2 participants
@gnh1201 and others