Check again - by now it has a (kinda positive) "Not sure how to do it and if it makes sense to do that in the same driver, but we'd be open for discussions" reply.
Hyper-V is extremely strict about what can access its hypercalls, so you can't do anything from userspace like with KVM and HAX. Hypercalls can only be made from ring 0 and creating domains can only be done from the root domain.
That doesn't help the project at all...
HLE seems to be more workable for Xbox...
Xenia is VERY far for the Xbox 360, it isn't technical but organisational issues instead
Yes, exactly. All of KVM, HAXM and the OSX Hypervisor.Framework are basically providing APIs to user applications that encapsulate the CPU's virtualization capability so that you can use it to implement VMs without needing kernel privilege. They differ in how high a level of abstraction they provide (eg KVM does a lot more for you in the kernel, H.f punts to userspace for everything), but the principle is the same.
It's on my backlog of experiments that I'll probably never get to, but has anyone had success running QEMU on, say, AWS (virtualized) Windows servers to run Linux VMs? I presume HAXM isn't relevant for attempting this?
HAXM started off as a part of the Android SDK for Windows but is now a standalone component as its wider applicability has been noted and capitalized upon.
Now that will be a fun pull request to watch.