Virtual Machine’s Hard Disk greyed out – Unable to resize
I have been asked by an application owner to increase the size of a disk on his applications virtual machine. So I went through the motions of logging into vCenter expecting to undertake a simple task of expanding the disk. However when editing the settings of the VM I noticed the hard disk settings were greyed out as below.
As the Disk File is showing a suffix of “-000001.vmdk” this would imply that there is a snapshot of the VM. So I headed over to snapshot manager to consolidate and no snapshots were present!
I did some forum reading on this issue and found some hints to remove the “lost” snapshot using vmkfstools. However, before trying this method I created a new snapshot for the VM and the consolidated. This returned the vmdk to its expected naming format and I was now able to increase the size of the disk as requested by our application team.
I used powerCLI to consolidate the snapshot but can be done through the GUI too, here is the PowerCLI command I used if anyone prefers that method of working:
$VM = get-vm vmname | get-view
Error when vMotion from ESXi 5.1 to 5.5 Update 3b
I was recently tasks with moving an ESXi cluster from ESXi 5.1 to ESXi 5.5.
I decided to move to the latest update release which was ESXi 5.5 Update 3b (build – 3248547). vCenter had already been upgraded to version 5.5. Your vCenter server version must not be lower than your ESXi hosts to be able to manage the hosts successfully. So you will need at least vCenter 5.5 Update 3b.
I started to put hosts into maintenance mode and perform an upgrade of ESXi via Update Manager. Several hosts were upgraded successfully with only a few remaining on ESXi 5.1. However I was not able to evacuate these hosts while keeping the VMs powered on as I was getting the below vMotion error.
Continue reading “Error when vMotion from ESXi 5.1 to 5.5 Update 3b”
I recently had a Virtual Machine showing as invalid within a vSphere environment.
To fix the issue you need to reload the Virtual Machine. Run the following command from PowerCli.
(Get-VM [VM-Name] | Get-View).Reload()
Once you run the command you should see your Virtual Machine back in the inventory as normal and no invalid status.
How to deploy vRealize Orchestrator 7
vRealize Orchestrator (previously known as vCenter Orchestrator) allows you to design and deploy scalable workflows to automate IT processes. Here is VMware’s description of the product:
Simplify the automation of complex IT tasks with VMware vRealize Orchestrator, which integrates with vRealize Suite and vCloud Suite to further improve service delivery efficiency, operational management and IT agility. Source: vRealize Orchestrator
If this is a tool that you haven’t used yet, this can really make those complex tasks easier to execute. I suggest you give it a try as there is no cost involved either!
Continue reading “How to deploy vRealize Orchestrator 7”
My First VMUG Experience
Last week my local VMware User Group were getting together in Newcastle-Upon-Tyne, England. I decided to satisfy my curiosity and head along to see what the VMUG meetings are all about, here’s a write up in case anyone was considering going to a VMUG meeting and what it entails.
Continue reading “My First VMUG Experience”
Updating ESXi hosts using Update Manager
You may be aware of the recent WannaCry ransomware attack. I mean who wasn’t, right? Internally within our company this caused a bit of a stir around patching and making sure our environment is up to date. Something that is overlooked by a lot of support staff but can be devastating if not kept up to date. At a recent VMUG I attended Michael Armstrong (@m80arm) from VMware was given a presentation on NSX security and asked for a show of hands if anyone’s environment is 100% patched. The result… no hands from 50 attendees! Quite alarming. So let’s go through patching our ESXi hosts using update manager.
Continue reading “Updating ESXi Hosts using Update Manager”
I had been tasked with upgrading an environment from vCenter 5.5 update 2 to update 3e. Sounds straight forward right? Well the environment has SRM (Site Recovery Manager) 184.108.40.206 installed. That shouldn’t be a problem though should it? Let’s start by updating the DR side first.
Continue reading “SRM (Site Recovery Manager) – vCenter 5.5 upgrade Issue”