Hyper-V in Windows Guest Under Proxmox

I need to provision a server for RemoteApp [part of Remote Desktop Services under Windows Server 2008]

My issue is that during the installation of the Remote Desktop Services feature, in order to install RemoteApp support, Hyper-V must be installed. Sounds easy, except the Hyper-V installation fails on the CPU check. The error is that the CPU does not support Virtualisation or it is turned off in the BIOS.

I have implemented the args: -cpu host flag in the /etc/qemu-server/<VMID>.conf file, however this does not fix it.

Does anyone have any experience or suggestion as to how I may be able to acomplish this?

Any help would be appreciated at this point as I am at a loss.

proxmox1:/etc/qemu-server# pveversion -v
pve-manager: 1.8-15 (pve-manager/1.8/5754)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-32
pve-kernel-2.6.32-4-pve: 2.6.32-32
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-11
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-2
ksm-control-daemon: 1.0-5


Matthew

No, the CPU here is a Core i7 960

Does this mean there is no way to acomplish this?

I have had some success.

For those interested, you can run the following commands from an elevated command prompt

Dism /online /enable-feature /featurename:Microsoft-Hyper-V
Dism /online /enable-feature /featurename:Microsoft-Hyper-V-Management-Clients

This installs the Hyer-V roles without the CPU check. I do not believe that it removes the VT requirements, but in my case, the Core i7 has VT and Hyper-V is working. It is also worth noting that I have removed the args: -cpu host flag from the /etc/qemu-server/<VMID>.conf file and it still works.

I can now confirm that I have installed and configured RemoteAPP on my Guest Windows Server 2008 R2 machine and it does appear to be working perfectly.

I can only assume this means that the Hyper-V install really does not need the VT support in order to use RemoteAPP. I have not gone as far as installing a Guest in Hyper-V, nor would I particularly want to. [I have proxmox for that ] This project was only to get RemoteAPP up and running, in this I appear to have succeeded. [touch wood]

Perhaps if anyone has anyone has a better understanding of what Hyper-V does under RemoteAPP they may be able to shed some light on why this works without Nested KVM for the sake of having the information in this thread.

That is different again. RemoteAPP is for running an application on a users desktop, when the application is setup on a terminal server. Basically Terminal Services without the rest of the servers desktop [Citrix XenApp's poorer cousin]

That app allows you to run an application hosted within a Hyper-V VM on a desktop machine without the rest of the Hyper-v VM machines desktop. Interesting, I did not know that exisited, but it owuld not have helped me here, I had to set up the Terminal Server to host the application. I am not actually running a Hyper-V VM.

Thanks for the info though. Never know when something like that might come in handy.

Matthew