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 device handle for GPU 0000:0B:00.0: Unknown Error
But when KVM hardware virtualization is disabled the error message does not happen and the GPU is operational in the Linux guest. Disabling KVM hardware virtualization results in very slow guest, otherwise I would consider it a solution.
So then I want to understand how disabling KVM hardware virtualization seemingly fixes the above device handle error and makes the GPU operational. It's like disabling KVM hardware virtualization solves an initial condition problem in the GPU that only becomes a problem when KVM hardware virtualization is enabled.
The GPU is Nvidia Tesla M2090 with various recent driver versions, and the guest is Ubuntu Server 14.04.3.There's a ton of other detail I could add here, but I'm not sure what would be most helpful except perhaps the following list of hardware upon which this error occurs.
motherboards: Asrock EPC612D8 and Asus Z10PE-D8.
processor: Intel Xeon E5-2609v3
Unable to determine the device handle for GPU 0000:0B:00.0: Unknown Error
But when KVM hardware virtualization is disabled the error message does not happen and the GPU is operational in the Linux guest. Disabling KVM hardware virtualization results in very slow guest, otherwise I would consider it a solution.
So then I want to understand how disabling KVM hardware virtualization seemingly fixes the above device handle error and makes the GPU operational. It's like disabling KVM hardware virtualization solves an initial condition problem in the GPU that only becomes a problem when KVM hardware virtualization is enabled.
The GPU is Nvidia Tesla M2090 with various recent driver versions, and the guest is Ubuntu Server 14.04.3.There's a ton of other detail I could add here, but I'm not sure what would be most helpful except perhaps the following list of hardware upon which this error occurs.
motherboards: Asrock EPC612D8 and Asus Z10PE-D8.
processor: Intel Xeon E5-2609v3