showing posts tagged with 'vmware'
by lunarg on October 9th 2017, at 14:42
To create an UEFI-bootable USB installer for ESXi 6.5 (or newer) on a Mac, follow the steps below.

First, you'll need an USB flash drive. Any recent drive will be large enough (you'll need at least 512MB). Also, download the latest ESXi installer ISO from My VMWare. You probably need a My VMWare account.

With the prereqs in place:

Insert the USB flash drive in the Mac and start up Disk Utility.

Erase the USB flash drive and choose to format it:Partition map = MBR

Filesystem = FAT32

Give it a descriptive name of your choosing.

After erasing the drive, we still have to mark the one partition on it as "active". Disk Utility does not support this and needs to be done using Termi  ...
by lunarg on September 28th 2017, at 14:36

If for any reason you need to determine whether a specific instance of VMWare View Connection Server is installed as a standalone server or a replica server, you can do so by looking into the registry.

In HKEY_LOCAL_MACHINE\Software\VMware, Inc.\VMware VDM, the value ServerInstanceType will indicate which type the CS is:

1 = standalone/first CS
2 = replica CS

Note that this doesn't really matter, as the only difference between them is whether they set up a new ADAM instance or connect to an existing one. After the installation of VCS, they are identical.

by lunarg on August 23rd 2017, at 14:11

Hyper-V does not allow to be installed on a machine that's already virtual (such as on another Hyper-V or VMWare). For VMWare, you can circumvent this by adding custom configuration parameters to the VM's configuration.

Add these to the VM's configuration, either through the vSphere (web)client, or by directly editing the VMX-file:

hvh.enable = TRUE
hypervisor.cpuid.v0 = FALSE 

If you're editing the VMX-file, you need to enclose the values (behind the =) in double quotes (").

by lunarg on August 22nd 2017, at 13:49
After successfully extending a partition on a VM, Disk Management shows the correct partition size but Explorer still shows the old size, even after a reboot.

The reason for this is that while the partition has been extended to the new size, the filesystem itself has not. Normally, Disk Management should first extend the partition, then the filesystem, but for some reason, the second part did not happen.

To resolve, perform an extension of the volume using diskpart.

Open an elevated command prompt and start diskpart (type diskpart and press Enter).

List all volumes to find out which volume number corresponds with the drive you need to resize: DISKPART> list volume

Select the volume  ...
by lunarg on July 24th 2017, at 17:19
In order to succesfully convert Windows systems to a VMware virtual machine, you need to install the sysprep files of the to be converted host. Below is a list of downloads to these sysprep files:

The base folder of where to put the files is always:

%ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone\sysprep

Extract contents to: base-folder\2k

Available in SP4 or the CD-ROM of Windows 2000 SP4 at Support\Tools\

Extract contents to: base-folder\svr2003


Extract contents to: base-folder\svr2003-64


Extract cont  ...
by lunarg on June 26th 2017, at 09:53
A list with direct links to VMware vSphere clients. Saves you a lot of time when you need to (re)install many different versions.

Starting with 6.5, the vSphere client is no longer available.

VMware vSphere Client 6.0 Update 3: VMware-viclient-all-6.0.0-5112508.exe

VMware vSphere Client 6.0 Update 2a: VMware-viclient-all-6.0.0-4437566.exe

VMware vSphere Client 6.0 Update 2: VMware-viclient-all-6.0.0-3562874.exe

VMware vSphere Client 6.0 Update 1: VMware-viclient-all-6.0.0-3016447.exe

VMware vSphere Client 6.0: VMware-viclient-all-6.0.0-2502222.exe

VMware vSphere Client 5.5 Update 3d: VMware-viclient-all-5.5.0-3705931.exe

VMware vSphere Client 5.5 Update 3: VMware-viclient-all-5.5.0-3  ...
by lunarg on June 9th 2017, at 13:31
In VMWare Workstation and vSphere ESX, it is possible to set disks to be independent so they are not linked to snapshots. Independent disks can then be set to be Persistent (changes are written immediately and permanently to disk) or Non-persistent (changes are lost when the VM powers down). In VMWare Fusion, although this option does not seem to be present, it is still available, and can be configured by manually changing the parameters in the VM configuration file (.vmx).

A VM configuration file is a text-based file containing all the parameters and properties for a VM. This file can include options that are not present in the Fusion UI. By adding parameters manually, you can enable featu  ...
by lunarg on May 8th 2017, at 14:32
A very common practice when setting up SAN storage on a VMWare cluster is to configure the storage path policy to be set to "Round Robin" to properly benefit from MPIO in addition to standard failover. However, if the cluster consists of many nodes or there are many volumes, this can take up quite a lot of time if you configure this using the (Web)GUI. A better way to adjust the setting for the entire cluster is through PowerCLI.

The one-liner:

Get-VMHost <Cluster-or-Host> | Get-ScsiLun -LunType "disk" | Where {$_.MultipathPolicy -ne "RoundRobin"} | Set-ScsiLun -MultipathPolicy RoundRobin

The cmdlet selects a cluster or host, gets all LUNs which are of   ...
by lunarg on April 11th 2017, at 14:03

I wrote a script to list virtual disk information for a specified VM, including VMDK path, SCSI IDs and more. It is loosely based on this script but excludes all WMI info.

Download here.

by lunarg on February 16th 2017, at 10:08

