‘Preparing to configure Windows – Do not turn off your computer’ – On a virtual infrastructure vCentre server


After installing the latest Windows updates and restarting the server you get the message ‘Preparing to configure Windows – Do not turn off your computer’ which seems like it has hung.

Initially I was unable to connect to the server at all via vSphere client or RDP. After a mild panic I connected to each vSphere node with the vSphere client until I found the server that was hosting the vCentre server. I was then able to access the console.

Panic over I decided to restart the server which kick started whatever update had crashed the server and I was able to then log in.

 

VMware virtual machine screen resolution only has a maximum resolution of 1176 x 885. Is it possible to increase?


After looking at the display adapter (VMware SVGA II) in the host XP VM I could not manage to have the display as full screen.
I assumed that I may need to edit the local VM’s .vmx file and specify 1280 x 1024 but it was actually easier to resolve.
– Power down the VM
– Select Edit Settings in the vSphere client
– Select Video Card
– In the right hand pane ‘Specify custom settings’ should be selected
– Click on the Video Memory Calculator button
– Under resolution select 1600 x 1200 (I initially chose 1280 x 1024 but in XP this still only gave me a maximum of 1280 x 960) and click OK
Inline images 1
– Restart your VM and then manually set the resolution
Inline images 3

You receive the error message “Unable to determine Guest Operating System” when trying to move a VM using VMware Converter


Had an issue moving a Windows 2008 x64 R2 Server and constantly recived the error unable to determine guest operating system. 

Found this excellent solution here http://wiert.me/2010/06/10/vmware-converter-4-01-unable-to-obtain-hardware-information-or-unable-to-determine-guest-operating-system/

Was able to change the guest operating system to just Windows 2008 and was then able to convert. Then I was able to change the guest OS back to R2 x64 after the conversion.

Virtualised Solaris 10 server has poor network performance when using the e1000 ethernet network driver


I experienced this problem when we were moving a lot of data from the Solaris server to a server in a different virtual infrastructure. The following web page explained the problem well and was able to use the same solution successfully:

http://mydigitalbrain.blogspot.com/2009/12/solaris-10-and-vmware-vmxnet-ethernet.html

We added the vmxnet driver as advised and made active whilst making the e1000 inactive. This worked as described but we also removed the e1000 interface as a test but this resulted in the networking failing altogether so it is important to keep the e1000 as the driver must be a necessary for networking to work.

How to install VMware tools on a Linux guest


I initially used the VMware guide http://www.vmware.com/support/ws5/doc/ws_newguest_tools_linux.html

From installing a few times on a variety of Linux flavours this is my interpretation.

In the Virtual Infrastructure right click on the Virtual Machine and select Guest and Install/Upgrade VMware Tools

image001

Click OK on the warning message

image002

The VMware tools are loaded as a CD/DVD drive in the guest Linux virtual machine. Ensure that you are logged in with root privileges, right click on the tar file and select Extract to

image003

Select an extraction location from the Extract in folder field. In this case I have chosen /tmp

image004

Once extraction is complete open a Terminal window and type cd /tmp

image005

The vmware-tools-distrib directory should exist inside the /tmp directory. Type

cd vmware-tools-distrib

image006

Next type

./vmware-install.pl

Answer the various configuration questions pressing Enter if you are happy to accept the default values

image007

Also take care choosing display resolution as certain applications require a minimum for installation

In this case I chose 1024 x 768

image008

Once completed you will need to restart X session to pick up the resolution

image009

A quick and easy way to restart is to use Ctrl-Alt and Backspace which will log you out of your desktop session

Error – Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again


I received this message when I tired to carry out a P2V conversion using the VMware stand alone converter on a Windows 7 client.

Solution that worked was to use the IP address of the destination rather than the UNC name.

Error adding a datastore in VMware ESXi 4.1 – Call “HostDatastoreSystem.QueryVmfsDatastoreCreateOptions” for object “ha-datastoresystem” on ESXi failed


image001

This occurred when I was trying to add a HP MSA1500 SAN which consisted of just 1 LUN as a datastore. I managed to get through the screens but no further than the formatting section.

To resolve this someone on the VMware forums mentioned about deleting the array containing the logical drive on the SAN and recreating a new but different RAID array before deleting again and recreating Array and Logical drive to meet your original requirements.

Steps were:

1. Attached a Windows server to the SAN via FC HBA

2. Opened the HP Array Configuration Utility and deleted the Array containing the RAID 6 logical drive

3. Created a new array with a RAID 0 logical drive

4. Deleted the array

5. Created a new array with a RAID 6 ADG logical drive

6. Went back into the vSphere client, rescanned the HBA and was able to add the logical drive without error

Is it possible to rename a VMware vSphere or ESX datastore whilst it is live?


You can easily rename a Datastore via the vSphere client without any impact on running VM’s in that datastore.

The name that you see is a friendly name that Vcenter uses for the datastore. The actual UUID of the datastore is not being changed therefore there is no impact on the vSphere host, datastore or VM’s.

If you feel unsure then by all means migrate the VM’s from the datastore before you make the name change.

How to re-register a Virtual Machine if it has been removed from the Inventory in VMWare vCenter


When you have removed a VM from the vCenter Inventory, often to reinitialise the VM there is no clear way in the vCenter Infrastructure client to add it back in through the toolbar menus.

The easiest way to add a VM back in to the inventory is to locate the datastore that is hosting the VM. Select Home > Inventory > Datastores

image001

Browse the folders and right click the corresponding .vmx configuration file and select Add to Inventory

You will be prompted for VMWare cluster and host before the VM is added back in to the inventory