PC Case Fan Effectiveness Analysis

A side effect of setting up your own VMWare lab is that, after all is said and done, you end up with a little furnace in a closet.  With Orlando weather, this is mostly unnecessary.

Having recently setup the ELK stack to monitor this VM, I searched for the string ‘temperature’ not knowing what I would find.

Steady Stream Of Temperature Warnings

Bingo, the image above clearly shows temperature warnings from the three hard drives in VM.

Continue reading

Data Science Toolkit on VMWare Error

Tried to run Running Data Science Toolkit in VMWare but get image error?

The OVA image provided seems to have been created in VirtualBox. Attempting to deploy in VMWare give the following error:

The OVF package requires unsupported hardware.
Details: Line 33: Unsupported hardware family ‘virtual box-2.2’.


Using VMWare’s OVFTool, we can convert this image to a ‘VMWare-format’ image as follows,

From the command line,

ovftool.exe -tt=vmx —lax c:\dstk_0.50.ova c:\dstk_0.50.vmx


After a good while, we will end up with VMWare, 60gb disk. That is it… your data science toolkit vm.

VMware Hypervisor Static IP

One of the few frustrating experiences learning VMware Hypervisor has been loosing my server!  At install time, I must have defaulted to automatically getting an IP Address from DHCP.  Twice now, I’ve attempted to login thru vSphere and my server is nowhere to be found.  The hosted VMs are all accessible.  Its just VMware that goes M.I.A leading me to the suspicion that I did something wrong.

My usual fix is to scan my network for devices.


After figuring out which IP Address is my server at now, I proceeded to the servers configuration page on the right and selected networking from the mid-left pane.


Selecting properties from the rightmost panel brings up the networking details for the server.  Here, I can see my new IP Address as well.


Selecting Management Network from the left pane and pressing the edit button brings up the network properties where I can change the IP Address.


Easy enough, I changed my settings to statically set my IP Address.  Done!

Cloning/Backing up a VM in VMware vSphere Hypervisor

One missing feature of the wonderful free version of VMware vSphere Hypervisor is the auto-magic way of cloning a VM.  Nothing I could find at least on this.  There are features for managing snapshots of VMs, for taking snapshots and related tasks, however, to backup/clone a VM, you have to take matters into your own hands. 

Before you follow this steps, ensure the VM you’re about to clone is off.

First step, on your VMWare GUI, from Storage section, right click/browse the datastore where your VM image is stored.


On the Datastore Browser, create a new folder.  This directory will shortly become your cloned VM directory.


Having created a directory for the VM (to be cloned), click on the folder of the VM you want to clone now.  From the contents of this directory, select all the files, skip the logs and right-click copy.  Notice screen-grab shows .ldk and .vswp files.  The existence of these is because I grabbed the image from a running VM.  Remember the VM to be cloned should be shutdown.  These files should not be part of copy/paste steps.


Having copied all the files, go back to the newly created directory and right-click paste these previously copied items.


From all the copied files, right-click the file with the vmx extension and select ‘Add to Inventory’.


Select a name for your newly created VM


Finally, select the location of new VM.  Here you can see me place all ‘Base’ VMs in their own ‘Resource Pool’.  I am only doing this to group together copies I make of any VM I configure.  I haven’t even looked up why I want to use a resource pool for its intended purpose.


You’re done!


As mentioned at the beginning of this post, there may be an official way of creating/cloning VMs in VMware vSphere Hypervisor but I do not yet know how.  This, however, works like a charm, enjoy.  Thanks for reading.