How to setup serial console access in VMware to capture boot logs for troubleshooting

This document (7018394) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 10 (all Service Packs)
SUSE Linux Enterprise Server 11 (all Service Packs)
SUSE Linux Enterprise Server 12 (all Service Packs)
VMware Workstation, ESX or ESXi

Situation

A virtualized system running on VMware Workstation, ESX or ESXi fails to boot. In order to proceed with troubleshooting support requested to capture the system messages for further analysis to see at which point of initialization the system fails.
The following steps will guide through the steps to connect a virtual serial console to the VM to save the kernel messages to a text file.

Resolution

  1. Shutdown the VM.
  2. Open the settings.
  3. Select the hardware tab and click Add.
  4. Choose Serial Port and hit next.
  5. Select Output to file and click next.
  6. Click Browse and choose a file location inside the VM folder on the datastore.
  7. Make sure the Serial Port gets connected once the machine powers on.
  8. Close the settings.
  9. Power on the virtual machine.
  10. At the boot prompt add the needed kernel options and hit enter.

Once the machine failed to boot, please check the file on the datastore if all messages from starting the kernel up to the error have been recorded and provide this file to support.

In case the file is empty, the serial port might have been connected to tty1/ttyS1 instead of tty0/ttyS0 as shown above. Please adjust the options if needed.

Starting with VMware vCenter the process of adding a serial console is slightly different:

  1. Shutdown the VM.
  2. Right click and select Edit Settings.
  3. From the drop down menu of "New device" select Serial Port and hit Next.
  4. Now just select the file location on the datastore.
  5. Press OK
  6. Power on the virtual machine

It may be advised to increase the BIOS timeout to the virtual machine to its maximum of 10 seconds (10000 milliseconds) to gain more time to react.

In case there is no direct input possibility for the kernel options please select the matching entry on the screen, hit 'e' to edit and add the needed options to the line containing the root volume.

Additional Information

Useful debug kernel options for SLE11:

console=tty0 console=ttyS0,115200 debug ignore_loglevel

Useful debug kernel options for SLE12:

systemd.log_level=debug systemd.log_target=console console=ttyS0,115200
Important: Starting with SLE 12 each installation adds the quiet option to the kernel options line to suppress messages during system boot. Please make sure this option gets removed when gathering boot debug information as systemd acts on this option as well and will provide less output.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7018394
  • Creation Date: 15-Dec-2016
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center