precice-profiling fails in Virtualbox on Windows
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8
- Forks
- 7
- Avg merge
- 10m
- Merged PRs (30d)
- 3
Description
In some instances, CPU features (AVX, AVX2, FMA) cannot be forwarded from the Host to the Guest.
The precice-profiling dependency polars requires those and will refuse to run.
This seems to happen when vagrant runs using VirtualBox on a Windows Host while Hyper-V is enabled.
Disabling it seems to be tricky.
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 reproducing precice-profiling with Vagrant and VirtualBox on a Windows host where Hyper-V is enabled. Investigate whether the guest receives AVX, AVX2, and FMA CPU features, then document or implement a confirmed way to run the dependency when those features cannot be forwarded.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100