Life of a Geek Admin

The Daily adventures of a true geek administrator

Life of a Geek Admin - The Daily adventures of a true geek administrator

Category Archives: Virtualization

Optimal Network Adaptor Settings for VMXNET3 and Windows 2008 R2

There is an ongoing debate between many admins on what are the best settings for the VMXNET3 driver on Windows 2008 R2 settings and I suppose there will be many more. In this postI will attempt to point out some of the options and recommended settings for the VMXNET3 adaptor.

 Global Settings

Receive Side Scaling (RSS)

Receive-Side Scaling (RSS) resolves the single-processor bottleneck by allowing the receive side network load from a network adapter to be shared across multiple processors. RSS enables packet receive-processing to scale with the number of available processors. This allows the Windows Networking subsystem to take advantage of multi-core and many core processor architectures.

By default RSS is set to enabled. To disable RSS you must open a command prompt and type:

netsh int tcp set global rss=disabled

There is also a second RSS settings that is in the VMXNET3 adaptor properties under the Advanced tab, which is disabled by default. Enable it by selecting from the dropdown.

This is a beneficial setting if you have multiple vCPU’s on the server. If this is a single vCPU then you will receive no benefit.

If you have multiple vCPU’s it is recommended to have RSS enabled.

netsh int tcp set global rss=enabled

References

http://technet.microsoft.com/en-us/network/dd277646.aspx

TCP Chimney Offload

TCP Chimney Offload is a networking technology that helps transfer the workload from the CPU to a network adapter during network data transfer. In Windows Server 2008, TCP Chimney Offload enables the Windows networking subsystem to offload the processing of a TCP/IP connection to a network adapter that includes special support for TCP/IP offload processing.

For VMXNET3 on ESXi 4.x, 5.0 and 5.1 TCP Chimney Offload is not supported; turning this off or on has no affect. This is discussed in several places.

References

http://www-01.ibm.com/support/docview.wss?uid=isg3T1012648

http://support.microsoft.com/kb/951037

The Microsoft KB951037 article is of interest because it includes a table that shows how TCP Chimney interacts with programs and services and gives insight to where you can gain the most from this feature. By default this setting is enabled.

As for the use of TCP Chimney Offload is to disable as it is not recognized by VMXNET3. To disable do the following.

Open a command prompt with administrative credentials.

At the command prompt, type the following command, and then press ENTER:

netsh int tcp set global chimney=disabled

To validate or view TCP Chimney

netsh int tcp show global

Recommended setting: disabled

 NetDMA State

NetDMA provides operating system support for direct memory access (DMA) offload. TCP/IP uses NetDMA to relieve the CPU from copying received data into application buffers, reducing CPU load.

Requirements for NetDMA

  • NetDMA must be enabled in BIOS
  • CPU must support Intel I/O Acceleration Technology (I/OAT)

You cannot use TCP Chimney Offload and NetDMA together.

Recommended setting: disabled

TCP Receive Windows Auto-Tuning Level

This feature determines the optimal receive window size by measuring the BDP and the application retrieve rate and adapting the window size for ongoing transmission path and application conditions.

Receive Window Auto-Tuning enables TCP window scaling by default, allowing up to a 16MB maximum receive window size. As the data flows over the connection, it monitors the connection, measures its current BDP and application retrieve rate, and adjusts the receive window size to optimize throughput. This replaces the TCPWindowSize registry value.

Receive Window Auto-Tuning has a number of benefits. It automatically determines the optimal receive window size on a per-connection basis. In Windows XP, the TCPWindowSize registry value applies to all connections. Applications no longer need to specify TCP window sizes through Windows Sockets options. And IT administrators no longer need to manually configure a TCP receive window size for specific computers.

By default this setting is enabled, to disable it open a command prompt with administrative permission and type:

netsh int tcp set global autotuninglevel=disabled

Recommended setting: disabled

References

http://technet.microsoft.com/en-us/magazine/2007.01.cableguy.aspx

Add-On Congestion Control Provider

The traditional slow-start and congestion avoidance algorithms in TCP help avoid network congestion by gradually increasing the TCP window at the beginning of transfers until the TCP Receive Window boundary is reached, or packet loss occurs. For broadband internet connections that combine high TCP Window with higher latency (high BDP), these algorithms do not increase the TCP windows fast enough to fully utilize the bandwidth of the connection.

