oxidecomputer / oxidecomputer/omicron
Image import can perhaps auto-detect and set disk block size
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
I imported the Debian 11 cloud image with disk block size set to 4096, which is different from that of the image (512 bytes). This caused the image to fail to boot up:
It would be good to be able to auto-detect and/or verify the block size since it is conceivable that end users may set it incorrectly.
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 by tracing the image-import entry point and how the configured disk block size is handled for the Debian 11 cloud image described here. Reproduce the mismatch between the image's 512-byte block size and a configured 4096-byte size. Done means import can detect or verify the image block size and prevent an incorrectly configured image from failing to boot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100