Category: VMWare

Performance Best Practices for VMware vSphere 4.1

VMware has released another great “technical paper” regarding Performance Best Practices for VMware vSphere 4.1. It can be found in the Technical Resource Center which by the way contains a lot of awesome docs.

The technical paper, Performance Best Practices for VMware vSphere 4.1, provides performance tips that cover the most performance-critical areas of VMware vSphere 4.1. It is not intended as a comprehensive guide for planning and configuring your deployments.

Chapter 1 – “Hardware for Use with VMware vSphere,” provides guidance on selecting hardware for use with vSphere.

Chapter 2 – “ESX and Virtual Machines,” provides guidance regarding VMware ESX™ software and the virtual machines that run in it.

Chapter 3 – “Guest Operating Systems,” provides guidance regarding the guest operating systems running in vSphere virtual machines.

Chapter 4 – “Virtual Infrastructure Management,” provides guidance regarding resource management best practices.

http://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.1.pdf

Source

Free Hyper9 GuessMyOSToo Plug-in for VI3 and vSphere4

This plug-in replaces generic VM icons in the VI3 and vSphere4 client inventory trees with OS-specific icons for both Windows and Linux guests.

gos-02
System Requirements
The only requirement is Virtual Center 2.5 or higher. The Hyper9 product is NOT required.

Download HERE

Exchange 2007/2010 Performance settings on vSphere.

When install a Exchange 2007 or Exchange 2010 Server on vSphere there are some settings that will increase de performance.

– Use de VMXNET 3 Adapter
– Use per Disk a SCSI Controller
– Store the Log & Database files on physical Lun on a SAN
– Use the LSI LOGIC SAS controller for Windows 2008 & 2008 R2
– Use the VMware Paravirtual SCSI (PVSCSI) Controller for Every physical Raw Device Mapping (RDM).

Another TIP.  Exchange 2007 & Exchange 2010 needs a lots of Memory. When choosing the size for the OS partition, swap file need also al lot of space.

Vizioncore release free VMware Management Pack for OpsMgr

Vizioncore, a wholly owned subsidiary of Quest have released a free Management Pack for System Center Operations Manager 2007 R2 which enables the monitoring of VMware virtual infrastructures.  Now, before I get into the features and capabilities of what the MP gives you, it’s important to point out that this is the first free MP to deliver these capabilities, and may stir things up a little over at both Veeam and Bridgeways, who both have established MP’s for OpsMgr to enable monitoring of VMware environments.  It’s important to say, both Veeam and Bridgeways offer trails of their solutions, so it would be important to compare the different MP’s for yourselves, however looking at a high level, one of the key elements that Veeam seems to have today, is that it’s PRO-enabled, thus provides more automated, dynamic and agile responses within the environment based on changing conditions.  That’s not to say both Bridgeways and Vizioncore won’t evolve their technologies in the future, and bring in PRO capabilities, however today, you would have to classify it as a differentiator for Veeam.  One you have to pay for however.

ScreenshotVizioncore Logo

So, what are the key features of the Vizioncore MP?

  • Essential alerts from the virtual infrastructure to reduce mean time to resolution (MTTR) of problems
  • Integration to System Center Operations Manager to centralize and consolidate monitoring efforts
  • Low cost and simple to use while allowing administrators to work in their familiar System Center Operations Manager views
  • Native management pack delivers alert and event management as well as trending inside the SCOM console
  • Agentless architecture for simple deployment and low overhead
  • Performance monitoring & availability event monitoring for fast resolution in the virtual environment
  • Out-of-the-box reports for host and guest metrics provides flexibility and clear communication between stakeholders

There’s even more features here…

What’s nice from my perspective, is the growth of the ecosystem around the Microsoft virtualisation platform, from Partners that have, in the past, been quite VMware focused.  That’s more Vizioncore than Quest, but still, it’s moving in the right direction.

If you’re interested, you can get all the info, and download the MP, from here.

Source

VMware vSphere 4.1 Released

WHAT’S NEW:

Installation and Deployment

