vSphere

Online PowerCLI Installation, Quick Steps

Here are some quick steps to installing PowerCLI onto your computer to get you started. I performed the steps listed below on a Windows 10 Computer.

 

Overview

VMware PowerCLI is a command-line and scripting tool built on Windows PowerShell, and provides more than 600 cmdlets for managing and automating vSphere, vCloud, vRealize Operations Manager, and VMware Horizon environments.

Requirements

PowerShell or PowerShell ISE, Internet Connection

Steps

Validate that you have an internet connection. Once done we need to confirm that you can connect to the PowerShell gallery online.

This is done by issues the following command: Find-Module -Name VMware.PowerCLI

 

Next we issue the command: Install-Module -Name VMware.PowerCLI –Scope CurrentUser

If prompted to accept the repository, choose Yes to All and continue

The installation process will begin to download the modules

Later unzipping them

And a short while later the installation will complete

Verify the module by using the following command: Get-Module VMware* -ListAvailable

That’s it, your done.

 

Command list:

Find-Module -Name VMware.PowerCLI
Install-Module -Name VMware.PowerCLI –Scope CurrentUser
Get-Module VMware* -ListAvailable

 

 

VMware vSphere 6.5 Nested Virtualization – Create and Install ESXi 6.5

With vSphere 6.5 and nested ESXi 6.5 hosts I enable myself to get hands on with vSphere advanced features with vCenter without having the physical hardware in my home lab. The advantages to this setup allows me to test out new VMware features or simulate issue that could happen in production.

The term “nested virtualization” is used to describe a hypervisor running under another hypervisor. In this case, I will be installing ESXi 6.5 inside a virtual machine hosted on a physical ESXi 6.5 host.

Requirements:

  • Physical ESXi Host (ESXi 6 – 6.5 – )
  • Physical hardware supporting either Intel EPT or AMD RVI

Steps to setup ESXi 6.5 virtual machine guest:

Log into vCenter or ESXi host with a user with admin credentials. In my case I am using the vSphere web client. *spoiler alert* no more C# (Thick) client for vCenter. However it still works with the ESXi 6.5 hosts.

Switch to the “VMs and Templates” view. Right click a folder and select New Virtual Machine > New Virtual Machine…

Choosing “Custom” configuration select type Other for OS family, doing the same for Guest OS version. *note* Ensure you are choosing 64-bit (Other 64-bit)

Once at the configuration hardware screen; Make a few modifications to the default values.

VM Guest Configuration Settings:

  • Define the CPU to a minimum of 2 or more. This includes cores.
  • Define memory to a minimum of 6GB RAM
  • Define Disk to 2 GB (Thin Disk)
  • Change network adapter type to VMXNET 3
  • Add an addition network adapter (also VMXNET 3)

Additional Configuration Step: Enabling support for 64-bit nested vms

Locate the and expand the CPU properties page and tick the check box next to “Expose hardware assisted virtualization to the guest OS”. This setting will allow you to 64-bit vms inside nested ESXi hosts. Read more about this feature here: https://en.wikipedia.org/wiki/Hardware-assisted_virtualization

Click next and exit configuration

At this point you are ready to install ESXi 6 – 6.5 as a Guest VM.

I leave you with this video of the full process. Thanks for visiting and I hope this helps any of you looking to do the same.

 

Originally posted on my LinkedIn Page:

https://www.linkedin.com/pulse/vmware-vsphere-65-nested-virtualization-create-install-jermal-smith

vSphere 6.5 release notes & download links

 

This weekend I had the fun of getting my hands and feet wet with installs of VMware’s ESXi 6.5 and vCenter 6.5. The links below should be useful to any of you looking to learn about the new release and download bits to install.

Release Notes:

Downloads:

Documentation:

VMware Flings: Embedded Host Client Update

I am excited about the release of VMware Labs Flings release of  version 3 of the Embedded Host Client. For those of you who find yourself out of the loop at time, no worries it happens.  Here is some details about the the embedded host client:

The Embedded Host Client is written purely in HTML and JavaScript, and is served directly from your ESXi host. The installed client is in its development phase at this time and does not have full feature sets, but has implemented a very useful feature set.

