oxidecomputer / oxidecomputer/falcon
serial console timeouts cause launch failures
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 20
- Forks
- 5
- Avg merge
- 11d 13h
- Merged PRs (30d)
- 2
Description
I'm seeing not-irregular launch failures due to the serial console timing out waiting for data during vm setup.
ERRO launch failed: exec: [sc] cr2: timeout waiting for data
The timeout is likely just a surface symptom of a deeper issue where we are not handling some sequence of bytes on the serial stream as we should.
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 the VM setup launch failure and tracing the serial-console timeout that reports “timeout waiting for data.” Determine which byte sequence or stream-handling case leaves the console waiting, then verify that launches complete successfully when that sequence occurs.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100