ESXi5.5u2 install fail on new x240 m5 – failed to resolve circular relocation

The other day I ran into a strange issue. Just received a bunch of Flex Blade x240 for a Vmware cluster and trying to get ESXi installed I was stopped by the following message: Failed to Resolve circular relocation.

vmware esxi failure - failed to resolve circular relocation

failed to resolve circular relocation

It happened on one server so I tried the next one and the next, same thing!

I opened a case with Vmware which resulted in the following KB:2050443

It seems like ESXi doesn’t support MMIO regions above 4GB.

It took me for ever to find the relevant IBM/Lenovo information. Eventually found it at not thanks to Lenovo support!

So I made the following changes in my BIOS, from 64-Bit resource allocation: Enabled to Disabled. And MM Config Base from 2GB to 3GB.

You will find the above settings under the BIOS>System Settings> Devices and IO ports

vmware esxi failure - lenovo good config

I hope this helps.


#esx, #flex, #ibm, #lenovo, #server, #vmware

No They Did Not – IT Rant

IT Manager says 32 yet 64 GB of RAM for a VMware host is more than enough.

Yet this company have 12 hosts with an average of 10 VM per host where memory is the contention point.

Would would J. do?

#consolidation, #it-rant, #memory, #vmware

SQL execution took too long on vCenter – SQL execution took too long: INSERT INTO VPX_EVENT_ARG WITH (ROWLOCK)

One day I woke with several warning alerts from foglight saying it got disconnected from a vCenter and reconnected almost right away but then flipping on and off all the time making foglight a bit spammy.

Looking at my vServer logs, I found out a repetitive peculiar message about queries taking too long while looking around the DB is undersized, and DB processes being responsive.

A few KB searches after, I read up that dbo.VPX_EVENT and dbo.VPX_EVENT_ARG tables are too large and must be truncated. (KB 2020507)

As per KB…

  1. Take a back-up of your current database. Do not skip this step.
  2. Use SQL Management Studio to connect to the vCenter Server database.
  3. Select New Query.
  4. Enter these queries in the new window and click Execute:

    Note: Execute each query separately and wait for the query to complete prior to running subsequent queries. Depending on the size of the tables, the process may take up to 15 minutes.

    • EXEC sp_msforeachtable “ALTER TABLE ? NOCHECK CONSTRAINT all”
    • USE name_of_the_vcdb
      TRUNCATE TABLE vpx_event_arg;
      DELETE FROM vpx_event;
    • Exec sp_msforeachtable @command1=”print ‘?'”, @command2=”ALTER TABLE ? WITH CHECK CHECK CONSTRAINT all”

Then all went back to normal after a restart of all services involved eventhough the KB title did not seem very related to my case.

#execution, #sql, #vcenter, #vmware

vCenter Server Appliance vs vCenter Server 5.5

I was reading some articles as I was getting ready to reinstall the whole vCenter Server after a major crap-out at a client.

I am talking about this kb from VMware and it seemed that VSA had improved so much it could actually be used at this SMB.

  • But I found out the following VMware vCenter Server Appliance 5.5 limitations.
  • vCenter Linked Mode is not supported
  • vCenter Heartbeat is not supported
  • Some VMware/Third Party Plugins might not support vCSA. Check with your desired plugin vendors if they support the vCenter Appliance.
  • Installing update Manager on the vCenter Appliance is not supported, but you can still set it up on a separate Windows VM.
  • If using the embedded database you will be limited to 100 hosts and 3000 VMs, but you always can utilize an Oracle Database to be able to scale to the vCenter Maximums of 1000 hosts and 10,000 VMs.
  • MS SQL Database is currently not supported by the vCenter Server Appliance, where you can either use the built-in vPostgres (Support up to 100 hosts and 3000VMs) or you will need to use Oracle Database to scale to 1000 hosts and 10,000 VMs. If you are planning to go beyond 100 hosts and 3000VMs and Oracle database is not an option or your cup of tea then you will have to stick with the Windows version of vCenter for now.
  • It does not support the Security Support Provider Interface (SSPI),  which is a part of SSO, and  is a Microsoft Windows API used to perform authentication against NTLM or Kerberos.
  • VMware View Composer can not be installed on the vCenter appliance, but it is no longer required to install it on the same machine as vCenter and it can be installed on a different machine and then it will support vCSA.

So I guess that’s not quite there. I’ll get some windows licenses on the way 🙂

#appliance, #vcenter, #vmware, #vsa