I'm trying to debug a Linux Kernel and need to get a full kernel panic log to figure out what's wrong with it. I'm trying to do this simply by connecting PuTTY via Serial Port to my Linux VM.
Here are the steps that I've done to connect PuTTY and my VM:
VMWare Workstation Pro:
Virtual Machine Settings -> Add Hardware -> Serial Port -> Named pipe: \\.\pipe\com_1, "This end is the server", and "The other end is an application."
PuTTY -> Session -> Connection Type: Serial -> Serial Line: \\.\pipe\com_1, Speed: 115200
Start the VM. When I get to GRUB, I edit my kernel command line by adding console=ttyS0,115200 at the end of it and hit F10. I then hit "Open" on PuTTY. A blank PuTTY session opens and my VM starts the boot process. On my VM, I get this output:
"Wrong EFI loader signature.
early console in extract_kernel
booted via startup_32()
Physical KASLR using RDRAND RDTSC...
Virtual KASLR using RDRAND RDTSC...
Decrompessing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel."
While in PuTTY, it's just a blank console.
Am I doing something wrong? Am I missing something?
If there's any other info I can give, please let me know.
For kernel debugging I tend to change the .vmx by hand.
serial0.present = "TRUE"
serial0.fileType = "pipe"
serial0.fileName = "\\.\pipe\com_1"
serial0.tryNoRxLoss = "FALSE"
serial0.pipe.endPoint = "server"
But so far I only used that with Windows guests on macOS (aka, VMware Fusion) 😉
Seems to me that you need to do a bit more in the linux guest.
Don't forget to turn off graphical splash screens if there are any.