During a test I used an old disk that has been previously used by Virtual SAN. The disk did not appear during the datastore creation process. I miss a flash drive here:
The problem is that the disk has not been cleared from it's VSAN configuration. It has still valid VSAN partitions, so the ESXi "claims it for VSAN" what makes it impossible to create a VMFS filesystem.
[Last Update April 19, 2014 - Patches available]
There are a lot of news according to the recently published OpenSSL vulnerability. The bug, also known as "Heartbleed", allows attackers to steal informations that are protected by the SSL/TLS encryption.
Is VMware ESXi and the vCenter affected?
There is currently no official statement from VMware regarding this issue. After some research I found affected versions im VMware products. Here are my findings:
The affected versions are OpenSSL 1.0.1 through 1.0.1f.
Read More »ESXi 5.5 affected by OpenSSL CVE-2014-0160 aka Heartbleed
The new coredump file feature in vSphere ESXi 5.5 creates a file to extend the coredump partition. This usually happens when you upgrade from a previous version to ESXi 5.5, or you install ESXi to a USB drive or SD card. This coredump file is created on a random VMFS datastoore by using a smart selection algorithm. This random placement causes different kind of problems, for example when you want to delete a datastore. Another problem might occur in an EMC VPLEX deployment where you want to failover VMs to the secondary site in a PDL situation (VMkernel.Boot.terminateVMOnPDL=1 / Disk.AutoremoveOnPDL=0). Datastores that had a coredump file configured can't get mounted back when the volume leaves the PDL state after a site failure has been fixed.
To workaround this issue you might want to permanently disable the coredump file. You can't just disable it, as it gets created automatically after a reboot.
The following error message appears when you try to delete or unmount a VMFS datastore:
The resource Datastore Name: * VMFS uuid: * is in use.
Cannot remove datastore 'Datastore Name: * VMFS uuid: *' because file system is busy. Correct the problem and retry the operation.
ESXi 5.5 has a new feature to store coredumps in a file residing on a datastore. It may sometimes create this file automatically and thus blocking datastores from being deleted. It also creates a vsantraces directory which blocks a datastore.
Read More »Cannot remove datastore * because file system is busy.
Short post on different connectivity states of a virtual machine and how to fix them.
Read More »VM grayed out as disconnected, inaccessible, orphaned or invalid
One problem that comes up quite often during VMware Virtual SAN Beta testing is that the Network status keeps in the "Misconfiguration detected" state. Sometimes the cluster also shows up with different "Network Partition Groups". This message can be caused by several problems. In this post i am going through the most commonly pitfalls and how to solve them.
Read More »Solve VSAN "Network status: Misconfiguration detected" Problems
At least since vSphere 5.1, a clean DNS and SSL setup prevents from several errors. I've often seen the vCenter Server Appliance failing with the following error message after trying to log in to the vSphere Web Client:
Failed to connect to VMware Lookup Service https://[VCENTER]:7444/lookupservice/sdk - SSL certificate verification failed.
Read More »Failed to connect to VMware Lookup Service during Web Client Login
This is a short list of myths, failures and issues I faced while working with VMware. I think that everyone working with virtualization should know these so i want to share my experiences:Read More »Top 10 VMware Myths, Failures and Issues