Cupfighter.net

Recently we started evaluating Citrix Edgesight, on a enviroment we are currently building, consisting of XenApp5 2008 x64 and XenDesktop 4 Farms.

After the installation of the EdgeSight agent, suddenly a bunch of applications running within a Java Virtual machine stopped functioning. Throwing the “Could not launch the java virtual machine” error.
These Java apps tried allocating quite some memory using these java arguments (eg: XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=35 -XX:NewRatio=2″   initial-heap-size=”32m” max-heap-size=”1024m”)

After some investigation a colleague (Hugo Trippaers) found out that there was only 0,9 GB of memory allocatable on our Citrix XenApp machines using the memtest32.exe tool. While our other servers happily reported 1,5 GB of allocatable memory (Within WOW64). (Physical Machine = HP DL380G6 with 48 GB of memory, uh should be enough?)

After some deeper digging using memalloc.exe, I discover some substantial differences in memory allocation between our XenApp Servers with the edgesight agent installed and servers without the EdgeSight agent.

XenApp servers with Edgesight Agent 5.2 SP1 x64: memalloc.exe with edgesight
XenApp Servers without edgesight: memalloc.exe – without edgesight

The main difference here is all the Citrix hooks being loaded, see below.
This apparently consumes so much memory that it was not possible for java to allocate enough memory.

For more insights on WOW64 look here:  http://blogs.msdn.com/gauravseth/archive/2006/04/26/583963.aspx

By default 32bit applications within WOW64 can leverage the full 4 GB of memory availlable, which is not possible on a native 32 bit system because of the separation of kernel and user space.
Applications need to be compiled with /largaddressaware (Visual Studio : http://msdn.microsoft.com/en-us/library/wz223b1z(VS.80).aspx) or patched using editbin (http://bilbroblog.com/wow64/hidden-secrets-of-w0w64-ndash-large-address-space/), to fully use the 4 GB availlable otherwise they can only allocate 1,6 GB of memory.

We will open a case with Citrix on this; to be continued.

Citrix hooks being loaded when edgesight is installed:
Read more…

Citrix recently released a webinar by Derek Thorslund on Citrix Flash HDX, check it out here: http://www.citrix.com/tv/#video/635

I was pretty impressed when trialling Flash HDX myselfs… seeing is believing The movies below are not mine, but linked from youtube.com. It’s worth trialling yourselfs, you won’t be disappointed.

Flash HDX Demo on XenApp

Flash HDX Demo on XenDesktop 3 (vs VMWare view 3)

Download the Technology preview of Citrix HDX Mediastream for Flash here.

While checking the statistics of our blog I saw some referrals from http://community.citrix.com.
We are listed as a Citrix Community featured website! We are very happy to see this, especially because this blog is very young! The first posts are from June 2009.

We will try not to disapoint you. We have some very interesting projects comming-up which involve very mission critical XenApp and XenDesktop environments. We will post our hands-on experiences here! So stay tuned !

We have been recently looking into VDI solutions for prospects. And with the VMWorld 2008 session of Brian Madden VDI vs Terminal Services in our mind, we were at first a bit hesitant.
Especially when it comes to end-user acceptance and the remote display protocols involved. RDP, ICA / HDX, HP RGS (http://h20331.www2.hp.com/Hpsub/cache/286504-0-0-225-121.html), they all have their limitations. (Yes, we have demanding end-users:)

Since we do a lot a of VMWare and Citrix we looked at both VDI products. VMware relies for 100% on a remote display protocols but Citrix has bought Ardence which now has been rebranded into Citrix Provisioning Server.
Ardence / Citrix Provisioning Server is able to stream a full-blown OS over the network to physical and virtual machines. It actually mounts a disk over the network.

Check the video below for a very cool demo

Ardence Demo

So with Ardence all the limits of remote display protocols are gone for demanding applications.

Next to this all VDI vendors are fighting for the best remote display protocols. Microsoft bought Calista, VMWare Teradici (www.teradici.com) and Citrix is extending the ICA Virtual Channels with all kinds of nifty extensions like Flash HDX (Still techpreview) and 3D rendering using GPU’s at the server side. We did a PoC with Flash HDX which offloads flash rendering to the client and this rocks, although still beta with some quirks. Finally full quality Flash on XenDesktop and XenApp. Another nice feature of XenDesktop is that it supports smartcards from the endpoint device

What’s new in FP1 of Xendesktop 3:
http://www.citrix.com/English/ps2/products/subfeature.asp?contentID=1686118

How does the Citrix VDI solution work?

It is actually based on a bunch of existing (proven) technologies:

- Ardence OS Streaming
- Application hosting / streaming from XenApp
- ICA into a client OS (XP / Vista / Window 7), sort of single user Citrix box.

VDI into the Physical Standardized Desktop

OS Streaming on the LAN based on Citrix Provisioning Server (rebranded from Ardence). Citrix Provisioning server streams a single disk image over the LAN to multiple desktops which then are able to run a full-blown OS without the limitations of remote display protocols and leveraging local computing power. By default the streamed disk image is non persistent and the OS on the desktop will return to the initial state after a reboot. When required dedicated, read-write images can be provisioned, however this breaks the single image storage advantage.

The application are then delivered onto the desktop using (“traditional”) XenApp either streaming or hosted.

And all personal settings are stored in a traditional roaming profile, profile management however will be necessary to keep al the bloat out. This can be done using Citrix Profile manager which comes with XenDesktop or your favorite profile manager.

VDI into a virtual Infrastructure

The same happens applies when you want to run Virtual Desktops in Virtual Infrastructue like XEN, VMWare or Hyper-V (All supported by XenDesktop). Not sure when vSphere 4 will be supported. The main difference is that you’ll need to access the Virtual Desktop using ICA/HDX and all the limitations involved. But the major limitation of flash over ICA is due to be solved with Flash HDX, which rocks. You’ll need to see this for yourselves, it’s 100% like running Flash locally.

XenDesktop 3 Architecture

Check www.brianmadden.com on all the pro/cons of the different VDI solutions.