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

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Starting a VM after applying 15 November and up patches on 3.0.2

Duncan Epping · Dec 20, 2007 ·

When patching ESX Hosts with iSCSI attached SAN’s it’s possible you encounter the following event when starting a VM:

“A general system error occured: The system returned an error. Communication with the virtual machine may have been interrupted.”

This is caused by the fact that the “Software iSCSI Client” isn’t enabled on the ESX firewall. November the 15th VMware released a couple of patches which addressed a bug. This bug made it possible to connect via the iSCSI software initiator without enabling the service on the ESX firewall. To open up the port open a console session to the ESX host and type “esxcfg-firewall -e swISCSIClient” or enable it via VirtualCenter “Configuration -> Security Profile -> Properties -> Check Software iSCSI Client”.

Related

Server iscsi, patches, vm, VMware

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist in the Office of the CTO in the Cloud Infrastructure Business Group (CIBG) at VMware. Besides writing on Yellow-Bricks, Duncan co-authors the vSAN Deep Dive book series and the vSphere Clustering Deep Dive book series. Duncan also co-hosts the Unexplored Territory Podcast.

Follow Me

  • Twitter
  • LinkedIn
  • Spotify
  • YouTube

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2023 · Log in