Monthly Archives: August 2014

Trouble with Hyper-V, Virtual Machine manager and XenClient

So in my Hyper-V enviroment all of hosts are administered by Virtual Machine Manager. The other day I needed to deploy Citrix XenClient to a hyper-v host (Since its the only hypervisor that is supported for the syncronizer part)

Now by default when installing XenClient it sets up the TomCat service running on port 443. After the XenClient installation was complete and I didn’t think much about it for the next week or so.

image

After that I needed to deploy a new virtual machine from a template to the same host, and then I started getting some strange error messages on the job status in VMM

“A Hardware Management error has occured trying to contact server”

image

Now I could either change the ports used for BITS in VMM by following the instructions here –> http://support.microsoft.com/kb/2405062 or I could change the ports of the TomCat engine by following the setup her –> http://support.citrix.com/article/CTX134691

So in my case I changed VMM To use different ports for BITS (Since I have other products that might run on 443 on a Hyper-V server.

image

After I changed the port, VM deployment worked as it should again!

Vmware products dictionary

So the last couple of days have all been about VMworld, with the keynotes being fullpacked regarding to updates and new stuff that are coming. The list is long with updates and rebranding of different products and new suites that are available. A funny story thou is that VMware releasted today a Workspace Suite (Which looks exactly like the suite that Citrix is selling, “the market guys should really learn how to use Google”)

The one thing that I find annoying with Vmware is the ability to actually describe what a product does. On their website its not common to find a good describtion of their long list of products, so I decided to make one for you instead, hopefully this comes handy for some Smilefjes

and note this is super short.

vSphere: This is VMware’s hypervisor

vCenter: This is their management software to manage vSphere servers.

vCenter Site Recovery Manager: Replication and recovery/failover to S2S

vCenter Orchestrator: Workflow and process automation software.

vCenter Log Insight: Log analysis tool

vCenter Operations Manager: Monitoring software against the virtual layer and hardware

vCenter Hyperic: Agent based monitoring software against operatingsystem and application and services.

vCenter Converter: P2V utility

vCenter Configuration Manager: Configuration and Compliance management.

NSX: Network virtualization and security platform.

vSphere Data Protection Manager: Backup software

vCloud Air:  A Hybrid Cloud solution, allows customers to extend their datacenter to VMware’s datacenters.

vCloud Director: A private cloud IaaS solution

vCloud Connector: Connects private cloud and the public cloud within a single management

vCloud Automation Center: Self-service catalog with the ability to create service templates

VSAN: Virtualised Software-defined Storage

VVOL: The ability to move much of the managmeent capabilities frmo the SAN to the VM level

vRealize Air Automation: The ability to provision and manage infrastructure and services across public/private clouds

Horizon: End user platform to deliver VDI/RDS solutions.

Now VMware has also created some new bundles.

Workspace Suite: Contains Horizon, AirWatch and WorkSpace Portal

EVO RAIL:  A Prebuilt architecture which is going to be prebundled from specific OEM vendors. Which contains vSphere, vCenter, VSAN, Log insight.

Getting started with RemoteFX vGPU on Windows Server 2012 R2

Now Microsoft has made alot of improvements with the latest RemoteFX feature in 2012 R2, (Now i’ve written a bit of the requirements of remoteFX before –> http://msandbu.wordpress.com/2014/05/18/remotefx-and-vgpu-2012r2-requirements/)

Most important thing to remember about remoteFX vGPU is that it is only supported on Enterprise Client OS (Therefore Windows 7 and 8 Enterprise SKUes)

It also requires Hyper-V 2012 / 2012 R2 installed with Remote Desktop Virtualization Host role installed.

It also requires a graphics card, http://blogs.msdn.com/b/rds/archive/2013/11/05/gpu-requirements-for-remotefx-on-windows-server-2012-r2.aspx

In my case I have Dell R720 with S7000 Firepro card. Now you need to install the FirePro drivers for 2012 R2 on the host.

After that you need to check for enabled the GPU to be used for RemoteFX. image

After that you need to have a virtual machine installed with Windows 7/8 enterprise Generation 1, and you need to attach a RemoteFX adapter to it. NOTE if you are running Windows 7 you need to update integration services!

image

Note that the number of monitors and resolution define how much video memory is dediated to the virtual machine. You can see the vRAM allocation overview here –> http://blogs.msdn.com/b/rds/archive/2013/12/04/remotefx-vgpu-improvements-in-windows-server-2012-r2.aspx

Now when you have configured a virtual machine with RemoteFX you can boot it and RDP to it.

To be sure that you are using RemoteFX you can look at the following.

DXDIAG:

 image

Device Manager:

image

Now to have optimal performance you need make sure that TCP/UDP 3389 is open, since RemoteFX uses UDP for most of the graphic transport. Now remember thet vGPU only supports DirectX acceleration (not OpenGL)

there are custom performance counters within the virtual machine to monitor, if for instance network is the issue/ performance locally or something else.

image

Now Microsoft states that RemoteFX is now supported on WAN and yeah it does work, but not at the same performance that Citrix or VMware has at the moment. ill come back with some more detailed tests on remoteFX vGPU comparted to 3D vGPU HDX later.