Friday, February 27, 2015

LSI Logic SAS vs VMware Paravirtual SCSI disk

Within virtual machines, there are different SCSI controllers available for writing the data to the actual disk. For the different operating systems, there are best practices which gives the best performance. Windows XP uses the BusLogic Parallel SCSI driver and the results are acceptable. With Windows 7 the commonly used controller is the LSI Logic SAS controller. Which is selected automatically when creating a virtual machine of this type.

Different vendors have different best practices, some of them advice to use the VMware Paravirtual SCSI controller. The VMware Paravirtual SCSI controller needs to be selected manually and needs some additional actions before it can be used. Creating a small additional disk with VMware

Paravirtual SCSI controller connected will force the OS the use and installation of the correct driver. The additional drive can be removed after installation and the initial drive must be connected to the VMware Paravirtual SCSI controller.

The question is which of these controllers gives the highest performance. For that I have started some tests with IOmeter in a virtual Windows 7 machine. The first test was with the VMware Paravirtual SCSI controller and using an additional disk beside the system disk. The results of the test is show below:

Test1

The second test was performed with the LSI Logic SAS controller and was using the additional diks.
This configuration could not give the same performance as the VMware Paravirtual SCSI controller, the results of this test are placed below

Test2

The other test we did was with the system disk instead of the additional disk. The same results are showed as the previous tests. The use of the VMware Paravirtual SCSI controller performs a little better then the LSI Logic SAS SCSI controller.

The results of above are within the virtual machine, with Xangati i was able to measure from the outside. The following picture will show the light better performance of the VMware Paravirtual SCSI controller, where the first and last test includes the VMware Paravirtual SCSI driver:

Xangati
For now, the conclusion can be drawn that the use of the VMware Paravirtual SCSI controller lead them a slight performance gain in these test.

VMware Remote Console 7.0 Released

VMware Remote Console (VMRC) is a standalone Windows application that provides console access and client device connection to virtual machines on a remote host.  You need to download this installer before you can launch the external application directly from a vSphere Web Client.
In the VMware Remote Console Windows application, you will have access to:
  • Mouse and keyboard functionality in the VM
  • Send Ctrl + Alt + Delete
  • Full screen mode
  • VM power operations
  • Client-side device connection such as CD-ROM, USB, and Floppy (requires administrator access)

Internationalization

VMware Remote Console 7.0 is available in the following languages:
  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese
  • Traditional Chinese
  • Russian
  • Italian
  • Spanish
  • Portugal
  • Nederlands
Download at source

Atlantis USX 2.2 Released

Atlantis USX is a software solution that accelerates performance and consolidates storage, increasing effective storage capacity to support running server workloads such as business-critical applications. USX builds on proven Atlantis compression, caching, deduplication, and tiering capabilities to provide a dramatically reduced storage footprint and improved performance, including built-in high availability. USX satisfies the storage requirements demanded by server workloads, removing the constraints of traditional storage.
With the new release the following new features came available.
  • XenServer – USX now supports Citrix XenServer. XenServer can use any of the USX volume types. USX configuration, deployment, and management is the same for all platforms.
  • New volume types:
    • The Hyper-Converged volume type supports server or VDI workloads and consumes only
      local resources. Hyper-Converged volumes are associated with an Infrastructure volume that
      provides shared storage so that the Hyper-Converged volume can migrate before entering
      maintenance mode even though the Hyper-Converged volume uses only local resources.
    • The Simple All Flash volume type supports persistent VDI deployments and enables you to
      use flash for both performance and capacity.
  • Maintenance mode – A host can be placed into maintenance mode from the new Hypervisors Management screen in the USX GUI.
  • Volume power operations and reboots can be performed from the Manage Volumes screen.
  • LDAP authentication – Use the new LDAP Authentication screen to bind to an LDAP server so that members of a specified LDAP group can log into USX.
  • Tree hierarchies are implemented for the display of datacenters, clusters, and hypervisors.
  • SNMP configuration – A new document, Atlantis USX SNMP Configuration, provides a listing of the USX MIB and information about configuring USX to communicate with an SNMP trap host.
