Don't spam console with "failed to write to tap" messages #4650
Conversation
A common first experience with firecracker (see e.g. firecracker-microvm#746) is to start a new virtual machine and immediately start getting spammed with messages like: 2024-06-21T22:10:18.189726925 [anonymous-instance:main] Failed to write to tap: Os { code: 5, kind: Uncategorized, message: "Input/output error" } This happens because firecracker will create the tap device if it doesn't already exist, and unlike most vmms it will not configure the device `up` in this case. All that means that this is both a common and an expected situation and does not require this level of notification. Signed-off-by: Lars Kellogg-Stedman <[email protected]>
|
Hi @larsks , As explained in our network setup doc, the first step to use network is to create a tap device: https://github.com/firecracker-microvm/firecracker/blob/main/docs/network-setup.md Also, as mentioned in the issue #764, we recommend to provide an already-created tap interface.
To prevent users from misusing Firecracker, we attempted to make it exit with error when the tap has not been created in issue #754, but we weren't able to find the way to detect that unfortunately.
We think just suppressing the error message doesn't solve the fundamental problem now, but we might get chance of reconsidering it! So could you please provide more information?
Thanks, |
zulinx86
added
the
Status: Awaiting author
A common first experience with firecracker (see e.g. #746) is to start a
new virtual machine and immediately start getting spammed with messages
like:
This happens because firecracker will create the tap device if it doesn't
already exist, and unlike most vmms it will not configure the device
upin this case.
All that means that this is both a common and an expected situation and
does not require this level of notification.
Signed-off-by: Lars Kellogg-Stedman [email protected]