I have had an annoying issues at two customer sites now, and I want to share the solution with you.
The problem is that you cannot VMotion VMs to a newly installed ESXi 6.5 hosts running on Lenovo SR650 hardware. The CPU used in the new host is Intel Xeon Gold 6154 Processor, and the old hosts are using Intel Xeon Processor E7-4880 v2. I do not think that the source CPU model is relevant to the issue it could be any supported Intel CPU in the same cpu family.
When trying to VMotion the following error is displayed:
The virtual machine requires hardware features that are unsupported or disabled on the target host:
"""""""""""""* General incompatibilities
If possible, use a cluster with Enhanced vMotion Compatibility (EVC) enabled; see KB article 1003212.
CPUID details: incompatibility at level 0x1 register 'ecx'.
Host bits: 0110:0010:1101:1000:0011:0010:0000:0011
If you then try to enable EVC in the cluster it complains that the new hosts has an issue, and returns this error:
The host's CPU hardware should support the cluster's current Enhanced vMotion Compatibility mode, but some of the necessary CPU features are missing from the host. Check the host's BIOS configuration to ensure that no necessary features are disabled (such as XD, VT, AES, or PCLMULQDQ for Intel, or NX for AMD). For more information, see KB article 1003212.
Continue reading Unable to VMotion to new Lenovo SR650 Host
just updated a vRealize Operations Manager server today from 6.0.2 to 6.6.1, and unfortunately I got an error during the fourth step of nine (4/9):
Failed The PAK action "apply_system_update" script "/usr/lib/vmware-vcopssuite/python/bin/python updateCoordinator.pu -p " failed
As I was in the middle of a vCenter upgrade and some other stuff, that was a little annoying, and I could not really find any articles on the particular problem, so I did some digging around in the appliance, and it turns out that it is not pleased with the certificate on the appliance.
Continue reading vRealize Operations Manager 6.6.1 Upgrade failed
After upgrading VCSA from version 6.5 to 6.5 Update 1 you might experience a problem with Task Names and object Descriptions. Names are not “resolved” to its human understandable name, but instead they are written as a API object name.
For instance a host profile compliance check would normally be “Compliance check” but is instead written as “profile.ComplianceManager.check.label” or a VMotion is written as “Drm.ExecuteVMotionLRO.label”
Continue reading vCenter Recent Tasks Descriptions and Names are broken after VCSA Upgrade
Sometimes I find it easier to create a new vCenter server then migrate the old one, and it is a perfectly good solution in many cases.
But annoyingly there is a lot of manual work involved.
One problem is the VM’s and Templates folders. They do not follow the host, so you have to create the folder structure manually and move each VM into the correct folder. Well I am way to lazy to do that by hand, so it’s time to Automate! Continue reading Migrate folder structure from old to new vSphere vCenter
Today I upgraded some HP BL460c Gen9 Blade Servers from ESXi 6.0 to ESXi 6.5. I always reinstall when going from 5.5 to 6.0 or 6.0 to 6.5, so After the server was done installing I found that the FCoE adapters and datastores was missing.
The servers are connected to some HP 3PAR storage using HP FlexFabric 10Gb 2-port 536FLB Adapters.
To regain access to your storage you need to enable the FCoE adapters using the esxcli command.
Continue reading FCoE Adapters and datastores missing after vSphere ESXi 6.5 Install
During an upgrade I got the following error: “A problem occurred while getting data from the source vCenter Server”
And the install log has the following information. Continue reading VMware vCenter VCSA 6.5 Upgrade “Error: queryAaaa ENODATA”
I have had an annoying issue in the vSphere 6.5 Web Client, where Auto Deploy would not show up in the left side menu.
Continue reading VMware Auto Deploy not showing in vSphere Web Client
Are you looking to Upgrade Mirage and move it to a new server, or are you just looking to move Horizon Mirage to a new server, this article will describe what you need to do.
Continue reading Upgrade VMware Horizon Mirage to new server
I just upgraded the vCenter in my test lab, and I got an error after the first part of the process. When it was about to migrate data from the old VCSA 6.0 Server.
I restarted to process but this time is was unable to get information from my source VCSA server. In the log I had the following errors:
2016-11-16T16:42:03.649Z - info: VM Identifier for Source VC: vm-108
2016-11-16T16:42:03.784Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: A general system error occurred: vix error codes = (1, 4294967294).
2016-11-16T16:42:03.785Z - debug: Failed to get fileTransferInfo:ServerFaultCode: A general system error occurred: vix error codes = (1, 4294967294).
2016-11-16T16:42:03.785Z - debug: Failed to get url of file in guest vm:ServerFaultCode: A general system error occurred: vix error codes = (1, 4294967294).
2016-11-16T16:42:03.785Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: A general system error occurred: vix error codes = (1, 4294967294).
2016-11-16T16:42:03.785Z - error: Failed to read the nodetype, Error: A general system error occurred: vix error codes = (1, 4294967294).
2016-11-16T16:42:03.786Z - error: sourcePrecheck: error in getting source Info: ServerFaultCode: A general system error occurred: vix error codes = (1, 4294967294).
I quickly discovered the reason. My root password was expired and it wanted me to create a new password for root.
Continue reading vCenter 6.5 Upgrade fails with error: vix error codes = (1, 4294967294)