virt_whp: coconut-svsm self test with 2 procs hangs on ipi test
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 238
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 100
Description
Running coconut-svsm built with hyper-v support, the ipi self tests seem to hang. I suspect that something is broken with our start vp hypercall handling since openhcl does not use it in vtl2.
build the svsm with make test-in-hyperv and run with something like:
cargo run --target x86_64-pc-windows-msvc -- --hv --vtl2 --igvm ~/svsm/bin/coconut-test-hyperv.igvm --com3 console --com1 none --igvm-vtl2-relocation-type disable --late-map-vtl0-policy off --processors 2
Contributor guide
No contributing guide indexed for this repository
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 by building coconut-svsm with make test-in-hyperv and reproducing the hang using the provided cargo run command with two processors. Investigate the start VP hypercall handling mentioned in the report; done means the two-processor IPI self test completes instead of hanging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100