Compound TCP, CTCP increases the TCP send window more aggressively for broadband connections (with large RWIN and BDP). CTCP attempts to maximize throughput by monitoring delay variations and packet loss. It also ensures that its behavior does not impact other TCP connections negatively.

By default, it is on by default under Server 2008. Turning this option on can significantly increase throughput and packet loss recovery.

To enable CTCP, in elevated command prompt type:

netsh int tcp set global congestionprovider=ctcp

To disable CTCP:

netsh int tcp set global congestionprovider=none

Possible options are:  ctcp, none, default (restores the system default value).

Recommended setting: ctcp

ECN Capability

ECN (Explicit Congestion Notification) is a mechanism that provides routers with an alternate method of communicating network congestion. It is aimed to decrease retransmissions. In essence, ECN assumes that the cause of any packet loss is router congestion. It allows routers experiencing congestion to mark packets and allow clients to automatically lower their transfer rate to prevent further packet loss. Traditionally, TCP/IP networks signal congestion by dropping packets. When ECN is successfully negotiated, an ECN-aware router may set a bit in the IP header (in the DiffServ field) instead of dropping a packet in order to signal congestion. The receiver echoes the congestion indication to the sender, which must react as though a packet drop were detected.

ECN is disabled by default, as it is possible that it may cause problems with some outdated routers that drop packets with the ECN bit set, rather than ignoring the bit.

To change ECN, in elevated command prompt type:

netsh int tcp set global ecncapability=default

Possible settings are: enabled, disabled, default (restores the state to the system default).

The default state is: disabled

ECN is only effective in combination with AQM (Active Queue Management) router policy. It has more noticeable effect on performance with interactive connections and HTTP requests, in the presence of router congestion/packet loss. Its effect on bulk throughput with large TCP Window is less clear.

Currently, it is not recommended enabling this setting, as it has negative impact on throughput.

Recommended setting is disabled

netsh int tcp set global ecncapability=disabled

Direct Cache Access (DCA)

Direct Cache Access (DCA) allows a capable I/O device, such as a network controller, to deliver data directly into a CPU cache. The objective of DCA is to reduce memory latency and the memory bandwidth requirement in high bandwidth (Gigabit) environments. DCA requires support from the I/O device, system chipset, and CPUs.

To enable DCA:

netsh int tcp set global dca=enabled

Available states are: enabled, disabled.

Default state: disabled

Recommended setting is disabled

To disable DCA:

netsh int tcp set global dca=disable

These are just settings that I have used successfully in the VMware environment and work well. You can pick and choose the settings that work best for your environment.

Network performance with VMXNET3 on Windows Server 2008 R2

Recently we ran into issues when using the VMXNET3 driver and Windows Server 2008 R2, according to VMWare you may experience issues similar to:

•Poor performance
•Packet loss
•Network latency
•Slow data transfer

The issue may be caused by Windows TCP Stack offloading the usage of the network interface to the CPU.

To resolve this issue, disable the TCP Checksum Offload feature, as well enable  RSS on the VMXNET3 driver.
Open the command prompt as administrator and run these commands:

netsh int tcp set global chimney=Disabled
netsh int tcp set global autotuninglevel=Disabled
netsh int tcp set global congestionprovider=None
netsh int tcp set global ecncapability=Disabled
netsh int ip set global taskoffload=disabled
netsh int tcp set global timestamps=Disabled

To validate type:

netsh int tcp show global

Next we will need to turn on RSS feature on the VMXNET3 driver. To do this open the network connections and adapter settings. Open Control Panel > Network and Internet > Network Connections. Right click on your adapter and select properties.

vmxnet3_4

Click on the Advanced tab and scroll down to find the RSS setting, you will see by default it is set to disabled. Set the drop down to enabled and click ok to save the settings.

vmxnet3_3

 

If you find there is no change just reset to default.

To reset to default type:

netsh int tcp set global chimney=Enabled
netsh int tcp set global autotuninglevel=normal
netsh int tcp set global congestionprovider=ctcp
netsh int tcp set global ecncapability=Enabled
netsh int ip set global taskoffload=Enabled
netsh int tcp set global timestamps=Enabled

