Virtual Hardware (VMX) Template configuration
| Hardware |
Value |
| Memory |
2 GB |
| CPU’s |
Number of virtual sockets: 1
Number of cores per socket: 2 |
| Video card |
Number of video displays: 1
Total video memory: 5 MB (1280×1024) |
| VMCI device |
None |
SCSI Controller 0
Hard disk 1 |
LSI Logic SAS, bus sharing: none
40 GB, Thick Provision Eager Zeroed (<—best performance) |
| CD/DVD Drive 1 |
Client Device |
| Floppy Drive 1 |
Removed |
| Network Adapter 1 |
VMXNET3, network: VM Network with DHCP (for joining domain) |
| General Options |
OS: Microsoft Windows Server 2012 R2 (64-bit) |
| VMware Tools |
Advanced: Check and upgrade Tools during power cycling |
| Virtual Machine Version |
8 (not 9 because you only can edit version 9 via vSphere web-client) |
| Advanced > General |
Enable logging |
Virtual Machine BIOS configuration
| Configuration |
Value |
| Boot-time Diagnostics Screen |
Enabled |
Read more…
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
Categories: Hyper-V, Microsoft, VMware Tags: Advanced Configuration, BIOS, Favorite, How-To, Hyper-V, Microsoft, Performance, Template, VMware, vSphere, Windows 2012R2
Today I configured VMware Capacity Planner 2.8 by a customer, after I finished the Collected inventory + Performance data task I started the Synchronize job. The .csv files uploaded successfully but at the end of the job I received this warning messages:
ERROR: An unexpected error occurred! Module = vcpPerformance Function = UpdateTask:16 Source = Microsoft JET Database Engine Error = Syntax error in UPDATEstatement.(-2147217900:0:5003144)
ERROR: An unexpected error occurred! Module = vcpSysPerf Function = CollectSystemPerformance: Source = vcpSysPerf Error = Type mismatch(13:0:1000013)
Solution:
I used a Dutch Windows 7 workstation to install VMware Capacity Planner Data Manager v3.0.0, in the requirements (Page 9: VMware Whitepaper) I noticed “English Windows version required” …
… but.. in VMware KB you need only need to change the Regional Options to English (United States) like:
After I changed the settings, applied the configuration and restarted the workstation I was able to upload the discovered files to the VMware Capacity Planner Dashboard, happy me!
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
VMware VROOM released/updated a nice Performance Troubleshoot guide for vSphere 4.1
The hugely popular Performance Troubleshooting for VMware vSphere 4 guide is now updated for vSphere 4.1 . This document provides step-by-step approach for troubleshooting most common performance problems in vSphere-based virtual environments. The steps discussed in the document use performance data and charts readily available in the vSphere Client and esxtop to aid the troubleshooting flows. Each performance troubleshooting flow has two parts:
- How to identify the problem using specific performance counters.
- Possible causes of the problem and solutions to solve it.
New sections that were added to the document include troubleshooting performance problems in resource pools on standalone hosts and DRS clusters, additional troubleshooting steps for environments experiencing memory pressure (hosts with compressed and swapped memory), high CPU ready time in hosts that are not CPU saturated, environments sharing resources such as storage and network, and environments using snapshots.
This document by no means covers the entire breadth of performance-related problems. We request the readers of this document, including VMware performance community members and vSphere administrators, to help us enhance this document by letting us know about all the performance problems they encounter in their vSphere-based virtual environments, including those that require elaborate troubleshooting steps. We hope that the community will actively contribute by engaging in live discussions, providing feedback, and asking questions. All this input will serve as the topics for future updates
[gview file=http://communities.vmware.com/servlet/JiveServlet/downloadBody/14905-102-1-17952/vsphere41-performance-troubleshooting.pdf]
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
Virtual Hardware (VMX) template configuration:
| Hardware: |
Value: |
| Memory |
2 GB |
| CPU’s |
1 |
| Video card |
Auto-detect video settings |
| VMCI device |
None |
| SCSI Controller 0 |
LSI Logic SAS, bus sharing: none |
| Hard disk 1 |
40 GB, Thin (after deploy always Thick) |
| CD/DVD Drive 1 |
Client Device |
| Floppy Drive 1 |
Removed |
| Network Adapter 1 |
VMXNET3, network: VM Network with DHCP (for joining domain) |
| General Options |
OS: Microsoft Windows Server 2008 R2 (64-bit) |
| VMware Tools |
Advanced: Check and upgrade Tools during power cycling |
| Virtual Machine Version |
7 |
Microsoft Windows Server 2008 R2 template configuration:
– Install always the latest VMware Tools (in my case: ESXi 4.1 build 260247)
– Change the CD/DVD Drive 1 from drive letter D:\ to X:\
– Install VMware display driver: VMware SVGA 3D (Microsoft Corporation – WDDM)
Driver located: C:\Program Files\Common Files\VMware\Drivers\wddm_video\
Read more…
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
Last week I bought a brand new OCZ Agility Series 60 GB SSD for my workstation as OS disk. I started a fresh Windows 7 64-bit installation and made some software tweaks for optimal performance. Down here some of those little settings to maximize your performance.
I already upgraded the firmware to the latest level v.1.5
My computer specs: click here
Read more…
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
You can monitor/check your ESX performance with esxtop, by generating a share to your vCenter Server and view the results with Perfmon you can follow this article.
Create Credentials:
1. I created a new share on my vCenter 2003 on E:\Logging\
2. I created a new user with username: Logging and password: Logging
3. On the new created folder I add the Logging account with full permissions to the security rights:
Read more…
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
vSphere 4.0 introduces a new para-virtualized network device – VMXNET3. We recently published a paper demonstrating its performance characteristics, compared to that of enhanced VMXNET2 (the previous generation of high performance virtual network device from VMware).
Some highlights of this paper are:
(1) Throughput gains of up to 92% for 10G TCP/IPv4 Rx workloads with large socket buffer, which greatly improves bulk data transfer performance in a data center environment.
(2) Dramatic gains across all configurations of IPv6 traffic, with significant CPU usage reduction and throughput improvement over enhanced VMXNET2.
In a nutshell, VMXNET3 offers performance on par with or better than its predecessors on both Windows and Linux guests. Both the driver and the device have been highly tuned to perform better on modern systems. Furthermore, VMXNET3 introduces new features and enhancements, such as TSO6 and RSS. TSO6 makes it especially useful for users deploying applications that deal with IPv6 traffic, while RSS is helpful for deployments requiring high scalability. Moving forward, to keep pace with an ever-increasing demand for network bandwidth, we recommend customers migrate to VMXNET3.
For more details, please read our full paper from here.
Performance problems can arise in any computing environment. In a virtualized computing environment performance problems can arise due to new and often subtle interactions occurring in the shared infrastructure. Uncovering the causes of those problems requires an understanding of the available performance metrics and their relationship to underlying configuration issues.
A new guide covering performance troubleshooting for VMware vSphere 4, including ESX 4.0 hosts, is now available. This document uses a guided approach to lead the reader through the observable manifestations of complex hardware/software interactions in order to identify specific performance problems. For each problem covered, it includes a discussion of the possible root-causes and solutions. Topics covered include performance problems arising from issues in the CPU, memory, storage, and network subsystems, as well as in the VM and ESX host configuration.
The document is available on the VMware Performance Community.
Er zijn nogal wat problemen omtrent Windows Terminal Servers/Citrix op VMware ESX servers. Wat zijn nou de beste instellingen om performance te waarborgen.
Om dit allemaal uit te zoeken ben ik bezig geweest bij een klant die performance problemen ervaren. Deze klant heeft meerdere ESX hosts, een host heb ik gepakt om bezig te gaan met de performance problemen. De host en VM’s hebben de volgende specificaties:
ESX Host Configuratie:
Model: HP ProLiant DL380 G5
Processors: 8 CPU x 1,999 Ghz
Processor Type: Intel® Xeon® CPU E5335 @ 2.00 Ghz
Number of NICs: 6
OS: VMware ESX 3.5 u4
vSwitch Configuratie:
vSwitch 1:
Read more…
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
Recent Comments