Recent content by vtrandal

@spirit, you may have solved this problem for us with your reply. Thank you! Your reply appears to address the issue and may lead to a solution or work around for us. Thanks again! So then how would be go about setting those args in a Proxmox guest? Just add them to the config file in...

@Soulgriever, the solution was so to do as you. In the /etc/pve/qemu-server/<vmid>.conf file we removed vga:qxl and added x-vga=on. We must note that we could not add x-vga=on until after the operating system was installed in the quest. So then this thread can be closed resolved if there are no...

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...

It's not necessary to have a tesla card to understand or reproduce our primary problem. Just create a linux VM with "KVM hardware virtualization" disabled and measure how long it takes for the VM to boot up. We find it takes about 10 minutes. But with "KVM hardware virtualization" enabled it...

Hello manu. It is a passthrough problem. Passthrough works if "KVM hardware virtualization" is disabled. We would like to understand why that is the case. Disabling "KVM hardware virtualization makes the VM very slow, otherwise we would consider it a solution. To be clear about the device we...

In my Proxmox VE 4.1 installations disabling KVM hardware virtualization fixes an nvidia-smi error message, and I would like to understand why. Here is the error message that results from running nvidia-smi on the Linux guest with KVM hardware virtualization enabled: Unable to determine the...