• 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

Duncan Epping

Virtual Iron 4.2 released

Duncan Epping · Dec 23, 2007 ·

Virtual Iron 4.2 has officially been released. Virtual Iron uses the Xen Hypervisor and positioned their product “Virtual Iron Enterprise Edition” as a competitor of VMware ESX. This new release includes a couple of long awaited features:

[Read more…] about Virtual Iron 4.2 released

VMware ESX 3i installable general availability

Duncan Epping · Dec 21, 2007 ·

VMware just officially released VMware ESX 3i, you can download the installable iso here. For now it’s only supported on Dell Poweredge 2950(Full) and HP DL380G5(Experimental) servers. Check out the installable, I booted it within VMware Workstation and right until I tried to boot a VM it worked fine, than it crashed. [Read more…] about VMware ESX 3i installable general availability

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”.

Ghosted devices

Duncan Epping · Dec 18, 2007 ·

After a p2v there are several “ghosted devices” left in the VM. This could for instance cause a message about having already assigned the same ip-address to another NIC when configuring your network.

This problem is caused by hidden devices which should be removed after a P2V:

  1. Within Windows open up the command prompt
  2. type “set devmgr_show_nonpresent_devices=1”
  3. start “devmgmt.msc”
  4. Click on “View” and select “Show Hidden Devices”
  5. Uninstall all grayed out devices
  • « Go to Previous Page
  • Go to page 1
  • Interim pages omitted …
  • Go to page 475
  • Go to page 476
  • Go to page 477

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the "vSAN Deep Dive", the “vSphere Clustering Technical Deep Dive” series, and the host of the "Unexplored Territory" podcast.

Upcoming Events

May 24th – VMUG Poland
June 1st – VMUG Belgium

Recommended Reads

Sponsors

Want to support Yellow-Bricks? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2023 · Log in