Atlantis USX 2.2 is now available in the download portal

Wednesday, April 16, 2014

Multiple Sessions in VMware Horizon View

When connecting to a floating pool using the View client, a user ended up receiving a new session despite having an existing session on another VM.

Analysis showed two desktop launch requests that came in from the same client connection in quick succession, spaced two seconds apart. Client log files imply the most likely scenario is that the user requested the desktop, immediately hit cancel on the wait dialog after the request was dispatched, and then launched it a second time. The View Connection Server correctly identified an existing disconnected session for the user while processing the first request at 13:18:57 for example, and provided the client with details to reconnect. The client dropped the Connection Server's response and sent a second request at 13:18:59. This in turn was routed to the same VM, but the request was rejected as the first connection was still being set up by the View Agent. At this point the Connection Server then fell back to providing the user with a new session as the original was unavailable.

Solution:
View 5.1.1 and onwards contains a hidden configuration option that will inform the Connection Server to not fall back and allocate a new session if it knows the user already has one, even if reconnecting to the session failed. In the specific case analyzed, if this was toggled the user would have received a connection error on the second launch request with the option to retry. Retrying a few seconds later would have succeeded.

VMware recommends that the option to disable the default fallback behaviour is enabled. Instructions for this are below:
  • Ensure connection servers are running 5.1.1 or later
  • Follow the steps to connect to the ADAM database at http://kb.vmware.com/kb/2012377
  • Navigate to the object CN=Common,OU=Global,OU=Properties,DC=vdi,DC=vmware,DC=int
  • In the Attribute Editor for the object, edit pae-NameValuePair attribute
  • Making sure not to adjust any other values, add a new string to the attribute with value "cs-allowfallbackfromexistingsession=0" (no quotes)
  • Click OK to close the editor dialog, your change is applied with no need to restart the servers
  • To reverse the change, edit the attribute again and remove the above line
Verification:
To verify the fix has been applied, you may find the allowFallback value in a debug level line on any desktop launch. The line will have the following format:
 
  DEBUG getSessionForApplication, userDn: , appMap: {=, [...], allowFallback=false, [...]}

Wednesday, May 29, 2013

How to use VMware Horizon View Multi VLan

With the release of VMware Horizon View 5.2, the functionality made ​​available that allow to create an automated pool where multiple VLANs to be linked. The administrator can use multiple network labels to a linked-clone virtual machine or an automated pool containing full virtual machines. Multi VLAN configuration is performed with PowerCLI from the View Connection Server. Functions are used from the PowerCLI for vSphere, so these need to be installed to.

Before a virtual machine as a golden image can be used within a multi-VLAN configuration. The hardware version of the virtual machine to version 9 be amended. Within hardware version 9, the functionality is present which is required for the use of the functionality.

There are different steps to create the the automated pool. The first step is exporting the availabele VLans for the golden image. The exported file needs to be configured and will be used for creating the Horizon View Pool.

Export Configuration
To create an export of the used VLans of the golden image, the following command is used for the export of the golden image configuration. When exporting the settings for a full cloned virtual machines, the command Export NetworkLabelSpecForLinkedClone need to be replaced with Export-NetworkLabelSpecForFullClone:

