Well, it took some tinkering on my part (think learning on the job so to speak) but I got Hypervisor working on my ThinkPad.
Hyper-V is the software piece of Intel VT:
http://ark.intel.com/Products/VirtualizationTechnology
This is built in hardware VM technology on a wide range of Intel CPUs. The AMD version is AMD-V but it is nowhere near as stable or fast as VT. Basically it gives the virtual machine direct hardware access as opposed to the other way Virtual Machines work, which is emulation.
Now there are other software packages that are VT based (like Parallels). It is why they achieve much better performance than non VT virtualization solutions.
So far I have been playing with Hyper-V Manager and trying to setup and configure a straight Unix distribution into a VM. One I have it in I plan to put the KDE UI on it and see where it goes.
Hyper-V is the software piece of Intel VT:
http://ark.intel.com/Products/VirtualizationTechnology
This is built in hardware VM technology on a wide range of Intel CPUs. The AMD version is AMD-V but it is nowhere near as stable or fast as VT. Basically it gives the virtual machine direct hardware access as opposed to the other way Virtual Machines work, which is emulation.
Now there are other software packages that are VT based (like Parallels). It is why they achieve much better performance than non VT virtualization solutions.
So far I have been playing with Hyper-V Manager and trying to setup and configure a straight Unix distribution into a VM. One I have it in I plan to put the KDE UI on it and see where it goes.
I like the fact that it has hardware access, and in Linux the virtualization platform KVM does the same thing only in a very stripped down fashion (still has access to hardware). VMware has limited access (like the graphics cards), but there is still a layer. A great exercise is virtualizing an existing physical machine.