It is possible to install the integration plugins for VMware on an ESX host directly from the Nimble website, provided your hosts have internet access:

  1. Place the host into maintenance mode.
  2. Connect to the host through a shell (e.g. SSH).
  3. Run the command:
    esxcli software vib install -d
    Wait for the installation to complete.
  4. Take the host out of maintenance mode and continue with the configuration.
by lunarg on January 19th 2017, at 16:49

With PowerCLI, you can generate all sorts of lists. To retrieve the configured and reported OS version of your VMs, try running this one-liner:

Get-VM | Sort | 
   Get-View -Property @("Name", "Config.GuestFullName", "Guest.GuestFullName", "Guest.IpAddress") | 
   Select -Property Name, 
       @{N="Configured OS";E={$_.Config.GuestFullName}},
       @{N="Running OS";E={$_.Guest.GuestFullName}},
       @{N="IP Address";E={@($_.Guest.IpAddress)}} | 
   Export-CSV -Delimiter ";" -Path "vms.csv"
by lunarg on January 10th 2017, at 14:42
If your ESX host has lost connection to the vCenter server, but you can still directly access the host's management, and can find nothing else wrong with the vCenter server or its network connection to the host, you may want to the free space on your ESX host.

Logs and other temporary files may have filled up one or more ramdisk partitions (e.g. when you don't have a persistent scratch partition, it gets mounted on /tmp). This can cause any of the following issues:

Connection loss between the ESX host and vCenter server;

Errors when attempting to reconnect or add an ESX host to a vCenter server;

Errors while attempting to activate or configure HA;

Other unexplainable errors...

You can   ...
by lunarg on January 10th 2017, at 14:38
If the scratch partition (/tmp) gets filled up, check for the presence of the file ql_ima.log. If it is present, you are bothered by a bug from an older version of the qla4xxx driver. Even if you use Update Manager, this driver does not get updated automatically. The solution is add the driver to Update Manager or download and install the update manually.

This procedure describes the manual installation of the update on your ESX host. There's no need to put the host in maintenance mode but you will have to reboot to use the new driver.

Download the driver (you need a VMware account):

VMware 5.5

VMware 6.0

Unpack the download and copy the file qla4xxx-634.55.28.0-offline_bundle-1682448.z  ...
by lunarg on December 9th 2016, at 10:53
When deploying a vShield Manager VA, its IP address is set to DHCP by default. Once deployed and started, you can log on through the console to change it to a fixed IP.

Open a VMWare console to the appliance and log on:

manager login: adminPassword: ****** (the CLI 'admin' password you entered during the deployment)

Go into enable mode and enter the setup:

manager> enablePassword: ****** (the enable password you entered during the deployment)manager# setup

Enter the IP address, subnet mask, gateway and DNS settings. When finished, you will be prompted to log out.

Note that after setting the IP address, I had to restart the appliance because the web interface was only accessible on t  ...
by lunarg on August 19th 2016, at 16:17

Found this interesting read on VMFS Extents and some of the (negative) myths that have arisen over the years:

by lunarg on December 5th 2015, at 13:19

You can quickly get a list of VMs, the datastores they are using and the logical folder they are in through PowerCLI:

Get-VM | Select Name,@{N="Datastore";E={[string]::Join(',',(Get-Datastore -Id $_.DatastoreIdList | Select -ExpandProperty Name))}},@{N="Folder";E={$_.Folder.Name}}

Combine it with Export-CSV to export the results to a CSV file.

by lunarg on November 16th 2015, at 11:24
VMWare ESX 5.5 introduces the ability to perform coredumps to a file instead of a partition.

To configure this, you need access to the ESX host's CLI (either through vSphere Management Assistant (vMA), directly on the host through console or SSH, or some other method). For this to work, you need "root" access (or the equivalent of it through vMA).

Once logged on, take a directory listing of the VMFS datastores to determine on which datastore you want to place the coredump -l /vmfs/volumes

You will see a list of datastore UUIDs as well as symlinks to those UUIDs. Use the symlinked names to figure out which UUID points to which datastore's logical name:For example:
DataSt  ...
by lunarg on October 26th 2015, at 14:00
When attempting to unmount or delete a VMFS datastore on a cluster, you may get the message that the resource is still in use, even though all the VMs have been moved off the datastore, or that Storage I/O Control (SIOC) is enabled on it (usually when attempting to unmount).

To circumvent the issue, temporarily stop SIOC, unmount/delete the datastore, then start SIOC again. If an unplanned Permanent Device Loss (PDL) is invoked when Storage IO control enabled on a storage device (iSCSI device or FC), the ESX host cannot remount the VMFS datastore, and also the steps below are then also required in order to be able to remount the datastore.

On each of the ESX hosts (if there's more than one  ...
by lunarg on October 6th 2015, at 13:44

You can download installation files and ISOs of any of the latest versions of VMWare Tools for each released version of ESX:

This is useful if you need support for a certain OS version but are not able to upgrade the ESX host in order to get it (e.g. Windows 10 support on ESX 5.5 "non-u3").

Note that, although officially unsupported, VMWare Tools is technically backwards compatible, meaning you can install a newer version on a guest running on an older ESX host.

by lunarg on October 6th 2015, at 13:37

Windows 10 is not out of the box supported on ESX 5.5, unless you're running 5.5u3. One of the issues is that earlier versions do not have a compatible video driver for Windows 10.

However, for older versions of ESX 5.5, you can manually download the VMWare Tools and install them:

showing posts tagged with 'vmware'