How to determine whether TCP Chimney Offload is working
When TCP Chimney Offload is enabled in the operating system and in the network adapter, the TCP/IP stack tries to offload suitable TCP connections to the network adapter. To find out which of the currently established TCP connections on the system are offloaded, follow these steps:

Use administrative credentials to open a command prompt.
Type the following command, and then press ENTER:

netstat –t

You receive output that resembles the following:

Active Connections
Proto  Local Address          Foreign Address        State           Offload State
TCP    127.0.0.1:52613        computer_name:52614    ESTABLISHED     InHost
TCP    192.168.1.103:52614    computer_name:52613    ESTABLISHED     Offloaded

In this output, the second connection is offloaded.

How To Connect to a Local Directory on a Windows Host with a Linux Guest in VirtualBox

Recently I felt the need to retrieve files from my Windows host on my Linux guest in VirtualBox 4.2.6. This is an easy task with the VBoxAdditions installed on the guest OS and a simple change in the shared folders in VirtualBox.

If VBoxAdditions are not installed on the guest host you must first get them installed. If you are running Fedora 17 or 18 look here for the instructions.

Next make sure to power off the guest VM and once powered off open the Settings for the VM and click on Shared folders.

shared1

Click on the add folder icon on the right side and a dialog box will open asking for the folder to add, you can type in the path ex: c:\Download or browse for it by selecting the drop down and select Other.

shared2

Insert a Folder Name and select Auto-mount. Click OK to accept the changes and restart the guest VM.

shared3

Once you have logged into your Linux VM you are ready to create a directory to mount and then mount the shared folder. In this example I have created the /mnt/share folder. Now all that is needed is to execute.

$ sudo mount -t vboxsf Download /mnt/share

Now we can get to the files but this command will have to be run every time, so why not create a shell script called mntshare.sh and just populate it with the exact command you ran. Now each time you start the VM you just run ./mntshare.sh.

Note that with this, the default mount options are used and all files are owned by root. This can be changed by adding some mount options. Options are passed on with the -o parameter. You can use multiple options with one parameter, separate the values with a comma.

$ sudo mount -t vboxsf -o uid=1000,gid=1000 Download /mnt/share

And that is all there is to creating and accessing a shared folder in VirtualBox.

How to Install VMWare Workstation 8.0.4 on Fedora 17

Recently ran into an issue were I was receiving VMWare module compilation errors when installing VMWare Workstation 8.0.4. The error I was receiving was it couldn’t execute and find the kernel-headers which were installed but not where VMWare was looking for them.

Download and install latest licensed version 8.0.4 from http://www.vmware.com/support

$ chmod +x VMware-Workstation-Full-8.0.4-744019.x86_64.bundle
$ sudo ./VMware-Workstation-Full-8.0.4-744019.x86_64.bundle

Install needed modules for module compilation

$ sudo yum install automake autoconf gcc kernel-devel kernel-headers

