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.
Just to mention again, it works perfectly under ubuntu or arch.
Just to mention again, it works perfectly under ubuntu or arch.
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?
Hi,
which kernel and qemu version ?
(proxmox 4.0 use ubuntu willy kernel + qemu 2.4)
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 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.
Almost:
- Install Debian Jessie
- Add Proxmox Repositories as per wiki https://pve.proxmox.com/wiki/Install..._Debian_Jessie
- Set Debian Kernel 3.16 as default (or seletc it during boot in grub menu)
- Enable PCIE Passthrough as per wiki https://pve.proxmox.com/wiki/Pci_passthrough
- Use OMVF instead of SeaBios on VM
- PCIE-Passthrough works with GPUS
Perhaps then it could be a good idea to open a bug ticket so Proxmox developers can do something about this.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 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...
You do not have to install it, just add the following line in your VM Config: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?
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.
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.