LiteBox/LVBS and nested virtualization
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
The LVBS kernel platform currently does not consider nested virtualization support. I was able to run it on Hyper-V within a Windows DevBox (nested virtualization), but one stress test (50 concurrent VTL/OP-TEE-SMC calls) failed. This might be related to nested VP/VTL/hypercall handling. Revisit this later.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the LiteBox/LVBS kernel platform and reproduce the failure on Hyper-V within a Windows DevBox with nested virtualization enabled. Investigate nested VP, VTL, and hypercall handling around the stress test of 50 concurrent VTL/OP-TEE-SMC calls. Done means the stress test completes successfully or the nested-virtualization limitation is clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100