Virtual Machine - Edit Settings (CPU) Part 3 (iii)

In my previous post, I have talked about CORE.

Now in this Part 3, We are going to talk about ENABLE CPU Hot Add.

In this screenshot as you can see, I have used vSphere Web Client, Right Click on virtual machine & edit settings.

3.ENABLE CPU Hot Add: This feature lets you add or remove CPU resource to a powered ON virtual machine.
It should be supported by the operating system and should be turned on in advance i.e If VM is running then this option is grayed out. In order to turn it, VM should be in POWERED OFF state.

 

This information is from Windows Server 2012 R2 Standard Edition.

Once CPU Hot Add is enabled: 

This information is from Windows Server 2012 R2 Standard Edition.

Now if you want to decrease the number of CPU, that can only be done if VM is powered OFF.

We are able to edit get this CPU option, I have installed Windows Server 2012 R2 Standard Edition. VMware has published these KB articles related to CPU Hot Add Feature: KB2020993, KB2051989 which relates to this feature for various operating systems.

Virtual Machine - Edit Settings (CPU) Part 1 (ii)

In my previous post, I have talked about CPU.

Now in this Part 2, We are going to talk about CORE.

In this screenshot as you can see, I have used vSphere Web Client, Right Click on virtual machine & edit settings.

CPU Settings:-
2.CORE: Here I have shared an example of single socket , quad core processor.
Initially when VMware released CORES PER SOCKET, it was there to deal with software licensing issue. So as to reduce number of licenses , which were based on SOCKETS.  Further, for performance it is beyond the scope of this blog post which includes: NUMA, vNUMA CPU technologies.

An interesting example is given on this KB:2078069

Virtual Machine - Edit Settings (CPU) Part 1 (i)

In order to learn more, one has to explore more.
In this series of blog post, i"ll be talking about all the options one have for a virtual machine.

This is Part 1 of virtual machines & I"ll be explaining and giving real time examples for all these options which are available for a virtual machine. In the end, we want our virtual machines to be running healthy. Hell Yeah!!

In this screenshot as you can see, I have used vSphere Web Client, Right Click on virtual machine & edit settings.

CPU Settings:-
1.CPU: It depends on your physical processor(Socket & Cores Per Socket) that are present on your server.
As you can see in my case, what my host(ESXi) has, I can that as LCPU to my VM.
If there is no hyperthreading than the total number of LCPU =8 & if it is enabled then the total number of LCPU=16. VCPU(Virtual CPU for VM) is scheduled on LCPU(Logical CPU, part of core).

So, In my case, the maximum number of vCPU that can be assigned to the VM =16.

Amazon AWS & Microsoft Azure Part 1. - Virtual Machines

I was very keen to learn about these two CLOUD giants namely Amazon's AWS & Microsoft's Azure.  So I started to explore about them that how are they similar and different from their offering perspective.

Both of them are Public Cloud offerings as most of the people are aware of it. So let's just start.
Azure has near to 68 offerings that one can choose from their big list whereas AWS has near to 100 offerings. Further, you can check their offerings on other blog posts. Like TOM's IT ProT has a very good comparison of it.

Starting with their Virtual Machine Related Services:-

AWS - EC2 ( Elastic Compute) & Azure Virtual Machines (Compute)

Here you can choose from a wide variety of Virtual machine instances that you can deploy and start using. So will start how to create a VM in EC2 and end with AWS Virtual machine.


Step1. Need to setup an account for AWS & Azure .

AWS has various type of Instances available, in layman's terms size of virtual machines. I"ll be using a Free Tier instance which will be T2.Micro

Similar way how to create a EC2 instance, you can check on  Amazon tutorials as well.

Azure has different size of Virtual Machine available.

Installing PowerShell & PowerCLI in MAC OS

Mac Install 

Install These are the detailed instructions. 

Step 1 - Download PowerShell for MAC and need to check whether it allows you to install if gives you an error related to the unidentified application. To resolve this, click the Apple symbol in the menu bar and open System Preferences > Security & Privacy and then click Open Anyway.
Installed will be there and install.

Step 2 - Make sure you did not miss this step from the PowerShell installation instruction:

brew install openssl brew install curl --with-openssl 

Step 3 - Create the following directory if it does not exists by running the following command: 

mkdir -p ~/.local/share/powershell/Modules 

Step 4 - Extract the PowerCLI modules into the directory you created above by running the following command: 

unzip PowerCLI.ViCore.zip -d ~/.local/share/powershell/Modules 

unzip PowerCLI.Cis.zip -d ~/.local/share/powershell/Modules 

unzip PowerCLI.Vds.zip -d ~/.local/share/powershell/Modules

Renew the IP of VMkernel port if assigned from DHCP.

While working with one of vSAN HomeLab, i have assigned VMkernel port to get IP from DHCP and I should have assigned it on different subnet but did on the same subnet as of vMotion.
So, without removing and re-creating the vmkernel port i have came across this esxcli command:



esxcli network ip interface set -e false -i vmkN ; esxcli network ip interface set -e true -i vmkN

esxcli network ip interface ipv4 get

no element found line 1 column 0 in vSphere Replication

While working with SRM, I came across the problem with vSphere Replication that

no element found line 1 column 0 

in its VAMI console i.e https:\\vSphereReplicationIP:5480.

Its there because one vSphere Replication Appliance can only be registered with one vCenter Server and once it is done , if somehow there is error in the communication between vCenter & vSphere Replication Server you"ll end up getting this error.

How I resolved this.

1. Removed the solution user present in users and group for the designated vSphere Replication Appliance.
Solution User will be like : com.vmware.vr-UUID of vcenter Server.

2. Try and reinstall the certificates of vSphere Replication from VAMI console.

3. Now it should work.