Storage

  • Boot from SAN. vSphere 4.1 enables ESXi boot from SAN (BFN). iSCSI, FCoE, and Fibre Channel boot are supported. Refer to the Hardware Compatibility Guide for the latest list of NICs and Converged Adapters that are supported with iSCSI boot. See the iSCSI SAN Configuration Guide and the Fibre Channel SAN Configuration Guide.
  • Hardware Acceleration with vStorage APIs for Array Integration (VAAI). ESX can offload specific storage operations to compliant storage hardware. With storage hardware assistance, ESX performs these operations faster and consumes less CPU, memory, and storage fabric bandwidth. See the ESX Configuration Guide and the ESXi Configuration Guide.
  • Storage Performance Statistics. vSphere 4.1 offers enhanced visibility into storage throughput and latency of hosts and virtual machines, and aids in troubleshooting storage performance issues. NFS statistics are now available in vCenter Server performance charts, as well as esxtop. New VMDK and datastore statistics are included. All statistics are available through the vSphere SDK. See the vSphere Datacenter Administration Guide.
  • Storage I/O Control. This feature provides quality-of-service capabilities for storage I/O in the form of I/O shares and limits that are enforced across all virtual machines accessing a datastore, regardless of which host they are running on. Using Storage I/O Control, vSphere administrators can ensure that the most important virtual machines get adequate I/O resources even in times of congestion. See the vSphere Resource Management Guide.
  • iSCSI Hardware Offloads. vSphere 4.1 enables 10Gb iSCSI hardware offloads (Broadcom 57711) and 1Gb iSCSI hardware offloads (Broadcom 5709). See the ESX Configuration Guide, the ESXi Configuration Guide, and the iSCSI SAN Configuration Guide.
  • NFS Performance Enhancements. Networking performance for NFS has been optimized to improve throughput and reduce CPU usage. See the ESX Configuration Guide and the ESXi Configuration Guide.

Network

Availability

  • Windows Failover Clustering with VMware HA. Clustered Virtual Machines that utilize Windows Failover Clustering/Microsoft Cluster Service are now fully supported in conjunction with VMware HA. See Setup for Failover Clustering and Microsoft Cluster Service.
  • VMware HA Scalability Improvements. VMware HA has the same limits for virtual machines per host, hosts per cluster, and virtual machines per cluster as vSphere. See Configuration Maximums for VMware vSphere 4.1 for details about the limitations for this release.
  • VMware HA Healthcheck and Operational Status. The VMware HA dashboard in the vSphere Client provides a new detailed window called Cluster Operational Status. This window displays more information about the current VMware HA operational status, including the specific status and errors for each host in the VMware HA cluster. See the vSphere Availability Guide.
  • VMware Fault Tolerance (FT) Enhancements. vSphere 4.1 introduces an FT-specific versioning-control mechanism that allows the Primary and Secondary VMs to run on FT-compatible hosts at different but compatible patch levels. vSphere 4.1 differentiates between events that are logged for a Primary VM and those that are logged for its Secondary VM, and reports why a host might not support FT. In addition, you can disable VMware HA when FT-enabled virtual machines are deployed in a cluster, allowing for cluster maintenance operations without turning off FT. See the vSphere Availability Guide.
  • DRS Interoperability for VMware HA and Fault Tolerance (FT). FT-enabled virtual machines can take advantage of DRS functionality for load balancing and initial placement. In addition, VMware HA and DRS are tightly integrated, which allows VMware HA to restart virtual machines in more situations. See the vSphere Availability Guide.
  • Enhanced Network Logging Performance. Fault Tolerance (FT) network logging performance allows improved throughput and reduced CPU usage. In addition, you can use vmxnet3 vNICs in FT-enabled virtual machines. See the vSphere Availability Guide.
  • Concurrent VMware Data Recovery Sessions. vSphere 4.1 provides the ability to concurrently manage multiple VMware Data Recovery appliances. See the VMware Data Recovery Administration Guide.
  • vStorage APIs for Data Protection (VADP) Enhancements. VADP now offers VSS quiescing support for Windows Server 2008 and Windows Server 2008 R2 servers. This enables application-consistent backup and restore operations for Windows Server 2008 and Windows Server 2008 R2 applications.

