1
完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
[与我最近的其他帖子有关,但我是单独发布的,希望能使问题清晰易懂。]
对于ESXi 6 U2,无论vGPU配置文件如何,在Linux上安装361.45.09网格驱动程序(例如RHEL 6)时,驱动程序安装程序会询问是否要创建xorg.conf。 如果您说“是”,则生成的xorg.conf不起作用,即startx给出“(EE)未检测到设备”。 这与在没有参数的情况下手动运行'nvidia-xconfig'相同,并提供了如下设备部分: “设备”部分 标识符“Device0” 司机“nvidia” 供应商名称“NVIDIA Corporation” EndSection 如果显式指定vGPU设备的busid(例如nvidia-xconfig --busid = PCI:2:0:0,则X.org成功启动。设备部分如下所示: “设备”部分 标识符“Device0” 司机“nvidia” 供应商名称“NVIDIA Corporation” BusID“PCI:2:0:0” EndSection (我注意到,例如安装Horizon View时,它会完全重写xorg.conf并添加一个显式的BusID。) 问题:是否期望nvidia-xconfig生成不起作用的xorg.conf? 如果没有,是否有计划最终修复它? 谢谢。 [编辑:附加日志] 以上来自于谷歌翻译 以下为原文 [Related to my other recent post but I'm posting separately to hopefully make the issue clear and easy to respond to.] With ESXi 6 U2, regardless of vGPU profile, when installing the 361.45.09 grid driver on Linux (e.g. RHEL 6) the driver installer asks if one wants to create xorg.conf. If you say "yes" the resulting xorg.conf does not work, i.e. startx gives "(EE) No devices detected". This is the same as running 'nvidia-xconfig' manually without arguments and gives a device section like: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection If one explicitly specifies the vGPU device's busid (e.g. nvidia-xconfig --busid=PCI:2:0:0 then X.org starts successfully. The device section looks like: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BusID "PCI:2:0:0" EndSection (I note that when e.g. Horizon View is installed it completely rewrites xorg.conf and adds an explicit BusID.) Question: Is it expected that nvidia-xconfig generates a non-working xorg.conf? If not, is there a plan to eventually fix it? Thanks. [edit: attached logs] |
|
相关推荐
5个回答
|
|
嗨Nathan,
感谢您突出这一点 - 我会将其传递给工程团队。 最好的祝愿, 雷切尔 以上来自于谷歌翻译 以下为原文 Hi Nathan, Thanks for highlighting this - I'll pass it on to the engineering team. Best wishes, Rachel |
|
|
|
另请注意,带有CentOS 7.1 guest虚拟机的Citrix Xen Server 6.5 SP1和虚拟机管理程序和guest虚拟机上的367.43驱动程序*不*需要BusID;
nvidia-xconfig开箱即用,可以生成有效的xorg.conf。 以上来自于谷歌翻译 以下为原文 Further note, Citrix Xen Server 6.5 SP1 with CentOS 7.1 guest and 367.43 drivers on hypervisor and guest does *not* require BusID; nvidia-xconfig produces a working xorg.conf out of the box. |
|
|
|
进一步说明:RHEL 6.6上的裸机和352.99驱动程序(最新的特斯拉,非网格驱动程序)确实需要BusID。
以上来自于谷歌翻译 以下为原文 Further note: Bare metal on RHEL 6.6 with 352.99 drivers (latest Tesla, non-Grid driver) does require BusID. |
|
|
|
嗨Nathan,
我和一位乐于助人的工程师说过......你能上传一份日志吗? 工程师说: 我们可以从这个配置中获得一个nvidia-bug-report.log吗? 如果虚拟化环境正在暴露另一个GPU,那么X可能只是试图将该GPU与NVIDIA驱动程序一起使用,这将无法工作,因此需要一个显式的BusID。 有许多配置可能需要显式的BusID; 默认情况下,nvidia-xconfig不会分配一个,因为它使得生成的xorg.conf更加灵活。 他还补充说:FWIW X不会找到非VGA设备,很多Tesla / GRID卡都是3D控制器,例如Tesla M4: #lspci | grep NV 01:00.0 3D控制器:NVIDIA Corporation Device 1431(rev a1) 如果NV gpus都不是VGA设备,那么nvidia-xconfig可以足够聪明地添加BusID ...大概是如果你使用nvidia-xconfig来生成xorg.conf你打算使用nvidia gpu。 但是很快就有多个屏幕/ gpus就无法知道什么是正确的事情。 你可以在你的卡上运行lspci,这样我们就可以看到它是什么...... 也许这是通过设计,而不是我们可以“修复”,但可能需要更好的文档/指令。 雷切尔 以上来自于谷歌翻译 以下为原文 Hi Nathan, I've spoken to a helpful engineer... Can you upload a log? The engineer said: Can we get an nvidia-bug-report.log from this configuration? If the virtualization environment is exposing another GPU, it's likely that X is simply trying to use that GPU with the NVIDIA driver, which won't work, hence the need for an explicit BusID. There are many configurations where an explicit BusID may be needed; nvidia-xconfig by default won't assign one, since it makes the resulting xorg.conf more flexible. He also added: FWIW X won't find non-VGA devices, lot of Tesla/GRID cards are 3D Controllers, eg Tesla M4: # lspci | grep NV 01:00.0 3D controller: NVIDIA Corporation Device 1431 (rev a1) nvidia-xconfig could be smart enough to add BusID if none of the NV gpus are VGA devices... presumably if you're using nvidia-xconfig to generate a xorg.conf you intend to use an nvidia gpu. But with multiple screens/gpus quickly its impossible to know what would be right thing to do. could you run lspci on your card so we can see what it is... It maybe this is by desing and not one we can "fix" but better doc / instruction might be necessary. Rachel |
|
|
|
附加日志到此线程中的第一条消息。
这些来自VMWare vGPU场景,而不是裸机。 工程师欢迎ping nkidd @ opentext。 如果想以更及时的方式得到答案。 以上来自于谷歌翻译 以下为原文 Attached logs to the first message in this thread. These are from the VMWare vGPU scenario, not the bare metal. Engineer is welcome to ping nkidd @ opentext . com if wanting answers in a more timely fashion. |
|
|
|
只有小组成员才能发言,加入小组>>
使用Vsphere 6.5在Compute模式下使用2个M60卡遇到VM问题
3127 浏览 5 评论
是否有可能获得XenServer 7.1的GRID K2驱动程序?
3533 浏览 4 评论
小黑屋| 手机版| Archiver| 德赢Vwin官网 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-23 12:32 , Processed in 0.868513 second(s), Total 82, Slave 66 queries .
Powered by 德赢Vwin官网 网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
德赢Vwin官网 观察
版权所有 © 湖南华秋数字科技有限公司
德赢Vwin官网 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号