Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[PromiseRejection: [object Object]]

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

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Understanding Invalid Opcode messages (1003278)

Last Updated: 1/29/2014Categories: InformationalTotal Views: 22798Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

This article provides information about Invalid Opcode messages that can be logged in a VMware ESX host's VMkernel log file, or a VMware ESXi host's messages log file.

For more information about log file locations, see Location of ESX 3.0-4.1 log files (1021800) or Location of ESXi 3.5-4.1 log files (1021801).

VMkernel Invalid Opcode messages appear similar to:

itvmw15 vmkernel: 0:23:58:15.339 cpu0:1062)SCSI: 215: Invalid Opcode (0x4d)

itvmw15 vmkernel: 0:23:58:15.668 cpu1:1062)SCSI: 215: Invalid Opcode (0x4d)

If a virtual machine fails citing a fault 6 or Invalid Opcode, see A virtual machine fails with the internal monitor error: VMM64 fault 6 (1003253).

You may see the entries in vmkernel.log with error:

Feb 28 21:58:42 vmkernel: 0:04:59:50.442 cpu7:15306)VSCSIFs: 329: handle 8199(vscsi0:0):Invalid Opcode (0xd1)

Feb 28 21:58:42 vmkernel: 0:04:59:50.511 cpu4:15200)VSCSIFs: 329: handle 8196(vscsi0:0):Invalid Opcode (0xd1)

If an ESX host is displaying a purple diagnostic screen containing Exception Type 6 or (#UD)Exception 6, see Understanding Exception 6 purple diagnostic screens (1025211).

Solution

This issue is resolved in VMware ESX and ESXi 4.1 Update 3. For more information, see the VMware ESX and ESXi 4.1 Update 3 Release Notes.

Invalid Opcodes are usually logged by the SCSI (ESX host storage) or VSCSI (virtual machine storage) modules in one of these conditions:

A SAN target does not support a command or operation issued by an ESX Server:

This may be as part of regular operation, an agent's request, or by a virtual machine.

Required commands should not return with Invalid Opcode. In such cases, review the SAN configuration for error and compatibility with ESX, and if necessary involve the storage vendor for further assistance.

The host has received undefined or unsupported storage commands from a virtual machine guest operating system, dispatched by the virtual machine's virtual SCSI adapter:

These messages are usually the result of running hardware monitoring agents in a guest virtual machine.

This can result in instability of the virtual machine and its guest operating system, in rare cases. Disabling and/or removal of these agents should be regarded as a priority troubleshooting measure.

A combination of these two conditions is also possible. This occurs when a virtual machine guest has issued commands or operations through ESX and toward the SAN storage target, but the operation is not recognized or supported by the target.

Note: To understand Opcode logging in greater detail, see the Identification section in this article.

Steps

If the virtual machine has been converted from physical host hardware, verify that the hardware monitoring agents have been disabled and/or removed prior to the conversion.

Check the deployed virtual machines for residual agents or processes that were originally intended for use on physical host hardware. While virtualized, hardware management agents are usually unable to provide the full extent of their intended functionality and may instead result in errors or further problems.

Due to the potential stability issues which may arise from running system/platform-specific hardware agents on virtual hardware, VMware recommends that you disable and/or remove them if present, unless explicitly designed and supported for use in a virtual machine by the respective hardware or application vendor.

Identification

Example: See this vmkernel log output of an ESX server. This message was generated because the SAN target did not support the attempted command or operation.

itvmw15 vmkernel: 0:23:58:15.668 cpu1: 1062)SCSI: 215: Invalid Opcode (0x4d)

In these error messages:

The involved virtual machine can be identified by examining the CPU value. This number identifies a World ID for a virtual machine.

The specific illegal SCSI operation or command can be identified by the value specified after the Invalid Opcode message, above. This hexadecimal value would usually conform to SCSI specification. For more information about these values, see SCSI Command Operation Codes at http://www.t10.org/lists/2op.htm.

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

To correlate this World ID with a specific virtual machine, use one of the methods described in Mapping a virtual machine world number to a virtual machine name (1001101).

Summary of Example

Hexadecimal value 0x4d translates as LOG SENSE. This command is used to obtain current data from the log pages of a SCSI target, for diagnostic purposes. When additional feedback (supported log pages) is provided in response to processing this command (at the SAN target), error counters can be retrieved by the initiator. This ultimately provides diagnostic metrics for monitoring software.

In this context, the SAN target does not support this command.

In this example, the guest operating system ran storage monitoring agents and attempted to query these log pages via a 0x4d (LOG SENSE) command, above, on a Raw Device Mapping (RDM) virtual disk.

To resolve this issue, the guest operating system should be reviewed, by disabling or removing of any hardware or storage monitoring agents responsible.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
ESXi ホストにおいてローカルストレージへのログ出力が停止する (2001442)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
VMFS データストアを拡張できず、[増加] ボタンが無効化される (1035285)

Results 1-4 of 4

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 vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX Server 2.5.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant