Did you ever manage to start an interactive getty on the console? #25

Activity

1. cfergeau commented on Feb 23, 2022

   

   cfergeau

   on Feb 23, 2022

   Contributor

   More actions

   I can interact with the VM terminal after starting it with example/virtualization if this is what you are asking?
2. deitch commented on Feb 23, 2022

   

   deitch

   on Feb 23, 2022

   Author

   More actions

   Hmm. Then I'm wondering what I'm doing wrong.

   I'm running it not with a standard distro, but with a composed minimal one. It's got a small script to read cmdline and determine where to start getty. Yet despite starting several - including to /dev/hvc0 - nothing is interacting.

   Do you know what device the actual console is using?
3. deitch commented on Feb 23, 2022

   

   deitch

   on Feb 23, 2022

   Author

   More actions

   Actually, I tried your approach. I just built from example/ dir, pulled down the Ubuntu 20.04.3 iso, extracted the vmlinuz and initrd, set them to env vars, and tried to boot it. It just sits there.
4. cfergeau commented on Feb 24, 2022

   

   cfergeau

   on Feb 24, 2022

   Contributor

   More actions

   You must gunzip the kernel or it will just sit there indeed. (forgot if this step is m1 specific, or is also needed on x86_64)
5. deitch commented on Feb 24, 2022

   

   deitch

   on Feb 24, 2022

   Author

   More actions

   It is an arm64 issue. For some reason, arm64 kernels are gzipped (which qemu and others can handle, but macOS VF cannot 🤷‍♂️ ) while x86_64 use built-in compression.

   It isn't that, I definitely was using an extracted kernel.
6. Repository owner locked and limited conversation to collaborators on Feb 24, 2022
7. Code-Hex

   converted this issue into a discussion #26 on Feb 24, 2022