showing posts tagged with 'virtualization'
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 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 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 March 19th 2015, at 12:39
Using the vSphere (Web) Client, it is only possible to "upgrade" your virtual hardware to the latest version supported by your ESX host. Sometimes, it's necessary to set the hardware version to a specific version, rather than just the latest supported one. This can be done through PowerCLI (for use with vCenter) or ESXi Shell (for free ESXi).

Before you begin, note that you have to power down a VM before you can change the hardware version.

You need VMWare vSphere PowerCLI installed on a computer, and access to a vCenter server (can be appliance or full version for Windows) with the necessary credentials.

Connect to the vSphere server:

$cred = Get-CredentialConnect-VIServer -Se  ...
by lunarg on January 27th 2015, at 12:56
You may get an error during the upgrade of Veeam Backup & Recovery to version 8, stating that the vPower NFS service is unable to start. Alternatively, when updating the individual components, you may also get a similar error (such as: "Error 1920.Service Veeam vPower NFS Service (VeeamNFSSvc) failed to start. Verify that you have sufficient privileges to start system services.").

There are several reasons possible for this, but the most likely one is a wrong NFS Datastore path specified in the registry, usually because the drive that the datastore is pointing to, is no longer present.
Another reason could be that your server has the "NFS sharing" feature installed,   ...
by lunarg on January 8th 2014, at 12:34
Even though you've unchecked the time synchronisation checkbox in VMware Tools, synchronisation may still occur. Particularly when a certain action is performed, such as a power-off/power-on, suspend/resume, snapshot handling, etc., time synchronisation will still occur.

To complete disable time synchronisation, even during the events mentioned, you have to add additional parameters to the VMware VM configuration. There are two ways to do this.

Note that you need to have the machine powered off before you can do these changes.

Use a text editor to directly edit the .vmx-file, adding the required parameters:

tools.syncTime = "0"time.synchronize.continue = "0"time.synchronize.restore = "0"  ...
by lunarg on April 3rd 2013, at 10:15
Currently, vCenter Server 5.1 is not supported on Windows Server 2012. Trying to install usually results in several errors, but they can be resolved with some workarounds and things to consider. This post is a gathering of (some of) those things.

First of, be sure to install .NET 3.5 using the Server Manager. It can be found as a feature. The installation delivered in the vCenter installation cannot be installed.

It's best to install the required components (SSO and Inventory Service) separately to ensure the installation of the different components goes smoothly. You will have to type in and remember the SSO passwords though.

Upon installation of the vCenter Server, it will insta  ...
by lunarg on April 4th 2011, at 15:51
With the installation of VMware ESXi 4, data stores will automatically be created using the default settings. This includes a block size of 1 MB. If you don't want that, you could delete the empty datastore and create a new one.

Sometimes, deleting the empty datastore fails with the message:

Call "HostDatastoreSystem.RemoveDatastore" for object "ha-datastoresystem" on ESXi "xx.xx.xx.xx" failed.

VMware's KB 1017104 provides the solution for another problem, but this works just as well with this issue, with a little variation.

Performing the steps in this solution will totally utterly destroy your data store. Do not use it if there's still any req  ...
by lunarg on March 8th 2011, at 10:28

Everything you need to set up and use VDI for free...

That's what Citrix is providing nowadays with XenDesktop Express. It provides full VDI for up to 10 users, and can work with XenServer, Hyper-V and VMware.

The full link to everything is this one:

by lunarg on October 15th 2010, at 11:54
At work, I'm currently deploying a Windows 2008 R2 on a VMware ESXi 4.0, and noticed an odd behaviour. At irregular intervals, the console of the guest OS simply locks up and doesn't do anything anymore. Networking and remote access seem to work fine, it's just the console that is freezed. Restarting the vSphere client doesn't help, and the only way to get rid of the problem is by hard-resetting the VM. The issue only occurs on Windows 2008 R2, the other VMs run fine.

The problem is caused by the VMware SVGA II driver, and has two underlying issues: the driver itself, and an apparent lack of video RAM (due to the new HW-accelerated GDI of 2008R2/Win7).

The most quickest way is to get rid o  ...
by lunarg on June 30th 2010, at 17:12
While not documented, it is possible to activate remote SSH access to an ESXi 4.0 (free or paid license).

You need console access to the machine to turn on SSH access; it cannot be done with the vSphere client.

At the console, press Alt+F1 to switch to the console. You will not see a prompt, but you will be able to type in the logon name.

Type in unsupported then press Enter; you will see a Password: prompt. If you did not set a password in ESXi, type in unsupported. If a password was set for the root account, type in that password.

Once logged in, navigate to /etc, and open the file inetd.conf.

~ # cd /etc/etc # vi inetd.conf

In the file, find and uncomment the line(s) f  ...
by lunarg on October 5th 2009, at 21:49
When running a Windows XP or 2003 in VirtualBox, under certain circumstances, the guest may generate a BSOD when booting. The message of the BSOD is a:


It is accompagnied by a referral to processr.sys, intelppm.sys or p3.sys, depending on the CPU used to install the machine.

The reason for this BSOD is a problem with these drivers, trying to perform an unsupported operation inside the virtual machine (like updating microcode or changing the power state of the CPU).
The issue usually surfaces when the guest machine is moved to a different system with different CPU time.

To resolve the issue, the processor drivers have to be disabled. T  ...
by lunarg on April 17th 2008, at 12:56

If you're using NAT for networking with your VMs, you need to use port forwarding if you want to access a VM from the outside network. This is a quick and dirty howto on how to do this in linux.

Fire up a terminal, and enter these commands:

VBoxManage setextradata nvm3 "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/HostPort" 28080
VBoxManage setextradata nvm3 "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/GuestPort" 28080
VBoxManage setextradata nvm3 "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/Protocol" TCP

In the sample above, I'm forwarding port 28080/tcp from the host to 28080/tcp on the guest. My VM's name is nvm3.

by lunarg on August 1st 2007, at 14:07

A document about the installation of the IBM Director and ServeRAID manager in VMware ESX 3 can be found here:

Should be useful to anyone who cares... If I ever get the chance to try it out myself (which should be fairly soon), it would probably be added (after rewriting, of course).

by lunarg on April 3rd 2007, at 17:28

Found this article to be useful while installing a Gentoo in a virtual machine for VMware:

I found the kernel configuration portion particularly useful, especially since I managed to enable every SCSI controller and network adapter accept the one I needed.

by lunarg on March 28th 2007, at 11:10

If VMware Server Console doesn't work on your Ubuntu 6.10 Edgy install, here's what to do.

If after installing, the console does not launch, but instead takes up 100% CPU until the end of days (or until you kill it), try starting the console with this command:

LD_PRELOAD=/usr/lib/$LD_PRELOAD vmware-server-console

This fixes some yet to be resolved issue around shared libs.

showing posts tagged with 'virtualization'