Search results

You'll have to provide more info if you want some feedback. I don't know the Lenovo hardware and if this system really supports vt-d. At least provide output of: $dmesg | grep -e DMAR -e IOMMU $lspci -vv #(only the part of the device which you want to passthrough) $lspci -vv | grep IRQ

If you don't want to wait, why don't you build the necessary packages on your own? Just install latest proxmox as guest os so that you can build the git packages without touching your running machine. You can use the DEV Readme as general guide.

Just a short update to my comment on using "pcie_acs_override" patch. After upgrading to latest git kernel pve-kernel-3.10.0-3-pve_3.10.0-11_amd64 I don't need pcie_acs_override anymore. My pci devices are now split into separate iommu_groups without any hickups.

Did you read the trouble shooting thread? That's not only about login issues, but also ssl issues! Just read the thread and create the proper ssl linking. After that your ssl issues should be gone.

Just an idea... Do you have an adaptec raid controller? Did you install the storage manager package? If yes, please have a look at the trouble shooting at https://pve.proxmox.com/wiki/Adaptec_maxView_Storage_Manager. At least I had SSL related issues with this combination in the past. As I said...

Proxmox 3.2 didn't introduce any changes to pci passthrough (thus the wiki is still valid). You should also use the search function of this forum if you need further input on how to passthrough pci devices. I would recommend to start testing with stock kernel first. If this works, you can start...

Your question is answered here: http://forum.proxmox.com/threads/17495-Issues-with-iommu-with-3-10-kernel-in-pvetest-repo

I know, this is kind of a monologue, but maybe this is helpful if someone else stumbles over the same issue. While doing some research I found a patch which adds a quirk in regards to PCIe ACS (kernel mailing list). This patch actually does resolve my issue, that all pci devices are in only one...

Now I've tried a step by step procedure for vfio-pci. # lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18) 00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 18) 00:02.0 VGA compatible controller: Intel Corporation Core...

That's what's happening when I start a vm with vfio-pci (network goes down): /var/log/messages: Feb 19 21:14:37 proxmox kernel: [ 203.280664] VFIO - User Level meta-driver version: 0.3 Feb 19 21:14:37 proxmox kernel: [ 203.284198] ------------[ cut here ]------------ Feb 19 21:14:37 proxmox...

Now I've upgraded to proxmox 3.2 beta and kernel 3.10. I get the same error msg as reported by tenyosensei. In my case I think that this is related to the new kvm module which does not support the previous option "kvm allow_unsafe_assigned_interrupts=1". I'm wondering why this option was...

I just checked my pve-no-subscription installation for updates and was wondering why there are so many new packages. E.g. new QEMU 1.7 seems to be already in pve-no-subscription repo. I thought the new packages were only available if pvetest repo is available!? # apt-cache policy pve-qemu-kvm...

I'm wondering why IOMMU makes trouble with kernel 3.10. That would be a regression for pci-assign. But it's good to see some progress on vfio-pci. Now there's another patch for vfio-pci integration that should make it usable (devel mailing list). Not sure if it will make it into proxmox 3.2...