oxidecomputer / oxidecomputer/propolis
implement CPUID profiles
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 270
- Forks
- 42
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 6
Description
RFD 314 documented the proposed contents for CPUID leafs presented to the guest. We need to make that a reality for guests by:
- Wiring up propolis to be able to configure the in-kernel vmm CPUID tables for the vCPUs
- Build logic to read in a CPUID "profile" (presumably correlated to a given version of the instance profile) and customize it with any instance specific (vCPU count/topology) details
- Determine how this CPUID data will be handled during a migration
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 reading RFD 314 and tracing how propolis configures the in-kernel vmm for vCPUs. Define the CPUID profile input, instance-specific vCPU topology customization, and migration handling; done means guests receive the intended CPUID data consistently across migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100