Revision history [back]

Hello,

Make sure you have enabled the RemoteFX feature on your compute nodes, by setting this config flag in the nova.conf file:

[hyperv]
enable_remotefx = True

Also, make sure you install the RemoteFX feature on your compute nodes:

Install-WindowsFeature RDS-Virtualization

Also, you have to make sure that your hosts are capable of the RemoteFX feature. Some of the requirements are:

• SLAT-enabled processor (Intel: Extended Page Tables (EPT), AMD: Nested Page Tables (NPT)).
• it must support DirectX 11.0 or newer.
• it must support WDDM 1.2 or newer.

Also, you have to make sure that your guests support RemoteFX. For a Windows guest, you can easily check this by looking at its Device Manager > Display Adapters, it should be something like: Microsoft RemoteFX Graphics Device - WDDM.

Finally, we've added support for RemoteFX in Windows / Hyper-V Server 2016, which comes with new features. Some of the new features for RemoteFX in Windows / Hyper-V Server 2016 are:

• 4K resolution option
• 1GB dedicated VRAM (availble choices: 64MB, 128MB, 256MB, 512MB, 1GB) and up to another 1GB shared VRAM
• Support for Generation 2 VMs
• OpenGL and OpenCL API support
• H.264/AVC codec investment
• Improved performance

In order to request a certain VRAM memory amount for your instance, you can create a flavor like this:

# format: resolution,number_of_monitors,vram_amount_in_mb
nova flavor-create m1.remotefx 111 4096 20 2 nova flavor-key 11 set hyperv:remotefx="1920x1200,1,1024"

Best regards,

Claudiu Belu