Backtrack:  
 
showing posts tagged with 'vmware'
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 files.ls -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:

https://packages.vmware.com/tools/esx/index.html

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:

https://packages.vmware.com/tools/esx/5.5u3/windows/index.html

by lunarg on August 21st 2015, at 10:23

If your vCenter server has a self-signed certificate, you will get a warning about this when connecting to it from vSphere PowerCLI. You can disable this warning through PowerCLI with the Set-PowerCLIConfiguration cmdlet.

  1. Start an elevated vSphere PowerCLI (right-click, Run as Administrator).
  2. Enter the following cmdlet:
    Set-PowerCLIConfiguration -InvalidCertificateAction Ignore
    Press Enter again to confirm the change.

After making the change, new connections to the vCenter server will no longer produce a warning about the certificate.

by lunarg on July 7th 2015, at 11:54
When you enable the ESXi Shell or SSH on a particular host in a vSphere cluster, a warning will appear on a ESX host:

ESXi Shell for the host has been enabled

or SSH for the host has been enabled

This is normal behaviour, but you can turn off these warnings for each of the hosts.

Note that prior to vSphere 4.1 Update 2, it is not possible to suppress the warnings.

Open vSphere Client.

Select the ESX host. From the Configuration tab (right pane), click Advanced Settings.

Navigate to UserVars → UserVars.SuppressShellWarning.Set its value to 1.

Click OK to confirm. The warning will disappear immediately.

Log on to vSphere Web Client.

Select vCenter from the Home menu. Select Host  ...
by lunarg on July 3rd 2015, at 15:39
The vSphere Web Client may display the following error:

Failed to verify the SSL certificate for one or more vCenter Server Systems: https://vCenter-Server-FQDN:443/sdk

or

Could not connect to one or more vCenter Server Systems:https://vCenterFQDN:443/sdk

Additionally, objects such as hosts or VMs are not displayed in the vSphere Web Client.

These errors usually occur with a re-installation or upgrade of vCenter Server, where the vCenter Server is registered to the same vSphere SSO more than once.

The faulty registration needs to be resolved by unregistered all duplicate vCenter Server instances from vSphere SSO, so only the correct registrations remain.

You will have to unregister al  ...
by lunarg on June 22nd 2015, at 10:29
The HP Network Config Utility provides advanced network configuration tasks for HP servers. It allows to set up NIC teaming, VLAN and more.

Uninstalling this software (e.g. after a P2V) is not possible through Control Panel (Add/Remove Programs) because it's not in the list like other HP software components. The only way to uninstall HP Network Config Utility is through an NIC's properties:

