No, hyperthreading is different from VT. VT enables the hardware virtualization capability of a CPU. That is required to run type-1 hypervisors like Hyper-V or ESXi. There is special Virtualization Technology (hence, VT) on some CPUs that allow type-1
hypervisors better access to the hardware, allowing many hypervisor functions to be performed directly to the hardware. Type-2 hypervisors like VMware Workstation run as a service or application on top of an operating system and pass all hardware requests
to its underlying operating system. They do not exploit, nor require, the capabilities of VT.
Hyperthreading is a 'trick' used by the chip vendors to create an extra execution 'thread' on a single core. As Brian said, it does not double the capabilities of the core because it is actually sharing a lot of individual components that can only
perform one function at a time. But, it can do things like instruction setup. So while the core is executing an instruction that it already set up, the hyperthread can be setting up another instruction. But there is only a single place on
the core that can execute the instruction, so it has to wait for the currently executing instruction to complete. You will hear a wide range of how much performance benefit you can potentially see from hyperthreading, but it is generally well south of
25%. And some applications do not run very well at all if they are run in a hyperthreaded environment. Therefore, you will sometimes find recommendation to disable hyperthreading, but you still have VT enabled.
Hyperthreading will show double the logical processors. VT does not change the number of logical proce