Well after editing back and forth, I digress back to my original post. The problem is somewhat a chipset issue but it's more that ASUS and many others don't Enable the VT-d/VT-x on their boards.
@IntelEnthusiast provided me this link ->
http://www.intel.com/support/motherboards/desktop/sb/CS-030922.htm?wapkw=%28support+for+Virtualization+on+desktop+board%29
Bottom-Line, you'll need to verify VT-d/VT-x support of: 1. VirtualBox requirements, 2. CPU Compliance and 3. MOBO Compliance -- there's no master list. The ASUS P8B WS supports VT-d, and the i7-2600 supports both VT-x/VT-d ->
http://ark.intel.com/products/52213 IMO I would do this using Xeon and Server grade MOBO.
VirtualBox
http://www.virtualbox.org/manual/ch01.html
"No hardware virtualization required. For many scenarios, VirtualBox does not require the processor features built into newer hardware like Intel VT-x or AMD-V. As opposed to many other virtualization solutions, you can therefore use VirtualBox even on older hardware where these features are not present. The technical details are explained in the section called “Hardware vs. software virtualization”."
http://www.virtualbox.org/manual/ch10.html#hwvirt
"Even though VirtualBox does not always require hardware virtualization, enabling it is required in the following scenarios:
* Certain rare guest operating systems like OS/2 make use of very esoteric processor instructions that are not supported with our software virtualization. For virtual machines that are configured to contain such an operating system, hardware virtualization is enabled automatically.
*
VirtualBox's 64-bit guest support (added with version 2.0) and multiprocessing (SMP, added with version 3.0) both require hardware virtualization to be enabled. (This is not much of a limitation since the vast majority of today's 64-bit and multicore CPUs ship with hardware virtualization anyway; the exceptions to this rule are e.g. older Intel Celeron and AMD Opteron CPUs.)"