Archive for the ‘vSphere’ Category

“Not enough Physical Memory” error – VMware Workstation problem on Windows 8.1

March 25, 2015 Leave a comment

When I first started virtualising vSphere 6, I had issues with VMware Workstation starting VMs.

I kept getting message “not enough physical memory is available”, when powering on VMs, despite having 16Gb and only attempting to start 1 VM with 1Gb RAM.

To fix this issue, edit c:\ProgramData\VMware\VMwareWorkstation\config.ini and add the line:

vmmon.disableHostParameters = “TRUE”

Then reboot.

Categories: Nested Lab, vSphere Tags:

The New VCP5-DCV exam is out!

January 22, 2014 8 comments

VMware today have announced the availability of a new VCP5-DCV exam.

For students that have attended 5.0 and 5.1 versions of courses, the VCP510 exam will continue to be available for a short time.

For students that attend the new 5.5 versions of the courses, there is a new VCP550 exam available.

This means that if you have studied for the exam having attended a 5.0 or 5.1 version of the course, there is no additional studying required now that 5.5 has shipped.

Hat’s off to VMware as this makes the whole process much easier!

Check out the VCP-DCV requirements at VMware Certified Professional 5 – Data Center Virtualization (VCP5-DCV)

Categories: vSphere

VMware VCA Exams FREE until 31st October 2013

October 9, 2013 2 comments

VMware recently announced VMware Certified Associate certifications as entry level exams for:

Cloud (VCA-Cloud)
DataCenter Virtualisation (VCA-DCV)
Workforce Mobility (VCA-WM)
Network Virtualisation (VCA-NV) – Coming Soon!

Currently you can take all of the exams available FREE!

They can be taken on-line anywhere, so pop along to the VMware Certification site to check out the eLearning materials to prepare, and book your exam with the following code:


For more information on the certification and associated free web based training visit the VMware certification site at

Good luck!

Categories: vSphere

vExpert 2013 awardees announced

June 11, 2013 2 comments

I know it’s a little late, but VMware have announced the vExperts for 2013, and I am thrilled to have been selected this year!

Check out the announcement at vExpert 2013 awardees announced

Categories: vSphere

New vSphere Certificate Automation Tool

April 5, 2013 2 comments

VMware have just released the vSphere Certificate Automation Tool v1.0. This can aid organisations creating their own signed certificates for all vSphere components, instead of using the default insecure self-signed certificates. The tool can be downloaded from this knowledgebase article:

Deploying and using the SSL Certificate Automation Tool (2041600)

Categories: vSphere

vSphere 5.x Storage vMotion does not rename virtual machine files on completing migration

February 1, 2013 6 comments

Since vSphere 5.0 was released, a feature previously avaiable was found to not work anymore.  This feature was that after a successful storage vmotion migration a renamed virtual machines’ files were no longer renamed to match.

This feature has been restored in vSphere 5.0 update 2, and in vSphere 5.1 update 1, however must be turned on.

Having upgraded, the option provisioning.relocate.enableRename must be set in the advanced vCenter Server settings.

Using the vSphere Client, navigate to the Home Page, and select vCenter Server Settings (under Administration), then select Advanced Settings from the left.  The parameter needs to be added with the value true as below:


The vCenter Service (or vCenter Server) will now need to be restarted.  Afterwards Storage vMotion should now rename the files when the virtual machine has been renamed.

This currently is not available for vSphere 5.1, but will be included in a future update.

Categories: Storage, vSphere

Tricking ESXi into seeing an SSD device

January 30, 2013 3 comments

Sometimes supported SSD drives do not appear in the vSphere Client or Web Client as an SSD, but instead as unknown or Non-SSD.

It is possible to use storage claim rules to alter this behaviour, to be able to use the ESXi host cache feature in ESXi 5.0 and above.

To start with, it is important to identify the device that is being reported incorrectly.


As you can see from the vSphere Client above, the datastore created as SharedSSD is reported as Non-SSD.

We need to identify the device that this datastore has been created on, one possible way would be to go into the properties of the datastore, and then enter the manage paths screen as shown below.


Notice that the SATP (Storage Array Type Plugin) used for this device is VMW_SATP_DEFUALT_AA, we will need this with the device id.

We can then right click on the path and copy the name to the clipboard. In this case that would contain all the detail after Name: in the lower window. The only detail required is in this case the iSCSI t10 number.

(Although in this example we have already created a datastore on the device, it would be possible to configure a device that does not currently have a datastore as SSD except we would need to identify the device via the storage adapter.)

Once we have the device id, and SATP we can than use the esxcli command line tool (found in the ESXi shell, and vCli and vMa) to configure a claim rule.

The first setup is to create the claim rule with the required optional parameter to enable SSD.


The next step is to ensure that the claim rule has been added.


Notice that the claim rule previously entered is displayed as a result of the command.

Now we need to reclaim all claim rules to ensure that SSD is now enabled for this device.


Notice that in this case it was unable to unclaim the path. This can happen sometimes, and is easily fixed with a reboot of the host.

Alternatively, unclaim the device:

esxcli storage core claiming unclaim -t device -d t10.945445000000000023030000000000000000000000000000

Then load, and run the claim rule:

esxcli storage core claimrule load
esxcli storage core claimrule run

If you do not get the unable to reclaim message detailed above, you can now confirm hat the rule has been applied and that the device is now seen as SSD.


As you can see in the above, the value for Is SSD: is true.

You should now see the datastore listed as SSD in the client.


It is also possible to use this method to allow the use of SSD for host caching when using a nested setup for testing.