Originally posted by oiaohm
View Post
Yes vkms/KMS based equals as close to a BMC interface as you can get without being a BMC.
Yes software with vkms to create a fake output then software that understands KMS that scrapes the output that kmsvnc demos then run X11/Wayland/TTY on that output then be remote but being treated as if you are local this is something way past your prior solution.
Yes software with vkms to create a fake output then software that understands KMS that scrapes the output that kmsvnc demos then run X11/Wayland/TTY on that output then be remote but being treated as if you are local this is something way past your prior solution.
Of course this brings us back to VNC how to fix up its lack of hand over in VNC protocol.
My preferences would be that the kernel boots with the linux console on the virtual display device when it detects no display hardware or when it's passed the option at boot. Then the kernel requires a private key from the user which matches a public key on the boot media to establish a TLS connection, and then forward it to whichever back end is ultimately chosen (VNC/RDP/SPICE/QXL/pipewire...) So then the display becomes available once the initrd has brought up the network, and that can happen before LUKS passphrase is prompted for mounting /.
Or, I guess another option would be to tunnel USB over ethernet, and then at the client side, present a USB hub with a virtual display adapter, keyboard, pointer, and storage... That could work with a kernel that has compiled-in support for generic USB storage, display, keyboard and pointer. Then even the initrd could come from the client, lol. AFAIK this is doable with today's mainline kernel.
Leave a comment: