Uses "passthroughed" GPU instead of iGPU
Reported by
code.dr...@googlemail.com,
Apr 5 2017
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. Use PC with iGPU and GPU 2. Use vfio to separate GPU from system 3. Open chrome://gpu/ What is the expected behavior? Chrome use the iGPU for rendering because the dedicated GPU is not available. What went wrong? Chrome uses the unavailable dedicated GPU. Did this work before? N/A Chrome version: 57.0.2987.133 Channel: stable OS Version: Flash Version: In my case I use an Intel i7 7700K and an nvidia GTX 970. The nvidia card is isolated from host. She will be used in an gaming VM. I think the problem can be found in SystemInfo.cpp: https://cs.chromium.org/chromium/src/third_party/angle/src/gpu_info_util/SystemInfo.cpp?rcl=fe48632f2f47f9513c0557c331a8f346ed92c82d&l=134 The comment indicate the problem: "// On dual-GPU systems we assume the non-Intel GPU is the primary one.". It is not checked whether this GPU is usable at all.
,
Apr 5 2017
,
Apr 5 2017
,
Apr 6 2017
,
Apr 7 2017
,
Apr 7 2017
Sorry for the bug. None of us have ever tried a setup like this. Please provide more details on how you isolated the discrete GPU. Is this along the right lines? https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVMF#Using_vfio-pci Honestly, if you're this much of a power user then we would welcome any patches that get things working as expected on your system. I don't think we have any desktop machines with both integrated Intel and discrete NVIDIA GPUs in our office.
,
Apr 7 2017
,
Apr 7 2017
,
Apr 7 2017
No problem, mistakes can happen ;) The linked guide is correct. I use the mentioned procedure, kernel module etc. I can test new versions or run delivered programs to get more information for you but I'm can only read some C or C++ code. I can't write it. So I can't help directly with a patch. Sorry!
,
Apr 11 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 11 2018
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by code.dr...@googlemail.com
, Apr 5 2017656 bytes
656 bytes View Download