Now Available:

Featured Resource:

line

Newsletter

Email Address:


line

Ask the Expert

Have a question for our resident expert? Email your questions to Greg.

« BREAKING: Microsoft NNTP Tech Support Forums to be Replaced by Web-based Forums | Main | Virtuozzo - O/S Virtualization Beats Entire System Virtualization? »

A Short Guide to Virtualizing Citrix on VMware ESX 3

I found this post recently on Brian Madden's web site discussing some very specific steps to tune your ESX server for hosting Citrix servers. Now, I personally don't often recommend the virtualization of Citrix or Terminal Servers for performance reasons, but for disaster and rapid recovery purposes, I think its always a good idea to have one instance residing on your ESX infrastructure. Doubly so if you're replicating those VM's over to a remote site for DR.

Some of the interesting and very specific recommendations I saw in this piece are...

sched.mem.pshare.enable

Enables memory sharing for a selected virtual machine. This boolean value defaults to True. If you set it to False for a virtual machine, memory sharing is turned off. This can be a way to switch off memory sharing without modifying the host ESX.

das.defaultfailoverhost

If this is set, VMware HA will first try to fail over Virtual Machines to the host specified by this option. This is useful if you want to utilize one host as a spare failover host. It is not usually recommended, however, because VMware HA tries to utilize all available spare capacity among all hosts in the cluster. If the specified host does not have enough spare capacity, VMware HA tries to fail over the virtual machine to any other host in the cluster that has enough capacity.

This is useful in case you modify the ESX Host settings on some of your ESX Hosts and want to make sure your Terminal and Citrix Servers failover to the desired and configured host.

sched.cpu.htsharing

Any (default) – The virtual CPUs of this virtual machine can freely share cores with other virtual CPUs of this or other virtual machines.
None – The virtual CPUs of this virtual machine have exclusive use of a processor core whenever they are scheduled to it. The other hyperthread of the core is halted while this virtual machine is using the core.
Internal – On a virtual machine with exactly two virtual processors, the two virtual processors are allowed to share one physical core (at the discretion of the ESX Server scheduler), but this virtual machine never shares a core with any other virtual.

Check out the full piece on Madden's site at:
http://www.brianmadden.com/content/article/A-short-guide-to-virtualizing-Presentation-and-Terminal-servers-on-VMware-ESX-3

TrackBack

TrackBack URL for this entry:
http://www.realtime-windowsserver.com/type/mt-tb.cgi/392

Post a comment

(All comments are approved by site leader before appearing here. Thanks for commenting!)

line

Greg Shields' Bio:

Greg Shields, is an independent author, instructor, and IT consultant based in Denver, Colorado, and a co-founder of Concentrated Technology. With nearly 15 years of experience in information technology, Greg has developed extensive experience in systems administration, engineering, and architecture specializing in Microsoft systems management, remote application, and virtualization technologies. Greg is a Contributing Editor for Redmond Magazine, MCPmag.com, and Virtualization Review Magazine and is the author of five books, including Windows Server 2008:  What’s New / What’s Changed. Greg is also a highly sought-after instructor and speaker, speaking regularly at conferences like TechMentor Events, and producing computer-based training curriculum for CBT Nuggets.  Greg is a recipient of Microsoft "Most Valuable Professional" award with a specialization in Windows Terminal Services.