Bug 1041093

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/hyper-v-remotefx.

Description:

OpenStack VDI support can be largely improved by enabling the Hyper-V RemoteFX features in the Nova Hyper-V driver.

RDVH must be enabled on the host* and one or more physical GPU with RemoteFX support need to be available.

*On Hyper-V server enable RDVH with: Add-WindowsFeature –Name RDS-Virtualization

RemoteFX Nova feature description
============================

RemoteFX, at the current state, allows a guest VM to access the hypervisor's GPU features for 3D graphical acceleration.

Guest configuration is performed by specifying the number of virtual desktops to be used by the VM and the maximum resolution, with a given set of predefined values:

"1024x768"
"1280x1024"
"1600x1200"
"1920x1200"
"2560x1600"

The hypervisor available resources include mainly the total video memory provided by the combined video adapters configured for RemoteFX.

This information is provided by a compute driver as part of it's host stats and available resources along with the total and available cpu cores, memory, disk space, etc.

Each VM consumes an amount of video memory which can be calculated as:

mem = 64*horizontal_res*vertical_res*monitor_count
e.g.: 64*1280*1024*2 = 167772160 bytes

A given image can specify the RemoteFX requirements by providing values for the following custom properties:

remotefx_max_resolution
remotefx_monitor_count

e.g:

glance image-create --property hypervisor_type=hyperv --property remotefx_max_resolution=1280x1024 --property remotefx_monitor_count=2  --name RemoteFX1 --container-format bare --disk-format vhd < image.vhd

This way, the scheduler can easily determine with an ad hoc filter which hosts are suitable for a an image requirements, given the host's available video memory and image requirements.

Beside spawning, the scheduler supports live and cold migration as well by applying the same filter. 


Specification URL (additional information):

None