Plain Virtualization

Today marks the announcement from VMware to end the availability in future release of vSphere Client for Windows also known as the C# Client by many.  The last version and will be vSphere Client 6.0.  Any version of vSphere alongside with support will still be released. With this, there will only be one client moving forward in the next release of vSphere (lightly announced in Aug 2016 during VMworld as usual).  As also stated there will be two edition of Web Client in next release namely: Flex and HTML5. There will be plugins from other vendors that will not work since the time to create support for HTML5 will take times, so it makes sense for those who are dependent on those plugin to utilize the Flex.  For users who are not using any Flex dependent plugin, you can fully utilize the HTML5 based web client completely and enjoy the requirement of using Flash and away from the security vulnerability that comes with it. Currently there is a Fling of the HTML5 c...

Some people asked me this question: Will HA be activated if datastore is lost on a host due to iSCSI connection failure or FC connection on just one host without losing the host server from the management network? Though I know the answer however I was curious myself and decide to find out by performing this on a iSCSI connection to see the results.   From my understanding, HA protects hosts failure however as long the host primary detection method (management network) is still alive, the host is considered alive in such, even though the VMs that the host is hosting is "gone" due to perhaps a nic failure for iSCSI connection or a HBA failure for FC connection, HA will not be activated even though datastore heartbeat (only in vSphere 5.x and its a secondary detection if primary failed) is lost. I realize vCenter will initialed a migration of the VM however this will get the process halt.  We have to kill the process and wait for a timeout in order to take...