VirtualVCP IT Virtualization

Although there are “many” “new” features in vSphere 4.1, there are many changes that have been made “under the hood”. I noticed this whilst I was playing with the beta. One of these changes is the way the vpxa agent enforces admission control in ESX/ESXi.

When an ESX/ESXi host has been added to vCenter and the vpxa agent has been installed on the host, the vpxa agent will not allow any virtual machines state changes to be made directly from the host itself. You will still be able to use the vSphere client to connect directly to the ESX/ESXi host, but you will not be permitted to power on VMs directly on the ESX host. You will also be denied access to power on VM’s using the CLI. Only through vCenter will you now be able to power on a VM. What makes this awkward is this: The error message that is returned when the vpxa agent denies power on operations does not state the reason why your VM has failed to power on.

I got caught out by this after my vCenter Server (that was running as a VM) was powered down. I then connected directly to the ESX host where the vCenter VM was registered, but I was unable to power on the vCenter VM as vpxa was denying the power on operation. The way to get around this is to stop the vmware-vpxa daemon on the host “service vmware-vpxa stop). Only then will you be able to power on VMs directly.

I also have to state that I have not tried the GA build of vSphere 4.1, so the only experience I have with vSphere 4.1 is the beta. It would be interesting to see if it's still the same. Feel free to test it out and leave comments.

• Add New
• Search
• RSS

Comments (2)

• 2010-09-16 15:09:49 |Comment came from:155.192.0.xxx| Mike Wilcox  - ESX Host "ransom" might be fixed in GA

  Just thought I would update you with my recent experience. I have recently installed vCenter 4.1.0 (Build 258902) in the following configuration:
  1.) vCenter Server is x64-bit OS, using external SQL 2008 Databases (VCenter, Update Manager), and is a VM.
  2.) ALL ESX Hosts are version 3.5.0 (259926).
  3.) The VM for vCenter is hosted on one of the ESX 3.5x Clusters.
  Using the above configuration, I am able to use the vSphere Client to connect directly to the ESX Host holding the vCenter VM - and I can power-off, as well as modify (edit) the configuration of the vCenter VM.
  Perhaps the problem you documented has been fixed in the GA code? (Of course, this could be different if I was using ESX 4.x Hosts!)

  • 0
  • 0

  ReplyQuote

• 2010-09-16 14:11:21 |Comment came from:155.192.0.xxx| Rynardt Spies  - ESX Host "ransom" might be fixed in GA

  Yes, I have tested this in my lab and it seems to be behaving normally now.

  • 0
  • 0

  ReplyQuote

Write comment

Your Contact Details:

Name:

Email: do not notifynotify

Website:

Comment:

Title:

UBBCode:         -color-aquablackbluefuchsiagraygreenlimemaroonnavyolivepurpleredsilvertealwhiteyellow -size-tinysmallmediumlargehuge

Message:

Joomla components by Compojoom