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

vmware-dev: No systemd output to console #1489

Closed
zmrow opened this issue Apr 14, 2021 · 5 comments
Closed

vmware-dev: No systemd output to console #1489

zmrow opened this issue Apr 14, 2021 · 5 comments
Assignees
Labels
area/kubernetes K8s including EKS, EKS-A, and including VMW type/bug Something isn't working
Milestone

Comments

@zmrow
Copy link
Contributor

zmrow commented Apr 14, 2021

Image I'm using:
vmware-dev

What I expected to happen:
Using the vSphere web console to view boot output, I expected to see all kernel and systemd messages.

What actually happened:
I see all kernel output, but nothing from systemd and all of the Bottlerocket boot services. The following is the last message before a login prompt:

<ugly time here> vmxnet3 0000:03:00.0 eth0: NIC Link is up 10000Mbps

How to reproduce the problem:
Boot the vmware-dev variant on VMWare and view output using the web console

@zmrow zmrow added type/bug Something isn't working area/kubernetes K8s including EKS, EKS-A, and including VMW priority/p0 labels Apr 14, 2021
@bcressey
Copy link
Contributor

We'll need to add the ability to specify custom kernel command-line arguments in the variant definition, rather than using a fixed console=ttyS0 value everywhere.

@tjkirch
Copy link
Contributor

tjkirch commented Apr 14, 2021

We'll need to add the ability to specify custom kernel command-line arguments in the variant definition, rather than using a fixed console=ttyS0 value everywhere.

I made #1490 to track this, which I plan to do soon. Then, this issue would hopefully just be adding the console line to the vmware-dev variant definition.

@zmrow
Copy link
Contributor Author

zmrow commented Apr 15, 2021

After doing a little research, it seems like once we get the correct console device figured out, we should be able to forward all of systemd/journald's output to it via:

systemd.log_target=console systemd.journald.forward_to_console=1

The kernel should output to all console devices present.

Resources:

  1. https://www.kernel.org/doc/html/v4.14/admin-guide/serial-console.html
  2. https://freedesktop.org/wiki/Software/systemd/Debugging/

@jpculp jpculp self-assigned this Apr 15, 2021
@tjkirch
Copy link
Contributor

tjkirch commented Apr 15, 2021

systemd.log_target=console systemd.journald.forward_to_console=1

I think we can get away with just fixing console since we already get the desired behavior on other platforms that have correct console, but it's good to have backup experiments.

@jhaynes jhaynes added this to the next milestone Apr 19, 2021
@jpculp jpculp added status/needs-proposal Needs a more detailed proposal for next steps and removed status/notstarted labels Apr 21, 2021
@jpculp jpculp added status/in-progress This issue is currently being worked on and removed status/needs-proposal Needs a more detailed proposal for next steps status/in-progress This issue is currently being worked on labels Apr 22, 2021
@jpculp
Copy link
Member

jpculp commented Apr 23, 2021

Merged.

@jpculp jpculp closed this as completed Apr 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubernetes K8s including EKS, EKS-A, and including VMW type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants