vSphere

vSphere Customization Specification and Ubuntu 17.10

Has anyone noticed issues with #vSphere Customization Specification and #Ubuntu 17.10 (GNU/Linux 4.13.0-25-generic x86_64) – Now that the network settings are located in: /etc/netplan/01-netcfg.yaml, I’m back to manually updating IP information (Server Naming still works).

Although the traditional /etc/network/interfaces reflects the information provided by the customization process, the host still acquires a DHCP issued address. After some digging I was able to find out that this information was no longer being referenced and is now being pulled from:/etc/netplan/01-netcfg.yaml

Here are the IP configuration details

/etc/network/interfaces:

/etc/netplan/01-netcfg.yaml:

Cannot remediate host because it is part of HA Admission Control enabled Cluster

Recently my team and I ran into incident with and error while patching esxi servers using VMware Update Manager(VUM).  When attempting o remediate the following error message was shown:

“cannot remediate host because it is part of HA Admission Control enabled Cluster”

Cause:

vCenter Server uses admission control to ensure that sufficient resources are available in a cluster to provide failover protection and to ensure that virtual machine resource reservations are respected.

Admission control imposes constraints on resource usage and any action that would violate these constraints is not permitted. If an automated process needs to take actions, it might temporarily violate the failover constraints.

 

Solution:

Before patching of the ESXi Servers that are part of the HA Cluster, make sure you have disabled “Admission Control”. Once server has been patched you can re-enable Admission Control on the cluster.

 

Steps to disable Admission Control

  • Right-click the cluster and click Edit Settings.
  • Under Cluster Features, click VMware HA.
  • Under Admission Control, select Disable: Power on VMs that violate availability constraints.
  • Click OK

This can also be disabled in the VMware Update Manager remediation wizard. When you remediate check the option “Disable High Availability admission control if it is enabled for any of the selected clusters.

 

Re: Why you should upgrade to vSphere 6.5 / ESXi 6.5

Recently I went to extend a volume on one of my guest systems and received an error requiring me to power off the system before extending the disk.

ErrorHot-extend was invoked with size (5368709120 sectors) >= 2TB. Hot-extend beyond or equal to 2TB is not supported. The disk extend operation failed: msg.disklib.INVAL

Good News – With vSphere 6.5 this is no longer a limitation.

Just one more reason why you should think about upgrading your VMware environment to the latest.

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