The subject says it all. We can speculate as to the cause: We think it is necessary to enable "above 4G decoding" in the OVMF bios. If that is the case then the question is: How can we enabled "above 4G decoding" or similar feature in the OVMF bios?
Otherwise, we believe the reason the VM cannot finish booting is because the K80 cannot get the PCI resources it needs unless "above 4G decoding" or similar feature is enabled in the OVMF bios.
Specifically, when attempting to start the VM using "qm start 112" there is no error message except on the console it says: "This VM has no graphic display device." That is the only message of any kind that we can see anywhere.
PCI passthrough works on this VM if the device is Nvidia Tesla M2090 as solved in previous thread:
https://forum.proxmox.com/threads/kvm-hardware-virtualization-affects-nvidia-smi.25873/
In the case of the M2090 we can use ssh to login into the guest operating system, but in the case of the K80 we get the following error message from ssh:
ssh: connect to host 192.168.1.65 port 22: No route to host
Otherwise, we believe the reason the VM cannot finish booting is because the K80 cannot get the PCI resources it needs unless "above 4G decoding" or similar feature is enabled in the OVMF bios.
Specifically, when attempting to start the VM using "qm start 112" there is no error message except on the console it says: "This VM has no graphic display device." That is the only message of any kind that we can see anywhere.
PCI passthrough works on this VM if the device is Nvidia Tesla M2090 as solved in previous thread:
https://forum.proxmox.com/threads/kvm-hardware-virtualization-affects-nvidia-smi.25873/
In the case of the M2090 we can use ssh to login into the guest operating system, but in the case of the K80 we get the following error message from ssh:
ssh: connect to host 192.168.1.65 port 22: No route to host
Last edited: