A little post today, only to inform you that October 22, PernixData released an update of his server side flash cache software, FVP 1.0.1.
The following issues have been resolved in the FVP 1.0.1 release:
- A VM that is mapped to multiple datastores and is configured in Write Back mode did not transition to Write Through mode, as expected, when a subset of its datastores were removed from the Flash Cluster. Instead appeared as stalled.
- When the virtual disk of a VM are migrated from one datastore to another there were times the VM was stuck in a “vMotion in progress” state and only a subsequent vMotion resolved the issue.
- When a datastore mapped to multiple hosts, some of which do not have FVP installed in them, is added to the Flash Cluster it resulted in the error below: “org.apache.http.conn.HttpHostconnectionException: Connection to http://<IP address of the host without FVP installed> refused”
- Loading the PernixData tab for specific VMs, within the PernixData FVP UI Plugin, may result in the “Error loading VM” message and no data being displayed.
- Loading the PernixData tab for specitic VMs, within the PernixData FVP UI Plugin, may result in the “Cluster Required” message even though the VM is running on a host that is part ofa cluster.
- Configuration changes made via the PernixData FVP UI Plugin do not take effect at times and explicitly refreshing the pages does not help. Shutting down and restarting the vSphere client doesn’t resolve the situation either.
- The ESX scratch location occasionally gets modified under the covers after installing the PernixData FVP Host Extension.
- Over saturating the network can at times simulate a SAN APD and can cause VMs to appear to be hung or crashed.
- The PernixData FVP UI Plugin may at times show extremely high and unrealistic IOPS numbers for the Flash Cluster.
- The VMware vSphere Client may crash at times when a Flash Cluster is deleted.
- When pressing the Now button while using the Custom Time Range in the Performance tab, the PernixData FVP UI Plugin shows stale time.
- Setting the Custom Time Range in the Performance tab by manually entering the time range in the “From” and “To” boxes doesn’t work.
- If a VM does not have a local flash device within its Flash Cluster then it will fail to leverage Network Flash as well.
If you are a PernixData customer or if you are only trying the eval version, you can download this new release with your credentials at the PernixData download portal.
An important note, this patch DOES NOT introduces support for VMware vSphere 5.5