Now to fix the compilation error. Thanks to Weltall’s Blog (http://weltall.heliohost.org/wordpress) we have a patch. Download and install patch for module compilation error from

http://weltall.heliohost.org/wordpress/2012/04/01/vmware-workstation-8-0-2player-4-0-2-and-7-1-x3-1-x-fix-for-linux-kernel-3-4-0/

Extract the tarball and edit patch-modules_3.4.0.sh

$ vi patch-modules_3.4.0.sh

We need to make the change because the script is looking for 8.0.2 and we have 8.0.4.

Change:

vmreqver=8.0.2
plreqver=4.0.2

to

vmreqver=8.0.4
plreqver=4.0.4

Run the patch as root

$ sudo ./patch-modules_3.4.0.sh

Now we are ready to fire up VMWare Workstation 8.0.4 and start virtualizing.

How To Set Your VirtualBox 4.2 VM to Automatically Startup

Being system administrators and tweakers we always like to make things automatically take care of themselves, right? Well of course we do and that’s where any auto starts we find are likely to get put in place.

A new feature added in VirtualBox 4.2 is autostart, this feature is available in Linux, Solaris and MacOSX hosts only. Let’s say there is a VirtualBox VM you start everytime  you startup your system, why not make it startup as soon as you start VirtualBox. I am using Fedora 17 for this example.

First you need to create the file /etc/default/virtualbox and add a few variables.

VBOXAUTOSTART_DB which contains an absolute path to the autostart database directory and VBOXAUTOSTART_CONFIG which contains the location of the autostart config settings. The file should look similar to this:

# vi /etc/default/virtualbox
# virtualbox defaults file
VBOXAUTOSTART_DB=/etc/vbox
VBOXAUTOSTART_CONFIG=/etc/vbox/vbox.cfg

Update: It has been commented that the file named vbox.cfg didn’t work for some. They have been successful using autostart.cfg, if vbox.cfg doesn’t work for you, then trying naming the file autostart.cfg.

Now we need to create /etc/vbox/vbox.cfg file and add

# Default policy is to deny starting a VM, the other option is "allow".
default_policy = deny
# Create an entry for each user allowed to run autostart
myuserid = {
allow = true
}

If you are the only user you can just add the line default_policy = allow to the vbox.cfg file.

Set permissions on directory to the vboxuser group and make sure users can write to the directory as well as sticky bit.
# chgrp vboxusers /etc/vbox
# chmod 1775 /etc/vbox

Add each of the users to the vboxusers group. Make sure to check their group memberships so they do not loose any groups they currently have assigned to their id.

# groups myuserid
myuserid wheel

# usermod -G wheel, vboxusers myuserid

Every user who wants to enable autostart for individual machines has to set the path to the autostart database directory with

$ VBoxManage setproperty autostartdbpath /etc/vbox

Now we are ready to set the VM’s we choose to start.

$ VBoxManage modifyvm --autostart-enabled on

This will create a myuserid.start  file in /etc/vbox directory

Now restart the vboxautostart-service to read in the changes.
# service vboxautostart-service restart

Reboot your system and your VM should start

VirtualBox 4.1.20 Released

VirtualBox 4.1.20 Released !!! make sure to update your installation to get the latest bugfixes,!
This is a maintenance release. The following items were fixed and/or added:

  • VMM: fixed a crash under rare circumstances for VMs running without hardware virtualization
  • VMM: fixed a code analysis bug for certain displacement instructions for VMs running without hardware virtualization
  • VMM: fixed an interpretion bug for TPR read instructions under rare conditions (AMD-V only)
  • Snapshots: fixed a crash when restoring an old snapshot when powering off a VM (bugs #9604, #10491)
  • VBoxSVC: be more tolerant against environment variables with strange encodings (bug #8780)
  • VGA: fixed wrong access check which might cause a crash under certain conditions
  • NAT: final fix for crashes under rare conditions (bug #10513)
  • Virtio-net: fixed the problem with receiving of GSO packets in Windows XP guests causing packet loss in host-to-VM transfers
  • HPET: several fixes (bugs #10170, #10306)
  • Clipboard: disable the clipboard by default for new VMs
  • BIOS: the PCI BIOS was not properly detected with the chipset type set to ICH9 (bugs #9301, #10327)
  • Mac OS X hosts: adaptions to Mountain Lion
  • Linux Installer: fixes for Gentoo Linux (bug #10642)
  • Linux guests: fixed mouse integration on Fedora 17 guests (bug #2306)
  • Linux Additions: compile fixes for RHEL/CentOS 6.3 (bug #10756)
  • Linux Additions: compile fixes for Linux 3.5-rc1 and Linux 3.6-rc1 (bug #10709)
  • Solaris host: fixed a guru meditation while allocating large pages (bug #10600)
  • Solaris host: fixed possible kernel panics while freeing memory
  • Solaris Installer: fixed missing icon for menu and desktop shortcuts

Download the latest here and don’t forget to download the latest extensions as well.

Create VM’s from the Command Line with VirtualBox 4

In an earlier post on creating screenshots using vboxmanage command in VirtualBox. Building on using vboxmanage command I discovered that I could create and modify a VM at the command line. This is an awesome feature if you are always building and deleting VM’s for testing an other purposes.

So in this post I want to cover how to create an modify a VM in VirtualBox from the command line. So let’s get typing.

cd C:\Program Files\Oracle\VirtualBox\
vboxmanage createvm --name winxp --ostype WindowsXP --register


Get a list of available ostypes use the vboxmanage list ostypes command. The output will scroll off the screen so add | more to the command so it is easy to move down by using the enter key.

VBoxManage list ostypes | more


Now we have a vm but it has no attached storage and has the defaults, so we need to make changes, this is where the createhd, storageattach, storagectl and modifyvm parameters come in to play.

First lets create a disk and attach it to the system.

There are many parameters that you can pass to modifyvm, for greater detail you should refer to the online user manual or execute vboxmanage modifyvm | more and page through the various options. Since we are modifying the VM we just created we will just need to modify parameters.

  • network (--nic<1-N> none|null|nat|bridged|intnet|hostonly|generic)
  • memory (–memory)
  • Video Ram (–vram)
  • boot1 (installation)

For our setting we want 512 MB ram, the nic to use NAT, video ram at 128 MB and set first boot to installation DVD. So our syntax is as below.

VBoxManage modifyvm "winxp" --memory 512 --boot1 dvd --nic1 nat --vram 128

Next we need to create a virtual hard disk for the VM and set it to 10 GB.

VBoxManage createhd --filename "winxp.vdi" --size 10000

Now lets add an IDE controller to the VM.

VBoxManage storagectl "winxp" --name "IDE Controller" --add ide --controller PIIX4

Next we will need to assign the vdi (HD) we create earlier to the IDE Controller we added.

VBoxManage storageattach "winxp" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium "winxp.vdi"

Attach the ISO file that contains the operating system installation that you want to install later to the virtual machine, so the machine can boot from it.

VBoxManage storageattach "winxp" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium /path_to/winxp.iso

Finally lets start the VM using the VBoxHeadless command to start the installation. If successful you will see a copyright notice.

VBoxHeadless --startvm "winxp"

Thats all there is to create a VM in VirtualBox from the command line. There are other settings that have to be set through the GUI that cannot be set from the command line. There are also more settings that can be done from the command line. Explore and see what else is possible by using vboxmanage!!

 

Creating Virtualbox Screenshots with VBoxManage

As a system admin by day I am always documenting how something was done so that others can do it themselves and also as a blogger as well. Text is wonderful but sometimes pictures are much better at explaining.

With Windows and Linux there are many point and click solutions like Snipping Tool (Windows 7), KSnapshot (KDE) and many others, but sometimes the command line is better and can be scripted.

One such documentation task I recently completed was relying heavily on Virtualbox and what I was needing was the whole screen and not a cropped image. Luckily the VBoxManage command includes a parameter controlvm (screenshotpng) to accomplish such a task.

The syntax is:

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" controlvm "" screenshotpng

As an example mhlinux3 is the name of my vm and test1.png for the filename. So the command will look like

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" controlvm "mhlinux3" screenshotpng c:\temp\test1.png

Pretty simple. So now lets automate it and create a command script that prompts for a filename. We can use the set command to define the variables and set /P to prompt for the filename.

For the variables we need to set the filename, the vboxmanage command, the output directory and the vm. For the output directory I have created a screenshots folder on the desktop. Below is the script which is saved as vmsnap.cmd on the desktop.

echo off
rem Create Virtualbox screenshots on windows
rem Prompt for filename
set /P ssname="Enter filename: " %=%
set vboxmanage="C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"

rem Specify the output directory
set outputdir=%USERPROFILE%\Desktop\screenshots

rem Specify the name of the VM here of which you want to take a screenshot
set vm=mhlinux3

%vboxmanage% controlvm "%vm%" screenshotpng %outputdir%\%vm%_%ssname%.png

If we double-click on the saved script a command box will appear waiting for a filename.

Enter in the name and press enter and the snapshot will complete and the window will close and if we check in the folder we will see the finished product.

And if we open the screenshot we see the finished product.

Happy snapping !!

Updating VMWare ESXi Hypervisor 5

Recently I built a VMWare ESXi Hypervisor 5 server for testing and learning purposes. As a good admin you must always patch and VMWare is no exception.

First download and install VMWare vCLI from http://www.vmware.com/support/developer/vcli/. You must have an account on VMWare to download the products, the account is free. I will be using vCLI installed on Windows 7 x64 Professional, so the path maybe different on your installation.

Now Download the latest patch from http://www.vmware.com/patchmgr/findPatch.portal. The current patch is ESXi500-201204001.zip. Once you have downloaded the latest patch copy it to a datastore on the ESXi 5 server or a place the server to patch has access to, for this post I am using /vmfs/volumes1/datastore2/updates. Download the zip file and do not extract it. Open vCLI session.

First we need to see if the server needs to be in Maintenance Mode for the patch, issue the following command:

esxcli --server=192.168.1.80 --username=root software sources vib get -d /vmfs/volumes/datastore2/updates/ESXi500-201204001.zip | grep "Maintenance Mode Required: True"

If grep returns a True then lets put it in maintenance mode, issue the following command:

"C:\Program Files (x86)\VMware\VMware vSphere CLI\Perl\bin\perl" vicfg-hostops.pl --server 192.168.1.80 --operation enter

Verify the host is in maintenance mode,issue the following command:

"C:\Program Files (x86)\VMware\VMware vSphere CLI\Perl\bin\perl" vicfg-hostops.pl --server=192.168.1.80 --operation info

Verify what vib’s are installed, issue the following command:

esxcli --server=192.168.1.80 --username=root software vib list | more

To find out which VIBs are available in the depot (the downloaded .zip file), issue the following command:

esxcli --server=192.168.1.80 --username=root software sources vib list --depot=/vmfs/volumes/datastore2/updates/ESXi500-201204001.zip | more

To update the ESXi 5 host with the VIBs included in the depot, issue the following command:

esxcli --server=192.168.1.80 --username=root software vib update --depot=/vmfs/volumes/datastore2/updates/ESXi500-201204001.zip

When the update is complete, verify the information presented. If prompted, reboot the ESXi 5 host by issuing the following command:

"C:\Program Files (x86)\VMware\VMware vSphere CLI\Perl\bin\perl" vicfg-hostops.pl --server 192.168.1.80 --operation reboot

Verify the patch bundle was installed, by issuing the following command:

esxcli --server=192.168.1.80 --username=root software vib list | more

If applicable, take the ESXi 5 host out of maintenance mode using the vSphere Client or with the following command:

"C:\Program Files (x86)\VMware\VMware vSphere CLI\Perl\bin\perl" vicfg-hostops.pl --server 192.168.1.80 --operation exit

If the operation  exit command fails just open vSphere client and remove the server from Maintenance mode and un-pause the vm’s on the server.

Note: All of this can be done from a Linux system as well. VMWare provides a Linux vCLI download as well. The difference in the commands is that the perl preface used for Windows can be omitted as well as the .pl on the end of the command.

Installing and updating ESXi 5 VMtools with OSP

Recently I had the pleasure of building n ESXi Hypervisor 5 server. Server sprawl has taken over and the time has come to consolidate. The first VM’s to create are my web and database servers. After the build I was needing to install VMtools to get the full functionality on my CentOS / SL / RHEL 6 servers.

There are several ways to do this but a way to add a repo and have it install updates when I update the servers is a better way, so that lead me to OSP (Operating System Specific Packages).

Checking the internet I found Operating System Specific Packages pdf that describes the process here.

The process I used here is for CentOS 6.2 / RHEL 6.2 and SL (Scientific Linux) 6.2. First I downloaded and imported the RSA and DSA certificates.

# wget http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-DSA-KEY.pub
# wget http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-RSA-KEY.pub
# rpm --import VMWARE-PACKAGING-GPG-RSA-KEY.pub
# rpm --import VMWARE-PACKAGING-GPG-DSA-KEY.pub

Now lets create the repo file. Name it vmwaretools.repo in /etc/yum.repos.d directory with the following contents.

[vmware-tools]
name=VMware Tools
baseurl=http://packages.vmware.com/tools/esx/5.0/rhel6/x86_64
enabled=1
gpgcheck=1

Save the file and type:

# yum update

And let the repository populate the information you need. Now we need to install the correct tools. Since I am using ESXi Hypervisor 5 I am limited to 1 CPU so I really don’t need to look and see if I have PAE enabled kernels. If I did, we would need to check using uname -r and look for the PAE designation in the kernel release.

# yum install vmware-tools-esx-kmods vmware-tools-esx

Once the tools have been downloaded and installed all that is needed is a reboot.

 

 

Switch to our mobile site