Management

  • vCLI Enhancements. vCLI adds options for SCSI, VAAI, network, and virtual machine control, including the ability to terminate an unresponsive virtual machine. In addition, vSphere 4.1 provides controls that allow you to log vCLI activity. See the vSphere Command-Line Interface Installation and Scripting Guide and the vSphere Command-Line Interface Reference.
  • Lockdown Mode Enhancements. VMware ESXi 4.1 lockdown mode allows the administrator to tightly restrict access to the ESXi Direct Console User Interface (DCUI) and Tech Support Mode (TSM). When lockdown mode is enabled, DCUI access is restricted to the root user, while access to Tech Support Mode is completely disabled for all users. With lockdown mode enabled, access to the host for management or monitoring using CIM is possible only through vCenter Server. Direct access to the host using the vSphere Client is not permitted. See the ESXi Configuration Guide.
  • Access Virtual Machine Serial Ports Over the Network. You can redirect virtual machine serial ports over a standard network link in vSphere 4.1. This enables solutions such as third-party virtual serial port concentrators for virtual machine serial console management or monitoring. See the vSphere Virtual Machine Administration Guide.
  • vCenter Converter Hyper-V Import. vCenter Converter allows users to point to a Hyper-V machine. Converter displays the virtual machines running on the Hyper-V system, and users can select a powered-off virtual machine to import to a VMware destination. See the vCenter Converter Installation and Administration Guide.
  • Enhancements to Host Profiles. You can use Host Profiles to roll out administrator password changes in vSphere 4.1. Enhancements also include improved Cisco Nexus 1000V support and PCI device ordering configuration. See the ESX Configuration Guide and the ESXi Configuration Guide.
  • Unattended Authentication in vSphere Management Assistant (vMA). vMA 4.1 offers improved authentication capability, including integration with Active Directory and commands to configure the connection. See VMware vSphere Management Assistant.
  • Updated Deployment Environment in vSphere Management Assistant (vMA). The updated deployment environment in vMA 4.1 is fully compatible with vMA 4.0. A significant change is the transition from RHEL to CentOS. See VMware vSphere Management Assistant.
  • vCenter Orchestrator 64-bit Support. vCenter Orchestrator 4.1 provides a client and server for 64-bit installations, with an optional 32-bit client. The performance of the Orchestrator server on 64-bit installations is greatly enhanced, as compared to running the server on a 32-bit machine. See the vCenter Orchestrator Installation and Configuration Guide.
  • Improved Support for Handling Recalled Patches in vCenter Update Manager. Update Manager 4.1 immediately sends critical notifications about recalled ESX and related patches. In addition, Update Manager prevents you from installing a recalled patch that you might have already downloaded. This feature also helps you identify hosts where recalled patches might already be installed. See the vCenter Update Manager Installation and Administration Guide.
  • License Reporting Manager. The License Reporting Manager provides a centralized interface for all license keys for vSphere 4.1 products in a virtual IT infrastructure and their respective usage. You can view and generate reports on license keys and usage for different time periods with the License Reporting Manager. A historical record of the utilization per license key is maintained in the vCenter Server database. See the vSphere Datacenter Administration Guide.
  • Power Management Improvements. ESX 4.1 takes advantage of deep sleep states to further reduce power consumption during idle periods. The vSphere Client has a simple user interface that allows you to choose one of four host power management policies. In addition, you can view the history of host power consumption and power cap information on the vSphere Client Performance tab on newer platforms with integrated power meters. See the vSphere Datacenter Administration Guide.

