• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

vmkping results in “syscall version mismatch (compiled: 0x7616c4e3, kernel: 0x50f63116)”

Duncan Epping · Feb 22, 2008 ·

When troubleshooting a VMotion problem on an unpatched ESX 3.0.2 update 1 host today I wanted to use vmkping. This constantly resulted in the following error message:

syscall version mismatch (compiled: 0x7616c4e3, kernel: 0x50f63116)

I did not find any useful info on google so I checked the VMware knowledge base, maybe some over at VMware can read my mind or it’s a pure coincidence they just updated the following KB article, it seems to be a bug which is fixed in ESX-1002424. It’s actually mentioned in the release notes… I should read those more often I guess.

Related

Server 3.0.x, Bugs, ESX

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2025 · Log in