Issue

"Unsupported SVGA driver" during Windows 10 upgrade in VMware Workstation

windows-10-upgradeUpgrading Windows 7, 8 or 8.1 to Windows 10 in VMware Workstation fails with the following error message:

Unsupported SVGA driver

The issue only applies to the Microsoft Update Validation Tool which has problems with the VMware SVGA driver. To resolve this issue, use the Windows 10 ISO to upgrade your Virtual Machine.

Read More »"Unsupported SVGA driver" during Windows 10 upgrade in VMware Workstation

How to fix ESXi on Intel NUC malformed Manufacturer and Model

VMware ESXi 5.x and 6.0 installed on a 5th gen Intel NUC (NUC5i7RYH, NUC5i5RYH, NUC5i5MYHE, NUC5i5RYK, NUC5i3RYH, NUC5i3MYHE and NUC5i3RYK) has a problem with SMBios system information.

  • Manufacturer and Model in the vSphere Client is displayed with replacement characters (� black diamond with a white question mark).
    5th-gen-nuc-manufacturer
  • Adding host to a vCenter Server fails with the following error message

    A general system error occurred: at line number 7, not well-formed (invalid token)

To solve this problem you have to replace the BIOS. This post explains how to create a customized BIOS with changed SMBios variables and install it on your NUC.

Read More »How to fix ESXi on Intel NUC malformed Manufacturer and Model

VMware ESXi 5.x E1000 PSOD Issue

Even though the bug has been fixed I still see it to come up. ESXi 5.x has two issues that might cause the ESXi host to fail with a purple diagnostic screen. Both PSOD look very similiar:

KB2059053:

#PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnn addr 0x0
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]E1000PollRxRing@vmkernel#nover+ 0xdb9
0xnnnnnnnn:[0xnnnnnnnn]E1000DevRx@vmkernel#nover+0x18a

KB2079094:

#PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnn addr 0x0
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]E1000PollRxRing@vmkernel#nover+0xeb7
0xnnnnnnnn:[0xnnnnnnnn]E1000DevRx@vmkernel#nover+0x18a
[...]
0xnnnnnnnn:[0xnnnnnnnn]Net_AcceptRxList@vmkernel#nover+0x157

Read More »VMware ESXi 5.x E1000 PSOD Issue

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 »ESXi Issues caused by hp-ams module

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 »Identify Virtual Machine Locks & Find ESXi Hosts by its MAC Address

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 »Reuse VSAN Claimed Disks as VMFS Datastore

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 »ESXi 5.5 affected by OpenSSL CVE-2014-0160 aka Heartbleed

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 »Permanently disable ESXi 5.5 coredump file

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 »Cannot remove datastore * because file system is busy.