VT-d support ?
- Thread starter XZed
- Start date
J
jfroebe
Guest
You need to use the 2.6.35 kernel. The 2.6.32 kernel doesn't have the CONFIG_DMAR or CONFIG_INTR_REMAP compiled in... unless you want to recompile the 2.6.32 kernel.
Take a look at http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liaat/liaatbppcipassthru.htm for setting up the device.
Take a look at http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liaat/liaatbppcipassthru.htm for setting up the device.
Thank you very much for your answer 
!
I'm going to test v1.8 w/ 2.6.35 kernel as soon as i'll receive hardware.
http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.8
I don't get the thing about "Ubuntu-xxxxx" 2.6.35 kernel ....
Does it mean that this previous documentation can be used w/ Ubuntu ? :
http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Lenny
(Or, perhaps, it's only referring to Ubuntu as being the kernel source)
No OpenVZ on 2.6.35 ? :
http://pve.proxmox.com/wiki/Proxmox_VE_Kernel
By the way, i found this how-to :
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
Finally, relating to your how to (similar to the one i'm quoting) :
I suppose it can be considered for devices other than network ones ?
My final goal is similar to this one :
http://forum.proxmox.com/threads/3469-PCI-Passthrough-with-1068e-onboard-SAS-controller
Any users feedbacks about VT-d / Proxmox stories ?
Thank you !
!I'm going to test v1.8 w/ 2.6.35 kernel as soon as i'll receive hardware.
http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.8
I don't get the thing about "Ubuntu-xxxxx" 2.6.35 kernel ....
Does it mean that this previous documentation can be used w/ Ubuntu ? :
http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Lenny
(Or, perhaps, it's only referring to Ubuntu as being the kernel source)
No OpenVZ on 2.6.35 ? :
http://pve.proxmox.com/wiki/Proxmox_VE_Kernel
By the way, i found this how-to :
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
Finally, relating to your how to (similar to the one i'm quoting) :
I suppose it can be considered for devices other than network ones ?
My final goal is similar to this one :
http://forum.proxmox.com/threads/3469-PCI-Passthrough-with-1068e-onboard-SAS-controller
Any users feedbacks about VT-d / Proxmox stories ?
Thank you
!Hi,Thank you very much for your answer
I'm going to test v1.8 w/ 2.6.35 kernel as soon as i'll receive hardware.
http://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_1.8
I don't get the thing about "Ubuntu-xxxxx" 2.6.35 kernel ....
Does it mean that this previous documentation can be used w/ Ubuntu ? :
no this means the kernel-source is from the ubuntu-kernel. pve is debian (lenny - pve2.0 will be squeeze based).
right, if you need openvz you have to use 2.6.32, or better 2.6.18 (this is the stable kernel for openvz).
sorry, i don't use pci-passthrough. So i can't give any hints (but i love the live-migration feature and with pci-passthrough you can't use this things).By the way, i found this how-to :
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
Finally, relating to your how to (similar to the one i'm quoting) :
I suppose it can be considered for devices other than network ones ?
My final goal is similar to this one :
http://forum.proxmox.com/threads/3469-PCI-Passthrough-with-1068e-onboard-SAS-controller
Any users feedbacks about VT-d / Proxmox stories ?
Thank you
Udo
Hi,
i don't have an url. But this can't works! E.G. a vm use a pci-e card via passtrough. The OS of the VM initialize the card (perhaps load also a firmware to the card). If you now live migrate the VM, the VM-OS use the new card like the old one, but this card aren't initialize, nor loaded firmware, nor has the same register/memory-content... This can't work would i say!
Udo