Tag Archives: Issue - Page 2

vMotion Fails - "The source detected that the destination failed to resume"

Virtual Machine Migration (DRS or user initiated) fails with the following error message:

migration-error

A genereal system error occurred: The source detected that the destination failed to resume

Error Stack:
The VM failed to resume on the destination during early power on.
Module DiskEarly power on failed.
Cannot open the disk '/vmfs/volumes/<...>.vmdk' or one of the snapshot disks it depends on.
Could not open/create change tracking file

  1. Check that Virtual Disks are not mounted to the backup host (VDP or other products). Sometimes when the backup fails, the virtual disks are not correctly removed from the backup host.
  2. Consolidate Snapshots (Right Click Virtual Machine > Snapshot > Consolidate)
  3. If the problem still persists, create a snapshot and delete it with the "Delete All" option.

ESXi Issues caused by hp-ams module

I recently had strange issues with Hewlett-Packard servers. ESXi hosts randomly have shown a couple of different symptoms:

  • ESXi host unmanageable
  • ESXi host grayed out in vCenter
  • Starting host services fails with an error message:

    Call "HostServiceSystem.Restart" for object "serviceSystem-[*]" on vCenter Server * failed.

  • Cannot perform vMotion to or from the host
  • Starting virtual machine fails with an error message:

    Power On virtual machine *
    A general system error occurred: The virtual machine could not start
    VMK_NO_MEMORY

  • Restarting services in DCUI fails

    A general system error occurred: Command /bin/sh failed

  • SSH connection to the host possible, but no response after login requests
  • Local console displays an error message:

    /bin/sh cannot fork

  • Error Message received at syslog server

    sfcb-HTTPS-Daemon[*]: handleHttpRequest fork failed: Cannot allocate memory
    crond[*]: can't vfork
    cpu*:*)WARNING: Heap: *: Heap_Align(globalCartel-1, 136/136 bytes, 8 align) failed.
    cpu*:*)WARNING: Heap: *: Heap globalCartel-1 already at its maximum size. Cannot expand)

  • DCUI message log (ALT+F12) displays an error message

    WARNING: Heap: *: Heap globalCartel-1 already at its maximum size. Cannot expand.

Read more »

Identify Virtual Machine Locks & Find ESXi Hosts by its MAC Address

I recently had an issues where a virtual machine crashed. VM Monitoring (VM HA) tried to restart it, but did not succeed. The virtual machine was greyed out in the inventory and could not be started because it was locked. Unfortunately, it was not possible to identify which ESXi host holds the lock. This post explains how to quickly identify which server is blocking the Virtual Machine.

Read more »

Reuse VSAN Claimed Disks as VMFS Datastore

During a test I used an old disk that has been previously used by Virtual SAN. The disk did not appear during the datastore creation process. I miss a flash drive here:

datastore-creationThe problem is that the disk has not been cleared from it's VSAN configuration. It has still valid VSAN partitions, so the ESXi "claims it for VSAN" what makes it impossible to create a VMFS filesystem.

Read more »

ESXi 5.5 affected by OpenSSL CVE-2014-0160 aka Heartbleed

[Last Update April 19, 2014 - Patches available]

There are a lot of news according to the recently published OpenSSL vulnerability. The bug, also known as "Heartbleed", allows attackers to steal informations that are protected by the SSL/TLS encryption.

Is VMware ESXi and the vCenter affected?
There is currently no official statement from VMware regarding this issue. After some research I found affected versions im VMware products. Here are my findings:

The affected versions are OpenSSL 1.0.1 through 1.0.1f.

Read more »

Permanently disable ESXi 5.5 coredump file

The new coredump file feature in vSphere ESXi 5.5 creates a file to extend the coredump partition. This usually happens when you upgrade from a previous version to ESXi 5.5, or you install ESXi to a USB drive or SD card. This coredump file is created on a random VMFS datastoore by using a smart selection algorithm. This random placement causes different kind of problems, for example when you want to delete a datastore. Another problem might occur in an EMC VPLEX deployment where you want to failover VMs to the secondary site in a PDL situation (VMkernel.Boot.terminateVMOnPDL=1 / Disk.AutoremoveOnPDL=0). Datastores that had a coredump file configured can't get mounted back when the volume leaves the PDL state after a site failure has been fixed.

To workaround this issue you might want to permanently disable the coredump file. You can't just disable it, as it gets created automatically after a reboot.

Read more »

Cannot remove datastore * because file system is busy.

The following error message appears when you try to delete or unmount a VMFS datastore:

The resource Datastore Name: * VMFS uuid: * is in use.

Cannot remove datastore 'Datastore Name: * VMFS uuid: *' because file system is busy. Correct the problem and retry the operation.

Cannot-remove-datastore- because-file-system-is-busy

ESXi 5.5 has a new feature to store coredumps in a file residing on a datastore. It may sometimes create this file automatically and thus blocking datastores from being deleted. It also creates a vsantraces directory which blocks a datastore.

Read more »

VM grayed out as disconnected, inaccessible, orphaned or invalid

Short post on different connectivity states of a virtual machine and how to fix them.

inaccessible-vm

Read more »

Solve VSAN "Network status: Misconfiguration detected" Problems

One problem that comes up quite often during VMware Virtual SAN Beta testing is that the Network status keeps in the "Misconfiguration detected" state. Sometimes the cluster also shows up with different "Network Partition Groups". This message can be caused by several problems. In this post i am going through the most commonly pitfalls and how to solve them.vsan-Network-status-Misconfiguration-detected

Read more »

Failed to connect to VMware Lookup Service during Web Client Login

At least since vSphere 5.1, a clean DNS and SSL setup prevents from several errors. I've often seen the vCenter Server Appliance failing with the following error message after trying to log in to the vSphere Web Client:

Failed to connect to VMware Lookup Service https://[VCENTER]:7444/lookupservice/sdk - SSL certificate verification failed.

failed-to-connect-to-vmware-lookup-service

Read more »