Open the network properties for any Ethernet NIC (doesn't matter which one).

In the This connection uses the following items: box (where you also set up IPv4/v6 settings), you'll see the HP Network Configuration Utilty.

Select (click) it, then click the Uninstall button. At the following prompt, click  ...
by lunarg on June 17th 2015, at 10:34
Linux distros with a 3.x kernel running on virtualized hardware (e.g. pvscsi on VMware) may ever so often spit out the following error:

$ dmesg | grep "WRITE SAME"
kernel: sda2: WRITE SAME failed. Manually zeroing.

This is because the disk driver (in our case: the VMware paravirtual driver) does not support the WRITE SAME SCSI command, resulting in this message.

While this poses no problem for the system at all, you may want to get rid of these messages, which is done by disabling the use of the WRITE SAME command. This can be done through a bit of configuration. Most modern systems have systemd on board which can be used for this, but in case your system doesn't, there's also a  ...
by lunarg on May 20th 2015, at 16:45
After configuring HA for a vSphere 5 cluster, you may encounter the following warning on each ESX host:

Configuration Issues
The number of vSphere HA heartbeat datastores for this host is 1, which is less than required: 2

vSphere 5 introduces datastore heartbeats in addition to network hearts, which allows to distinguish between a network-isolated host and a crashed host. In order for datastore heartbeats to work properly, vSphere requires at least 2 shared datastores available on every host in the cluster. If there's less than 2 shared datastores, datastore heartbeats will not function properly, resulting in the configuration issue message.

If you only have one shared datastore and wish   ...
by lunarg on May 6th 2015, at 09:20

You may have noticed that running the VMWare vSphere client on a display with higher DPI settings causes problems with the mouse cursor alignment when working inside a VM. This is because of a mismatch between the DPI settings of the VM and the DPI settings of your computer.

To resolve, right-click the shortcut to the client, go to the Compatibility tab, and enable Disable display scaling on high DPI settings.

The downside of this method is that there will be misalignment of some parts in the client, but it is still workable and moreover, it solves the mouse issue in a VM.

by lunarg on April 29th 2015, at 16:49
When attempting to add an ESX host to vCenter, you may get one of the following errors:

Error #1
Cannot install the vCenter agent service: Cannot upload agent.

Or:

Error #2
Cannot install the vCenter agent service: unknown installer error

Below is a list of most common errors:

Check whether the host is accessible through port 902/tcp. Check the firewall settings and/or routing between the ESX hosts and the vCenter server.

Check whether there is sufficient space on the ESX disk. If there's not enough space, this often gets logged in /var/log/syslog.log during the installation of a VIB.
Usually the problem occurs with the tmp partition (i.e. scratch disk) being full or almost full. You n  ...
by lunarg on April 29th 2015, at 16:39
Below is a list of most common CLI commands for VMWare ESXi. Type these in directly in an ESXi or SSH shell.

vim-cmd vmsvc/getallvmsList all VMs running on the host. Also provides vmid, required for commands below.vim-cmd vmsvc/power.off vmidPower off specified VM.vim-cmd vmsvc/power.on vmidPower off specified VM.vim-cmd vmsvc/power.reboot vmidReboot specified VM.vim-cmd solo/registervm /vmfs/volume/datastore/subdir/vm-file.vmxRegister the VM stored at location on the ESX host inventory.vim-cmd vmsvc/unregister vmidUnregister VM from the host. Does not remove the VM's files from the datastore.vim-cmd vmsvc/destroy vmidDelete the specified VM. The VMDK and VMX files will be deleted from stor  ...
by lunarg on April 29th 2015, at 14:00
Sometimes it may be required to do a full restart of agents and services on a VMWare ESX host. You could do a full reboot, but this requires all VMs to be shut down or moved to another host. Fortunately, it is also possible to do a complete restart of services on a host without affecting the VMs running on it.

There are two ways of doing this, depending on whether you have direct access to the host, through console or through a remote management system like HP's iLO or Dell's iDRAC, or have to do it remotely.

Note that using the Restart management agents function from the console is not the same as a full restart of all services.

Use this method if you have access to the host directly thr  ...
by lunarg on April 29th 2015, at 13:18
There are two ways to enable the SSH server on a VMWare ESX host, through the vSphere client or through direct access through the console.

Use this method if you have access to the host directly through console, or when you can use a remote management system such as HP's Integrated Lights-Out or Dell's iDRAC.

If you can't log on using the vSphere client, this is the only way to enable the SSH server.

Log on to the console using the root account.

In the menu, go to Troubleshooting, then enable the SSH server.

Log on to the ESX host through the vSphere client. You can also log on your vCenter server to enable the service.

Click on the host (in vCenter or when logged in directly on the ES  ...
by lunarg on April 29th 2015, at 10:00

When attempting to install or upgrade VMWare vServer server or its components, you may get the following prompt:

Please insert the Disk: 1

If you click OK, the message reappears. Clicking Cancel results in the installation to roll back.

Resolution

Copy the entire installation files to a location on the local hard drive and run the install/upgrade from there.

When running the installation from the local hard drive, and you get the error Provided password is wrong or empty, reboot and re-run the install from the local hard drive.

by lunarg on April 23rd 2015, at 11:05
When upgrading or reinstalling VMWare Site Recovery Manager (SRM), you may run into the following error:

Error message
Failed to Clear Inventory Service Registration

This error can occur when you attempt to upgrade/reinstall SRM, and have decided to clear out the SRM database, or when you have done a reinstall of vCenter, the inventory service, or have cleared out the Inventory Service database.

There are two ways around this.

Keep the old SRM database instead of overwriting it, but after the installation, you will manually have to clean up the existing database, since you wanted to clear out the old data in the first place.

Alternatively, and more easily done, is to remove the database  ...
by lunarg on April 22nd 2015, at 12:58
The Trend Micro OfficeScan AEGIS engine may cause a desktop not to load during logon, resulting in a black screen with only the mouse cursor visible. The process explorer.exe is not loaded, nor can it be loaded through Task Manager.

The problem usually occurs on provisioned desktops, either through VDI (VMWare View) or some other 3rd party management solution (Dell Kace, etc). Various components of these solutions hook into key Windows components (Winlogon, Explorer extensions, etc), and are then being blocked by the Trend Micro Behavioral Analysis service (the AEGIS-engine).

A workaround is to either whitelist all the components, but this is often not a straight-forward solution. Another   ...
by lunarg on April 21st 2015, at 08:16

When attempting to install VMWare Tools on a Windows 2000 VM, you may get the following error:

Error message
Microsoft Runtime DLLs cannot be installed on this Operating System. Please see Microsoft KB835732

To resolve, you need to install Security Update for Windows 2000 (KB835732) (requires SP4 as well).

showing posts tagged with 'vmware'
 
 
« January 2018»
SunMonTueWedThuFriSat
 123456
78910111213
14151617181920
21222324252627
28293031   
 
Links
 
Quote
« I needed a password with eight characters so I picked Snow White and the Seven Dwarves. »