The main difference between all those solutions is the same reason as why there are so many car companies - it is a big market and everyone thinks they can do it better.
As for your comparison points, everyone will give different answers. Typically, if you just want to mess around and know what you are doing, I would recommend Virtual Box. If you want to do more advanced things, I would recommend VMWare Workstation, if you do not know what you are doing, but just want to virtualise, I would recommend Microsoft Virtual PC.
Qemu is not virtualisation, it is emulation. this means it is slower, but it has its moments and its niche that other products do not fit in to.
As for your direct points:
Virtualization
The process of running a machine virtually, this is the general name of the topic.
Virtual Machine
A name for a single machine that runs virtually on a host.
Hypervisor
A hypervisor is a virtualisation technology which allows for the greatest performance by attempting to run as thin as possible on top of the bare metal hardware.
Paravirtualization
This term is very awkward and is subjective to different people. Typically, most modern virtualisation technology, even those that use a Hypervisor also use paravirtualisation for a few hardware components (e.g. networking controller.). My definition (which I am happy to be corrected on) is presenting virtual hardware which is different to the physical hardware it is actually connected to.
Hardware Virtualization
(typically) Support for virtualisation is built in to the processor directly which increases the performance. For example, in the early days of virtualisation, it was performed via emulation which has extra overhead. Hardware virtualisation is basically a bunch of "shortcuts" inside the processor that allow virtual machines to run a lot faster - in some cases, almost at the same speed as a native machine.
I hope this helps!
Article mentioned for PCI-passthrough, the Kernel config is required
make menuconfig
set "Bus options (PCI etc.)" -> "Support for DMA Remapping Devices" to "*"
set "Bus options (PCI etc.)" -> "Enable DMA Remapping Devices" to "*"
set "Bus options (PCI etc.)" -> "PCI Stub driver" to "*"
optional setting:
set "Bus options (PCI etc.)" -> "Support for Interrupt Remapping" to "*"
However, I could not find these options under "Bus options" and instead for it under "Device Drivers --> IOMMU Hardware Support".
After following the article mentioned, I still had issues boot up the guest machine and getting errors that "Device 'pci-assign' could not be initialized". I managed to get it boot by executing:
echo 1 > /sys/module/kvm/parameters/allow_unsafe_assigned_interrupts
Refer to the following article if you're still having issues: http://spica-and-roid.blogspot.com.au/2012/07/howto-kvm-passthrough.html
Best Answer
Hardware acceleration (accelerated performance mode), as the name suggests requires hardware assistance from the CPU (see Intel VT, not sure what AMD's equivalent is).
Within your Debian VM it's only aware the instruction sets provided by the virtual CPU (vCPU) opposed to the physical core so the accelerated mode isn't available.
Basically avoid nested virtualisation if you need the performance.
Why not just develop on the Windows 10 host? If you need a Linux environment try using the Windows subsystem for Linux functionality. That'd allow you to install Ubuntu and then the Android development suite within that. Suspect that'd provide a better experience.