Platform Enhancements

  • Performance and Scalability Improvements. vSphere 4.1 includes numerous enhancements that increase performance and scalability.
    • vCenter Server 4.1 can support three times more virtual machines and hosts per system, as well as more concurrent instances of the vSphere Client and a larger number of virtual machines per cluster than vCenter Server 4.0. The scalability limits of Linked Mode, vMotion, and vNetwork Distributed Switch have also increased.
    • New optimizations have been implemented for AMD-V and Intel VT-x architectures, while memory utilization efficiency has been improved still further using Memory Compression. Storage enhancements have led to significant performance improvements in NFS environments. VDI operations, virtual machine provisioning and power operations, and vMotion have enhanced performance as well.

    See Configuration Maximums for VMware vSphere 4.1.

  • Reduced Overhead Memory. vSphere 4.1 reduces the amount of overhead memory required, especially when running large virtual machines on systems with CPUs that provide hardware MMU support (AMD RVI or Intel EPT).
  • DRS Virtual Machine Host Affinity Rules. DRS provides the ability to set constraints that restrict placement of a virtual machine to a subset of hosts in a cluster. This feature is useful for enforcing host-based ISV licensing models, as well as keeping sets of virtual machines on different racks or blade systems for availability reasons. See the vSphere Resource Management Guide.
  • Memory Compression. Compressed memory is a new level of the memory hierarchy, between RAM and disk. Slower than memory, but much faster than disk, compressed memory improves the performance of virtual machines when memory is under contention, because less virtual memory is swapped to disk. See the vSphere Resource Management Guide.
  • vMotion Enhancements. In vSphere 4.1, vMotion enhancements significantly reduce the overall time for host evacuations, with support for more simultaneous virtual machine migrations and faster individual virtual machine migrations. The result is a performance improvement of up to 8x for an individual virtual machine migration, and support for four to eight simultaneous vMotion migrations per host, depending on the vMotion network adapter (1GbE or 10GbE respectively). See the vSphere Datacenter Administration Guide.
  • ESX/ESXi Active Directory Integration. Integration with Microsoft Active Directory allows seamless user authentication for ESX/ESXi. You can maintain users and groups in Active Directory for centralized user management and you can assign privileges to users or groups on ESX/ESXi hosts. In vSphere 4.1, integration with Active Directory allows you to roll out permission rules to hosts by using Host Profiles. See the ESX Configuration Guide and the ESXi Configuration Guide.
  • Configuring USB Device Passthrough from an ESX/ESXi Host to a Virtual Machine. You can configure a virtual machine to use USB devices that are connected to an ESX/ESXi host where the virtual machine is running. The connection is maintained even if you migrate the virtual machine using vMotion. See the vSphere Virtual Machine Administration Guide.
  • Improvements in Enhanced vMotion Compatibility. vSphere 4.1 includes an AMD Opteron Gen. 3 (no 3DNow!™) EVC mode that prepares clusters for vMotion compatibility with future AMD processors. EVC also provides numerous usability improvements, including the display of EVC modes for virtual machines, more timely error detection, better error messages, and the reduced need to restart virtual machines. See the vSphere Datacenter Administration Guide.

Partner Ecosystem

  • vCenter Update Manager Support for Provisioning, Patching, and Upgrading EMC’s ESX PowerPath Module. vCenter Update Manager can provision, patch, and upgrade third-party modules that you can install on ESX, such as EMC’s PowerPath multipathing software. Using the capability of Update Manager to set policies using the Baseline construct and the comprehensive Compliance Dashboard, you can simplify provisioning, patching, and upgrade of the PowerPath module at scale. See the vCenter Update Manager Installation and Administration Guide.
  • User-configurable Number of Virtual CPUs per Virtual Socket. You can configure virtual machines to have multiple virtual CPUs reside in a single virtual socket, with each virtual CPU appearing to the guest operating system as a single core. Previously, virtual machines were restricted to having only one virtual CPU per virtual socket. See the vSphere Virtual Machine Administration Guide.
  • Expanded List of Supported Processors. The list of supported processors has been expanded for ESX 4.1. To determine which processors are compatible with this release, use the Hardware Compatibility Guide. Among the supported processors is the Intel Xeon 7500 Series processor, code-named Nehalem-EX (up to 8 sockets).

You can download VMware vSphere 4.1 HERE

VMware Workstation 7.1 is available

VMWare has released VMware Workstation 7.1.

image

What’s New in VMware Workstation 7.1

  • Support for 8 virtual processors (or 8 virtual cores) and 2 TB virtual disks.
  • Support for OpenGL 2.1 for Windows Vista and Windows 7 guests.
  • Greatly improved DirectX 9.0 graphics performance for Windows Vista and Windows 7 guests. Up to 2x faster than Workstation 7.
  • Launch virtualized applications directly from the Windows 7 taskbar to create a seamless experience between applications in your virtual machines and the desktop.
  • Optimized performance for Intel’s Core i3, i5, i7 processor family for faster virtual machine encryption and decryption.
  • Support for more Host and Guest Operating Systems, including: Hosts: Windows 2008 R2, Ubuntu 10.04, RHEL 5.4, and more Guests: Fedora 12, Ubuntu 10.04, RHEL 5.4, SEL 11 SP1, and more.
  • Now includes built in Automatic Updates feature to check, download, and install VMware Workstation updates.
  • Ability to import and export Open Virtualization Format (OVF 1.0) packaged virtual machines and upload directly to VMware vSphere, the industry’s best platform for building cloud infrastructures.

    Download VMware Workstation HERE. You need a valid VMware Account to download.

    • Defrag your Virtual Machines (VMs’)

    Just like any other operating system, over time, a disk will become fragmented. Virtual machines are no different. The time that it takes for a disk to become fragmented depends on what data is being added to and removed from the virtual machine hard drive.

    Why use MyDefrag instead of the standard Windows defragger?

    • Much faster.
    • Totally automatic, extremely easy to use.
    • Optimized for daily use.
    • Disk optimization, several strategies.
    • Directories are placed together.
    • Reclaims NTFS reserved areas after disk-full.
    • Maintains free spaces for temporary files.
    • Can defragment very full harddisks.
    • Can defragment very large files.
    • Can defragment individual directories and files.
    • Can be run automatically with the Windows Scheduler.
    • Can be used from the commandline.
    • Can be used as a screen saver.
    • Can be run from cdrom or memory stick.
    • Script language, can be customized.
    • Better voor VCB, VDR, DPM & Snapshots.

    When you run MyDeFrag.exe with /verysilent it detect automatically the OS and then install x86 or x64 version from MyDefrag. It’s always installed at c:\program files. You can deploy it with MDT 2010 automatically when installing the OS. Or run it from a network share.

    You can use Group Policy Preferences to schedule it. 
    image

    Administering VMware Site Recovery Manager 4.0

    Mike Laverick heeft heeft een “nieuw” boek uitgebracht Administering VMware Site Recovery Manager 4.0.
    Hij heeft ooit eerst het eerste boek uitgebracht over VMWare SRM: Impleamenting VMware Site Recovery Manager.
    Nu heeft het boek ge herschreven voor Site Recovery Manager 4.0.

    Wat heeft hij allemaal gedaan:
    – All graphics updated to vSphere4
    – All new theme of the New York and New Jersey – Protected and Recovery Site
    – How setup replication for EMC Celerra, Clariion CX3, NetApp Filers and HP Lefthand VSA
    – Integrated with these three storage vendors  – so I cover what happens in EMC, NetApp, and HP when recovery plans are tested or run
    – Coverage of the new “Shared Site” configuration
    – Integrating PowerCLI scripts to the Recovery Plan
    – How to automate VMware SRM using the SRM SDK API
    – Updated PowerCLI chapter specific to the new vSphere4 Distributed vSwitches

    Dit boek is gratis te downloaden als PDF. Klik op het boek om het te downloaden. Je kunt het ook bestellen maar dan is het niet gratis.

    image

    Installeren van VMWare Tools op CentOS

    Login met VMWare Server Console CentOS en mount de cdrom

     image
    mkdir /mnt/cdrom
    mount /dev/cdrom /mnt/cdrom
    mount: block device /dev/cdrom is beveiligd tegen schrijven, gemount als alleen-lezen

    Mount zal de link naar de cdrom / mnt / cdrom directory.en de installatie te starten.
    cd /mnt/cdrom /
    rpm-i VMwareTools-4.0.0-219382.i386.rpm

    Voordat draait VMware Tools voor de eerste opstart moet hij geconfigureerd worden voor de kernel met het volgende commando:
    "/usr/bin/vmware-config-tools.pl"
    Om gebruik te maken van de VMXNET Driver moet je het volgende doen: ma
    /etc/init.d/network stop
    rmmod pcnet32
    rmmod vmxnet
    modprobe vmxnet
    /etc/init.d/network start

    Verwijder VMWare Tools binnen CentOS
    rpm-e VMwareTools

    VMWare View GPO settings

    Group Policy settings die je moet zetten onder Remote Desktop

    image

    VMWare View Client GPO settings
    – Enable the shade
    – Pin the shade
    – Don’t check monitor alignment on spanning
    – Color depth
    – Desktop background
    – Show contents of window while dragging
    – Menu and window animation
    – Themes
    – Cursor shadow
    – Font smoothing
    – Desktop composition
    – Audio redirection
    – Redirect drives
    – Redirect printers
    – Redirect serial ports
    – Redirect smart cards
    – Redirect clipboard
    – Redirect supported plug-and-play devices
    – Bitmap caching
    – Shadow bitmaps
    – Cache persistence active
    – Enable compression
    – Windows key combination redirection
    – Bitmap cache file size

    The VMware View ADM files can be found on the following place:

    “C:\Program Files\VMware\VMware View\Server\Extras\GroupPolicyFiles”

    – vdm_agent.adm contains properties relating to the authentication and
    environmental components of a client desktop controlled by View Agent
    -  vdm_client.adm contains properties relating to the configuration parameters of
    View Client
    – vdm_server.adm contains properties relating to View Connection Server
    – vdm_common.adm contains properties relating to all components of View Manager
    – pcoip.adm PCOIP Performance properties

    Meer hierover vindt je in VMWare View Manager Administration Guide & VMWare XP deployment Guide

    Translate »