Even on a 2 GB RAM workstation (as mine) VMware virtual machines can run slowly. Too slowly sometimes.
This can depend on a large amount of factors but we can reduce the number to 4 critical issues:
- Antivirus real-time protection
You probably run VMware Workstation on your everyday working computer, and you probably want to stay secure running an antivirus software.
The most useful feature of any AV is the real-time protection, catching and monitoring I/O accesses of every process for suspicious activities.
This feature can greatly impact on your VMs performances and should be fine-tuned for virtualization.
So be sure to create an exclusion filter on your real-time protection settings for .vmdk (VMware virtual disk) and .vmem (VMware virtual memory) files. In this way countinous I/O operations on your virtual machines will not be hit by antivirus checking.
Note: if you plan to run liveCD operating systems (like Knoppix) inside your VMs or simply often use CD images for installing new software, I highly recommend to exclude .iso files too from AV checking.
- HostOS disk fragmentation
A really performance hitter for virtual machines is a fragmented host OS disk.
VMs virtual disks are very large (4 GBs at minimum on the average) and are created by default as non preallocated. In other words your virtual disk grow as you install more software on the guest OS till reaching your defined disk limit.
If you use only one physical disk for everyday work and VMs storing, you probably will use space around a growing virtual disk, obliging your host OS to fragment virtual machines more and more.
So be sure to:
- Create a dedicated partition for virtual machines only
- Create guest OSes virtual disks with Allocate all disk space now option
- Schedule a daily defragmentation for your virtual machines directories (maybe at launch time or during the night)
- Memory trimming
Workstation checks which part of the guest OS virtual memory is not used and allocates it back to the host OS. This permits to have more concurrent virtual machines running but everytime the guest OS asks back for its memory it suffers a performance degradation.
So, if you have enough free RAM for all planned concurrent VMs, be sure to disable memory trimming for guest OSes adding the following line to the virtual machine configuration (.vmx) file:
Note: Memory trimming can be disabled through GUI since Workstation 6.0.
- Page sharing (quoted from VMware documentation)
VMware uses a page sharing technique to allow guest memory pages with identical contents to be stored as a single copy-on-write page. Page sharing decreases host memory usage, but consumes system resources, potentially including I/O bandwidth.
You may want to avoid this overhead for guests for which host memory is plentiful and I/O latency is important. To disable page sharing, add the following line to the virtual machine configuration (.vmx) file:
These suggestions will work well for every VMware Workstation 5.x and Player 1.x since both share same engine.
blog comments powered by Disqus
virtualization.info Newest articles
October 21st, 2016
Citrix announced its financial results for third quarter 2016.
The revenues for the second quarter were $841 million for an increase of 3% compared to Q3 2015.
Net income was $132…
October 19th, 2016
2016 edition of VMworld US has been quite turbulent, on the other hand during VMworld Europe, happening these days in Barcelona, the company announced a few more products for the…
October 18th, 2016
Log Insight is a log aggregation, management and analisys tool, that VMware first introduced in 2013 and now is usually compared with Splunk.
Yesterday VMware announced Log Insight’s new major…
October 13th, 2016
Yesterday Microsoft announced the general availability of Windows Server 2016 which the company defines as a cloud-ready OS.
Beside fancy definitions, one of the most relevant perks of this release…
September 22nd, 2016
During Oracle OpenWorld 2016 the company released version 3.4.2 of its enterprise virtualization solution.
Oracle VM is available for both x86 and SPARC based processor architectures and uses the Xen hypervisor…
September 1st, 2016
Today was the last day of VMware’s flagship conference VMworld in Las Vegas, an highly controversial edition which left a good chunk of the audience disoriented if not properly disappointed….
August 11th, 2016
Last week Gartner updated its Magic Quadrant for Cloud Infrastructure as a Service (IaaS) for the year 2016. The Magic Quadrant for the year 2015 was released in May last year…
August 2nd, 2016
Ansible is one of the four main players in the automation market, younger then the well known Chef and Puppet, has been launched in 2013 in Durham, N.C. and acquired…
July 19th, 2016
Yesterday IBM announced its results for Q2 2016.
If we compare with the same quarter in 2015 earnings per share, from continuing operations, decreased 22%. Net income, from continuing operations,…
June 24th, 2016
Red Hat announced its financial results for the first quarter of fiscal year 2017.
Total revenue for the first quarter was $568 million, with an increase of 18% from the…
June 24th, 2016
Today Red Hat released in beta version 4.0 of its KVM-based virtualization platform Red Hat Enterprise Virtualization (RHEV).
As a major release RHEV 4.0 ships a wide series of enhancements including:
June 21st, 2016
virtualization.info has been following WhatMatrix since its inception and, after 6 months since the website has been launched, we are happy to report that its community is growing and contributing…
June 21st, 2016
DockerCon 2016 began yesterday in Seattle with a number of announcements from Docker and key partners.
Here is a quick summary of the day:
Docker 1.12 with built-in orchestration: starting…
June 14th, 2016
Yesterday, Bellevue (WA) based company WinDocks, released a free edition of its homonymous port of the Docker daemon to Windows called WinDocks Community Edition.
The company, founded by a small…