VMware Cloud Community
mrpink37
Contributor
Contributor

BUG REPORT "...kern.notice] vmxnet3s:0: getcapab(0x200000) -> no"

/EDIT changed to bug report (is there any other place where I can file this?) Various users report having the issue using VMXNET3 and Solaris 11 (b173), Solaris 11 Express (b151) and OpenIndiana (b151a)

This issue does not appear with ESXi v4.1 (running same VMs)

Affected systems: Solaris 11 (b173), Solaris 11 Express (b151), OpenIndiana (b151a)

ESXI Version(s): 5.0

Issue: /var/adm/messages gives error "vmxnet3s: [ID 654879 kern.notice] vmxnet3s:0: getcapab(0x200000) -> no" This is repeated every 30 seconds or so (see attached screenshot).


Reply
0 Kudos
19 Replies
Sreejesh_D
Virtuoso
Virtuoso

Is VM hardware and  VM Tools are upgraded? if no, please do so and reboot the VM.

Reply
0 Kudos
mrpink37
Contributor
Contributor

Yes, all vms are vm version 8 and running latest vmware-tools.

Reply
0 Kudos
mrpink37
Contributor
Contributor

So I went ahead and reinstalled latest vmware-tools. Problem persists.

This is what I get upon booting the Solaris vm (see attached)

Reply
0 Kudos
pkam
Contributor
Contributor

Hello,

I have similiar issue on some ESXi 5.0 and OpenIndiana 151a installations.

Is the message anything to worry about? If yes, should we avoid using the driver? If no, how to disable the annoying message in logs and console?

Regards

Piotr

Reply
0 Kudos
mrpink37
Contributor
Contributor

Besides the log getting spammed I haven't noticed any adverse effects so far. Network performance of the Solaris vms is as expected.

Reply
0 Kudos
ytotk
Contributor
Contributor

Anyone know how to disable logging of the message if it is benign?

Reply
0 Kudos
admin
Immortal
Immortal

Hi there -- I have a few clarifications to ask.

(1) Did you notice this in your active production environment ? Could you explain a little more about your environment .

(2) As a system admin , do you constantly tail the logs for these sort of messages ?

Reply
0 Kudos
mrpink37
Contributor
Contributor

Let me clarify. It's not a production environment. It's a small setup for testing purposes running ESXi on a Supermicro X8SIL-F (Dual Intel 82574L Gbit Ethernet)

There is one Solaris 11 vm (b173) with a zfs filesystem where the two other vms are stored; i.e. one Debian 6 (headless) vm and a Windows Server 2008 R2 vm (serving as a RDVH RemoteFX deployment)

And yes, I regularly check logs for irregularities.

Reply
0 Kudos
JamesMC
Contributor
Contributor

Hi,

Has there been any update to this issue, or a bug record made to the developers?

Reply
0 Kudos
mrpink37
Contributor
Contributor

I believe there has not been filed a bug report. Mainly because I don't know where I can properly file one.

Reply
0 Kudos
ajje
Contributor
Contributor

I also get these messages spammed in the message log.

A new entry is added exactly every 30 seconds.

Reply
0 Kudos
alphenit
Enthusiast
Enthusiast

Any news on this..?
I'm also seeing this behavior with the latest ESXi 5 version on a OpenIndiana VM with the latest VMWare Tools.

Aug 26 09:25:51 oizfs01 last message repeated 1 time
Aug 26 09:25:51 oizfs01 vmxnet3s: [ID 654879 kern.notice] vmxnet3s:1: getcapab(0x200000) -> no
Aug 26 09:25:51 oizfs01 last message repeated 1 time
Aug 26 09:26:21 oizfs01 vmxnet3s: [ID 654879 kern.notice] vmxnet3s:0: getcapab(0x200000) -> no
Aug 26 09:26:21 oizfs01 last message repeated 1 time
Aug 26 09:26:21 oizfs01 vmxnet3s: [ID 654879 kern.notice] vmxnet3s:1: getcapab(0x200000) -> no
Aug 26 09:26:21 oizfs01 last message repeated 1 time
Aug 26 09:26:51 oizfs01 vmxnet3s: [ID 654879 kern.notice] vmxnet3s:0: getcapab(0x200000) -> no
Aug 26 09:26:51 oizfs01 last message repeated 1 time
Aug 26 09:26:51 oizfs01 vmxnet3s: [ID 654879 kern.notice] vmxnet3s:1: getcapab(0x200000) -> no
Aug 26 09:26:51 oizfs01 last message repeated 1 time
Aug 26 09:27:21 oizfs01 vmxnet3s: [ID 654879 kern.notice] vmxnet3s:0: getcapab(0x200000) -> no
Aug 26 09:27:21 oizfs01 last message repeated 1 time
Aug 26 09:27:21 oizfs01 vmxnet3s: [ID 654879 kern.notice] vmxnet3s:1: getcapab(0x200000) -> no
Aug 26 09:27:21 oizfs01 last message repeated 1 time

Only place I've seen bugreport possibilities is here:
http://www.vmware.com/support/policies/howto.html

*Please consider awarding points if my response was helpful*
Reply
0 Kudos
mrpink37
Contributor
Contributor

Apparently ESXi 5.1 will support Solaris 11 as guest OS.

Can anyone confirm that this issue is resolved after upgradeing to 5.1?

Reply
0 Kudos
HellMind
Contributor
Contributor

5.1 doesnt even support pass though its too green

I still need a way to SHUT that msg off

Reply
0 Kudos
rkagerer
Contributor
Contributor

I'm having the same problem in a test environment.  Consider this my "upvote" for this bug report!

Reply
0 Kudos
ashleyw
Enthusiast
Enthusiast

Also seeing this same issue on OmniOS (151.004-stable) and NexentaStor (3.1.3.5) all under ESXi5.1 (build 914609) with latest Solaris tools installed with the virtual machine type set to "Oracle Solaris 11 (64-bit) and the virtual hardware level set to 9.

vmxnet3s: vmxnet3s:0: getcapab(0x200000) -> no
last message repeated 25 times

Reply
0 Kudos
geppi
Contributor
Contributor

I have the same issue under ESXi 5.1 build number 799733 patched with ESXi510-201212001 build number 914609.

The problem is experienced in Solaris VMs configured with the vmxnet3 network adapter and VMware-Tools  9.0.1 build-913578 for Solaris.

I get the log messages in an Openindiana 151a7 VM and an OmniOS 151.004-stable VM.

If this log messages does not indicate a real problem I would appreciate a method to stop the spamming in /var/adm/messages and on the console !

Reply
0 Kudos
jgsupport
Contributor
Contributor

Had this issue too, FINALLY resolved in vSphere 5.1U1!!!

From the release notes at http://www.vmware.com/support/vsphere5/doc/vsphere-esxi-51u1-release-notes.html

Solaris 11 virtual machines with VMXNET3 network adapter might write messages to /var/adm/messages in every 30 seconds
Solaris 11 virtual machines with VMXNET3 network adapter might write messages to the /var/adm/messages. The error message similar to the following might be displayed in the system log:
vmxnet3s: [ID 654879 kern.notice] vmxnet3s:1: getcapab(0x200000) -> no
This issue is repeated in every 30 seconds.
This issue is resolved in this release.

Reply
0 Kudos
geppi
Contributor
Contributor

Yes, I can confirm this. After upgrading to ESXi-5.1-U1 and installation of the new VMware-Tools 9.0.5 build-1065307 for Solaris in the OmniOS VM the annoying message is gone.

Reply
0 Kudos