Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Enabling serial-line logging for ESX and ESXi 4.1 (1030667)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 19146Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides steps for about enabling serial-line logging for an ESX or ESXi 4.1 host.

It is sometimes helpful to have logs captured independent of disk or network connectivity when troubleshooting issues. Enabling serial logging will send all VMKernel logs (and Service Console for ESX) to the serial port in addition to their normal destination. For more information on network-based logs, see Enabling syslog on ESXi (1016621). For more information on disk-based logs, see Location of ESX log files (1021800).

This article assumes that the serial port on an ESX or ESXi host is connected to a remote computer, and that remote computer is listening for logs on the serial port. For more general information, see the parent article in this series Enabling serial-line logging for an ESX or ESXi host (1003900).

Resolution

ESX and ESXi 4.1 can be configured to send logs to the serial port in three points in time. Collect logs leading up to the point in time that the problem is seen.

After installation and startup

During startup

During installation

After installation and startup

A running ESX or ESXi host can be configured to output log messages via the serial communications port. If the ESX host does not successfully boot, consider configuring it during startup instead.

When configuring an installed ESX host to output log messages via the serial communications port, there are two things which need to be configured:

Configure the ESX or ESXi host VMKernel to send logs to the serial port.

Configure the ESX host Service Console to send logs to the serial port.

Configure the ESX or ESXi host VMKernel to send logs to the serial port

Using the VMware vSphere Client, select the ESX host in the inventory.

Click the Configuration tab.

Click Advanced Settings.

Select the Misc heading.

Set either the Misc.LogToSerial option to 1. This is the default. This enables logging to a serial port.

Select the VMKernel heading.

Set either the VMKernel.boot.com1_baud or VMKernel.boot.com2_baud options to 115200. This is the default. This controls the speed of data send out the serial port.

Set the VMKernel.boot.logPort option to com1 or com2. The default of blank disables use of the serial port for logging.

Note: Changing VMKernel.boot.logPort requires a reboot to take effect.

Configure the ESX host Service Console to send logs to the serial port

This step is only applicable to ESX, not to ESXi. For more information, see VMware ESX and ESXi 3.5 Comparison (1006543).

Login to the Service Console of the VMware ESX being configured, using the physical console or SSH.

Make a copy of the grub.conf configuration file by running the command:

cp /boot/grub/grub.conf /boot/grub/grub.conf-backup

Edit the file /boot/grub/grub.conf using your preferred text editor. For more information, see Editing configuration files in VMware ESX (1017022).

Locate the line starting with kernel.

Remove the quiet option from the kernel line.

Add the console option to the end of the kernel line:

console=ttyS0,115200 console=tty0

For example, this is a line that has been modified:

kernel /vmlinuz ro root=UUID=51beafbf-b273-4195-9a2c-04dd3b7d7786 mem=272M console=ttyS0,115200 console=tty0

Note: This example uses ttyS0 which is the first serial port (COM1). To use the second serial port (COM2), specify ttyS1.

Save the grub.conf file.

Note: The Service Console logging configuration requires a reboot to take effect.

During startup

If an ESX or ESXi host does not successfully boot, serial line logging can be configured using advanced kernel boot-time parameters. This takes effect for the current boot, and does not persist across future reboots.

ESX 4.1 Startup

At the Grub bootloader screen, use the arrow keys to highlight VMware ESX 4.1

Press e to edit the commands before booting.

Use the arrow keys to highlight the line starting with kernel.

Press e to edit the line.

Remove the quiet option from the kernel line.

Add advanced vmkernel options to the line to specify a serial port:

vmkopts=debugLogToSerial:1,logPort:com1

Add advanced Service Console options to the line to specify a serial port:

console=ttyS0,115200 console=tty0

Press Enter to accept the change

Press b to boot.

ESXi 4.1 Startup

At the Loading Hypervisor screen, press Shift + O on your keyboard.

At the Enter advanced options prompt, type the advanced option to specify a serial port:

logPort=com1

Press Enter to boot.

During install

If an ESX or ESXi host does not successfully install, serial line logging can be configured when booting the installer using advanced kernel boot-time parameters. This takes effect for the current boot, and does not persist across future reboots.

ESX 4.1 Installation

At the VMware ESX 4.1 boot menu, use the arrow keys to highlight Install ESX in graphical mode.

Press F2 for other options.

Modify the boot command line by removing quiet

Modify the boot command line by adding the SerialPort option to vmkopts to specify a serial port:

vmkopts=debugLogToSerial:1,logPort:com1

For example, this is a line that has been modified:

initrd=initrd.img vmkopts=debugLogToSerial:1,logPort:com1 mem=512M

Press Enter to boot.

ESXi 4.1 Installation

At the VMware VMvisor Boot Menu, use the arrow keys to highlight ESXi Installer.

Press Tab to edit options.

Modify the boot command line by adding the options following vmkboot.gz to specify a serial port:

LOGPORT=COM1

For example, this is a line that has been modified:

mboot.c32 vmkboot.gz LOGPORT=COM1 --- vmkernel.gz --- sys.vgz --- cim.vgz --- ienviron.vgz --- install.vgz

Press Enter to boot.

Related Information

To configure serial logging on a Cisco UCS blade, see the Cisco Managing Remote Presence documentation.

Note: The preceding link was correct as of January 17, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.

Enabling serial-line logging for an ESXi/ESXi host
VMware ESX and ESXi 3.5 Comparison
Enabling syslog on ESXi 3.5 and 4.x
Editing configuration files in VMware ESXi and ESX
Location of ESX 3.0-4.1 log files

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
コンポーネント VCSServiceManager のインストールがエラー コード「1603」で失敗しました (Installation of component VCSServiceManager failed with error code '1603'.)ログで詳細を確認してください。 (56469)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESX 4.1.x

Take Our Survey

Support Assistant