I think the intel guys themself are confused about the support of Virtualization. We can find lengthy articles on intel site about the virtualization technology, however we dont find any clear mention of Virtualization supported Motherboards and processors. These people are having ambiguity in their specifications regarding VT.
Do you have VT-D or is it VT-X ???
I have a work station built around a Xeon , X3380 which has ( VT-X ) I belive the Sec Gen I-core 7 are ( VT- D ) Which are not as good for Virtualization ??
Vt-X is the old basic virtualization. Vt-d is the new I/O virtualization (well, kind of new).
You are right but what ever you need a board that will support VT alot of boards don't ???
From what I've read intel has a BIOS problem on the new 6 series boards to support VT .
I don't really understand what you meant.
I need Vt-d support and have trouble finding hardware that supports Vt-d. Specifically I have trouble finding motherbords with Vt-d support.
Since I'm building a workstation I would prefer a desktop motherboard with Core i7, but that seems absolutelly impossible and new Xeons with motherboards are a little bit out of the desired price range (plus I still have trouble finding motherboards with Vt-d support, even for the new Xeons).
I use a Intel DQ67SWB3 board with a i7-2600.
This combination supports vt-d.
I was able to pass an Nvidia graphics card into a VM run by kvm.
The Ubuntu running in the VM loaded the driver (nouveau) but the card did not work.
Passing a Realtek based NIC did fail because the card shared an IRQ with another
This puzzled me since the graphics card used a shared IRQ too, but I got no error
message about that.
I played around with VMware ESXi 4.0.1 and it claims to support VT-d for exactly
three different PCIe devices in the world: two Broadcom and one Intel NIC.
I googled around a lot but I could not find sufficient information on how to configure
the APIC in the BIOS or in Linux to assign a dedicated IRQ line to a device.
Given that and the lack of industry support for VT-d I would not take it into
account for an production environment.
Passing the DQ67SW's USB3 controller seems to work: a USB WLAN Stick can be used in the VM to connect to my WLAN. I did no benchmarks...
Trying the same with the onboard sound leads to distorted sound from within the VM.
/proc/interrupts in the VM shows much more interrupts than on the host.
Using taskset on kvm and [irq/56-kvm] to pin them to CPU0 did not help.
A little embarrassing.