-
Notifications
You must be signed in to change notification settings - Fork 33
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
[arm64] The initrd stage VNC console does not have output when running on QEMU-KVM #1553
Comments
Try adding |
To give more context what happens, as there are two scenarios that behave a little bit different. Scenario 1: ARM64 QEM-KVM Flatcar instance using qemu-kvm commandsThis scenario can be easily reproduced on an ARM64 box (DO NOT USE emulation), with the command:
In this scenario, after the VM is started and a VNC console is opened, one can see in the VNC console, in this order: the TianoCore bootloader, Grub 2 with the Flatcar boot options (default, usr-a, usr-b), NOTE that between the Scenario 2: ARM64 QEM-KVM Flatcar instance using libvirtExample Libvirt XML:
Curiously, the video device as set in the libvirt config xml translates to a qemu-kvm command NOTE that in scenario 2, the message is More debug is required. |
The ARM64 ttyAMA0 is already set correctly in the bootengine. This most likely looks like an initrd issue with either a missing kernel module not built or kernel parameter or even systemd parameter. |
My bad, it is set correctly inhere: https://github.com/flatcar/scripts/blob/main/build_library/grub.cfg#L82 |
ttyAM0 is a serial console, vnc connects to a graphical console. If you want to see boot output on both you need to set tty0 as well |
Unfortunately, it does not work, at least on my environment - I tried to add the |
Description
On ARM64, when booting on QEMU-KVM with VNC enabled, the VNC console does not show any output in the Flatcar initrd stage early boot stage.
Impact
No way to debug from VNC if any ignition or initrd stage error appears.
Environment and steps to reproduce
TBD.
Additional information
Please add any information here that does not fit the above format.
The text was updated successfully, but these errors were encountered: