Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dmesg logs can interleave with normal programs #1115

Open
sharnoff opened this issue Oct 16, 2024 · 0 comments
Open

dmesg logs can interleave with normal programs #1115

sharnoff opened this issue Oct 16, 2024 · 0 comments
Labels
a/tech_debt Area: related to tech debt c/autoscaling/neonvm Component: autoscaling: NeonVM t/bug Issue Type: Bug

Comments

@sharnoff
Copy link
Member

Problem description

Inside our VMs, all output is aggregated into a single stream. Sometimes this causes logs from the kernel to cut off other logs mid-line, making them much harder to search.

There's also a handful of examples linked in the comments on #578.

This isn't a frequent problem by any means, but it prevents being able to rely on the quality of the logs from our VMs (hence: why this issue is marked as tech debt).

Implementation ideas

A simpler idea could be to direct dmesg output to /dev/console and everything else to some virtio serial device, so that any interleaving would be purely between normal user programs.

Or, implementing #578 might also fix this issue.

@sharnoff sharnoff added a/tech_debt Area: related to tech debt c/autoscaling/neonvm Component: autoscaling: NeonVM t/bug Issue Type: Bug labels Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/tech_debt Area: related to tech debt c/autoscaling/neonvm Component: autoscaling: NeonVM t/bug Issue Type: Bug
Projects
None yet
Development

No branches or pull requests

1 participant