Export-NetworkLabelSpecForLinkedClone `
-vc_id "
7d87df91-bf73-47b3-b01a-f54214e6ff61" `
-clusterPath "
/myresourcepool/host/Cluster1/" `
-parentVMPath "
/myresourcepool/vm/Win7-Parent" `
-parentSnapshotPath "
/Win7-Parent/snapshot" `
-maxVMsPerNetworkLabel 
5 `
-networkLabelConfigFile "
C:/Win7.txt
"

The vc_id identifies the vCenter Server. To obtain the vCenter ID, the following command can be used:

Get-ViewVC | select vc_id

The following output is displayed

vc_id
-----
7d87df91-bf73-47b3-b01a-f54214e6ff61
c0ed93c8-c5b5-42d1-aeed-99764921d29c

Edit Export file
The exported file needs to be edited before used for creating the View Pool.

#Network Label Configuration Spec
#WARNING! Setting enabled flag to false will
#turn off the automatic network label assignment
#for newly provisioned desktops.
enabled=true
#Parameter Definition for NIC
nic1=Network adapter 1
#Parameter Definition for Network
network01=vlan10
network02=vlan20
network03=vlan30
#Network Label Attribute Definition
#Expected format:
#..maxvm=
nic1.network01.maxvm=5
####nic1.network02.maxvm=5
nic1.network03.maxvm=5

Within the configuration file, the different VLans availabele for the golden images are shown. A VLan can be selected by removing the #### before the line.  In the above example, the used VLans are set network01 and network03, the maximum used IPs witin the VLan is maximized to 5.

Create View Pool
The exported configration file from the previous step will be used for the creation of the Horizon  View pool. The following command can be used:

Add-AutomaticLinkedClonePool -Pool_id -displayName "" -NamePrefix "-{n:fixed=3}" -Vc_id 7d87df91-bf73-47b3-b01a-f54214e6ff61 -Persistence NonPersistent -VmFolderPath "/myresourcepool/vm/" -ResourcePoolPath "/myresourcepool/vm" -ParentVmPath "/myresourcepool/vm/Win7-Parent" -ParentSnapshotPath "/Win7-Parent/snapshot" -DatastoreSpecs "[Moderate,OS,data]/myresourcepool/host/VMFS01” -Composer_ad_id 12232fbf-1dbd-42e5-84dd-f18848e5bcf5 -UseUserDataDisk $false -UseTempDisk $true -MinimumCount 1 -MaximumCount 5 -HeadroomCount 2 -PowerPolicy AlwaysOn -SuspendProvisioningOnError $true -NetworkLabelConfigFile "C:/Win7.txt"

The composer_ad_id parameter specifies the ID of the View Composer domain. To obtain the Composer id the following command can be used:

Get-ComposerDomain | select composer_ad_id

The following output is displayed
composer_ad_id
--------------
12232fbf-1dbd-42e5-84dd-f18848e5bcf5
a7e97ac8-1c61-4a41-8bd6-666a7e2eda17


The Horizon View pool is created and will start provisioing the linked clones. Additional configuraton steps can be made after creation of the pool.

Tuesday, March 5, 2013

What’s New in VMware Horizon View 5.2

VMware Horizon View 5.2 delivers valuable enhancements to end user experience and ease of management, while further driving down the total cost of ownership for VDI.

What's New with End User Experience

  • Support for Windows 8 based desktops
  • Hardware Accelerated 3D Graphics
  • Improved video and VOIP communications with Microsoft Lync 2013 support
  • Streamlined access to View Desktops from Horizon
  • Easily connect to desktops from any device with HTML Access
  • Enhanced productivity from mobile devices with new 'Unity Touch' functionality

What's New with Ease of Management

  • Large pool creation with elimination of 8 host limits, and multiple vLAN support
  • View Administrator performance improvements with large numbers of desktops
  • Accelerated provisioning and recompose operations.
  • Tech Preview of a new Integrated Service Console in the vSphere Web Client
  • Support for vCenter Server Virtual Appliance based deployments

Saturday, February 9, 2013

Removing vCenter Extensions


Many different products that provide additional functionality within a vSphere environment, use the registration method within the vCenter Server. These so-called vCenter Extension used for integration. This may sometimes happen that a new installation of the product must be carried out where the vCenter Extension not properly removed. These vCenter Extensions can also be manually removed.

To remove a vCenter Extensions, go to the URL:

https:// //mob/?moid=ExtensionManager

Here, an overview is given of the present Extensions.




Select the Extension that needs to be removed and select Unregister Extension.



In the opened window, the name of the Extension need to be filed. For example com.vmware.vShieldManager to remove the Extension of the vShield Manager software. Then select the option Invoke Method to the registration within the vCenter Extension Services to remove the Extension.