These features include:

  • VM operations (Power on, off, reset, suspend, etc).
  • Creating a new VM, from scratch or from OVF/OVA (limited OVA support)
  • Displaying summaries, events, tasks and notifications/alerts
  • Providing a console to VMs
  • Configuring host networking
  • Configuring host services

 

Installation Steps:

  1. Enable SSH on your ESXi host, using DCUI (Direct Console User Interface) or the vSphere web client.
  2. SCP the VMware_bootbank_esx-ui_0.0.2-0.1.3172496.vib to a directory on your ESXi host. In my case I used a shared storage LUN or NFS volume as I will apply this to multiple hosts.
  3. Next issue the following command:

     

Upgrade Steps

  1. Enable SSH on your ESXi host, using DCUI (Direct Console User Interface) or the vSphere web client.
  2. SCP the VMware_bootbank_esx-ui_0.0.2-0.1.3172496.vib to a directory on your ESXi host. In my case I used a shared storage LUN or NFS volume as I will apply this to multiple hosts.
  3. Next issue the following command:

     

Example output from running the above command:

[root@esx1:~] esxcli software vib update -v /vmfs/volumes/nfs/installs/flings/VMware_bootbank_esx-ui_0.0.2-0.1.3172496.vib
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: VMware_bootbank_esx-ui_0.0.2-0.1.3172496
VIBs Removed: VMware_bootbank_esx-ui_0.0.2-0.1.2976804
VIBs Skipped:

 

Tools of choice

WinSCP – http://winscp.net/eng/index.php

Putty – http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

 

For more info on ESXi Embedded Host Client: https://labs.vmware.com/flings/esxi-embedded-host-client

 

Thanks for visiting – jermal

 

OVF Deployment Issue Ubuntu Snappy 15.04-stable (5 cloud)

When you have time, you do something.

Tonight I was headed over the Ubuntu site to grab me the latest version because I was thinking of installing OpenStack when I noticed on their landing page and noticed “Get Ubuntu Core” ; yes something new.

But where is my Raspberry Pi? No worries they have OVF images I can use to deploy to my vCenter Lab here at home. So I started just this and encountered an issue I once had.

Lets walk you through my events.

Downloading the image

  1. Found myself on the Ubuntu Internet of Things landing page: http://www.ubuntu.com/internet-of-things
  2. Located the OVF section of the getting started page: http://developer.ubuntu.com/en/snappy/start/
  3. Downloaded the OVA image (x86): 15.04/stable

Deploying the OVF Template 

  1. Using the vSphere Client, connected to vCenter (or stand alone ESXi host)
  2. Select server to deploy to and choose file > Deploy OVF Template
  3. Browse to the path were you downloaded your OVF image and select it

This is when I received the following error:
The following manifest file entry (line 1) is invalid: SHA256(core-stable-amd64-cloud.ovf)= d4b8922ed38a4eb9055576f7b46f8e92f463398298f3a42af942f25457d4d41c

Troubleshooting Step 1

  1. I extracted the OVA image (core-stable-amd64-cloud) with 7zip
  2. Once extracted attempted the steps detailed above “Deploying the OVF Template”

The same error was thrown once more.

Troubleshooting Step 2

Within the extracted folder exists the following file types: certificate, manifest, ovf (instruction / configuration) and disk image

  1. I remove the SHA256(core-stable-amd64-cloud.ovf)= d4b8922ed38a4eb9055576f7b46f8e92f463398298f3a42af942f25457d4d41c line from the .MF (manifest)
  2. Once removed I attempted the steps detailed above “Deploying the OVF Template”

It failed also, only this time the error started the the remaining SHA256 was also invalid.

Troubleshooting Step 3 – Third time is the charm

  1. Moved into the extracted OVA folder
  2. Deleted the .mf (manifest) file
  3. Followed steps above “Deploying the OVF Template” only this time using the OVF located in the extracted folder

This go around everything worked

So why did this happen?

The template was changed after its creation which invalidated the SHA256 key.  I have made templates myself, only to have to edit something out such as removing a CD Rom reference which later caused me issues.

I hope this helps if you face this incident or something similar

 

Thanks for visiting – jermal

Also published here