PCIe passthrough does not work

Just to mention again, it works perfectly under ubuntu or arch.

Sure but my Proxmox server runs heaps of KVM and LXCs and I would rather not move OS, simply because proxmox bug causes this issue.
 
Hi,
which kernel and qemu version ?

(proxmox 4.0 use ubuntu willy kernel + qemu 2.4)

So are you using the proxmox environment on top of ubuntu to get it to work? - I might have to do that as I need this working ASAP. Before I do this, any viable alternative that is stable?
 
Last edited:
So are you using the proxmox environment on top of ubuntu to get it to work? - I might have to do that as I need this working ASAP. Before I do this, any viable alternative that is stable?

No, as I mentioned in the first post I try to switch from ubuntu server to proxmox. The proxmox & arch installation are on seperate partitions.

Hi,
which kernel and qemu version ?

(proxmox 4.0 use ubuntu willy kernel + qemu 2.4)

Ub14.04, qemu 2.3, working with kernel 3.16 and 3.19 without any patches. For my productivity I use OVMF for Windows instead of seabios, but it works with seabios and Linux too, so theoretically should work both in proxmox too, but for me seabios does not work at all, and with OVMF it's kinda broke too, I mean Windows needs 5 boot trys until it finaly boots up. Didnt try it with a Linux VM atm.
 
I could be great to see if it's working with proxmox qemu 2.4 + jessie 3.16 kernel for example.

I think it's a kvm bug in last kernels, but I would like to be sure that's it's not a regression in qemu.
 
I could be great to see if it's working with proxmox qemu 2.4 + jessie 3.16 kernel for example.

I think it's a kvm bug in last kernels, but I would like to be sure that's it's not a regression in qemu.

I installed the 3.16 Kernel from debian repo and the same issue occured - testing its not hardware before confirming though but it worked under arch.
 
I could be great to see if it's working with proxmox qemu 2.4 + jessie 3.16 kernel for example.

I think it's a kvm bug in last kernels, but I would like to be sure that's it's not a regression in qemu.

I installed Debian 8 and everything from the proxmox repos ontop, then made the original 3.16 kernel as default and it's working like a charm now, no crashes or reboots, but I'm using OVMF, didn't try seabios.

So you were right, problem should be somewhere in the new kvm and/or kernel build. Perhaps the implemented seabios is broken (too) but I dont care about that. Windows & Linux are fine with OVMF.
 
I installed Debian 8 and everything from the proxmox repos ontop, then made the original 3.16 kernel as default and it's working like a charm now, no crashes or reboots, but I'm using OVMF, didn't try seabios.

So you were right, problem should be somewhere in the new kvm and/or kernel build. Perhaps the implemented seabios is broken (too) but I dont care about that. Windows & Linux are fine with OVMF.


So your step is like this:
  1. Install Debian Jessie
  2. Add Proxmox Repositories & install as per wiki https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie
  3. Enable PCIE Passthrough as per wiki https://pve.proxmox.com/wiki/Pci_passthrough
  4. Use OMVF instead of SeaBios on VM
  5. PCIE-Passthrough works with GPUS

correct ?
 
Last edited:
Almost:
  1. Install Debian Jessie
  2. Add Proxmox Repositories as per wiki https://pve.proxmox.com/wiki/Install..._Debian_Jessie
  3. Set Debian Kernel 3.16 as default (or seletc it during boot in grub menu)
  4. Enable PCIE Passthrough as per wiki https://pve.proxmox.com/wiki/Pci_passthrough
  5. Use OMVF instead of SeaBios on VM
  6. PCIE-Passthrough works with GPUS

I tried using the Proxmox distribution with the same steps for the 3.16 kernel direct from Debian repos and it didn't work so I wonder if there is something else added to the distro causing the failure...
 
So you were right, problem should be somewhere in the new kvm and/or kernel build. Perhaps the implemented seabios is broken (too) but I dont care about that. Windows & Linux are fine with OVMF.
Perhaps then it could be a good idea to open a bug ticket so Proxmox developers can do something about this.

On a side note, what is the best way on Proxmox 4 to install OVMF and then use in VM's configuration?
 
I tried using the Proxmox distribution with the same steps for the 3.16 kernel direct from Debian repos and it didn't work so I wonder if there is something else added to the distro causing the failure...

Proxmox don't add nothing special to the distro, only qemu 2.4 is used instead default qemu 2.1 in debian jessie.

you can install proxmox 3.4, qemu 2.2 , on proxmox 4.0 if you want.

wget http://download.proxmox.com/debian/...on/binary-amd64/pve-qemu-kvm_2.2-13_amd64.deb
wget http://ftp.us.debian.org/debian/pool/main/libj/libjpeg8/libjpeg8_8d-1+deb7u1_amd64.deb
dpkg -i *.deb


or qemu 2.3, from proxmox 4.0 beta1

wget http://download.proxmox.com/debian/...nary-amd64.beta1/pve-qemu-kvm_2.3-5_amd64.deb
dpkg -i pve-qemu-kvm_2.3-5_amd64.deb
 
Last edited:
Perhaps then it could be a good idea to open a bug ticket so Proxmox developers can do something about this.

On a side note, what is the best way on Proxmox 4 to install OVMF and then use in VM's configuration?
You do not have to install it, just add the following line in your VM Config:
args: -bios /path/to/OVMF.fd
 
qemu 2.3, from proxmox 4.0 beta1

Do I understand correctly that I could simply install QEMU 2.3 from Proxmox 4.0 beta 1 (instead of installing Proxmox 4.0 with a 3.16 kernel over a Debian Jessie base) and that PCIe passthrough would work fine? I would rather not mess much with my current server installation.
 
Do I understand correctly that I could simply install QEMU 2.3 from Proxmox 4.0 beta 1 (instead of installing Proxmox 4.0 with a 3.16 kernel over a Debian Jessie base) and that PCIe passthrough would work fine? I would rather not mess much with my current server installation.

I think we could try qemu 2.3 with kernel 4.2. It could help to see if the problem come from qemu 2.4 or kernel.

If it's don't work, try again qemu 2.3 but with kernel 4.1
http://download.proxmox.com/debian/...eta1/pve-kernel-4.1.3-1-pve_4.1.3-7_amd64.deb

or kernel 3.19
http://download.proxmox.com/debian/...a1/pve-kernel-3.19.8-1-pve_3.19.8-3_amd64.deb


If the problem come from qemu 2.4, we can focus on it and help qemu devs to debug that.
 
Any more updates from other users, (successful or not) and this the issue been targeted now directly in Proxmox?
 
Code:
Hi guy,ovmf support has been added to last proxmox 4.X in pve-no-subscription repostory.just add   ovmf:1 in vmid.conf.(use virtio-scsi to boot).Your guest os need to be installed to boot on uefi.
 
Code:
Hi guy,ovmf support has been added to last proxmox 4.X in pve-no-subscription repostory.just add   ovmf:1 in vmid.conf.(use virtio-scsi to boot).Your guest os need to be installed to boot on uefi.

Nice. windows 10 with GPU Passthrough has been on my Agenda for a while now. Will try it tonight and report back.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!