VT-d now in Asus Bios

[tangoseal]

Here is a screenshot with the latest 1202 Rampage IV Extreme BIOS I just loaded not too long ago.

VT-d is now a bios tag. I am using 3930K Stepping C2 (recently received via warranty from Intel)

 

[LstBrunnenG]

First off, who's denying that C2 fixes VT-D? The problem is that motherboards might not support a feature that no chip supported at launch.

Second, I thought I read somewhere that that option will appear for C1 users as well. That it uses some microcode workaround so that the hardware redirection 'works' but it kills performance. You should try passing through a video card to a VM guest.

 

[tangoseal]

First off, who's denying that C2 fixes VT-D? The problem is that motherboards might not support a feature that no chip supported at launch.

Second, I thought I read somewhere that that option will appear for C1 users as well. That it uses some microcode workaround so that the hardware redirection 'works' but it kills performance. You should try passing through a video card to a VM guest.

Edited.. to better reflect my intended direction.

I did pass a GPU through and it worked great. However keep in mind that when pass hardware through you need to have double the hardware if you want to run HOST and VM both with fancy graphics, i.e. You cant share one GPU between a host and the VM using VT-d. But you can add a second GPU and use it in the VM. Just not one card for both at the same time. Wouldn't be able to play BF3 in your VM and at the same time play Starcraft II in your Host using the same GPU. Just a limitation.

However you can share a GPU with more than one VM apparently. I am talking windows VM. I was testing using Parallels Workstation 6. ESX-i is another beast of an OS I use for corporate testing environments. I havent tried gaming in an OS using ESXi5.

I could be wrong about the GPU in other VT-d supporting software that runs in windows however all I really know is ESX. My first time passing my 6990 through worked fine in VM but my host wouldn't even recognized the GPU as it was assigned via VT-d to the VM in Parallel Workstation. Could this possibly be just a limitation of Parallels or is it VT-d while running in a windows environment?