Windows VMs created on XS7.0 not detecting Display Adapter Even after Installing NVIDIA Graphics Drivers

When a system, with over 500GB of RAM installed, has the GPU drivers on XenServer 7.0 installed, and on a Windows VM (Windows 7/8/10) you install the video drivers as per the Nvidia documentation – http://www.nvidia.com/download/driverResults.aspx/106952/en-us. The Windows VM the Display Adapters are not detected correctly and an error is returned when the Drivers are verified.

Note: This limitation applies only to systems with supported GPUs based on the Kepler and Maxwell architectures: GRID K1, GRID K2, Tesla M6, Tesla M10, and Tesla M60.

During the Boot time of the VM errors are generated in /var/log/messages on XenServer.

Sep 2 14:09:48 <hostname> vgpu-4[9428]: notice: vmiop_log: ######## Guest NVIDIA Driver Information: ########

Sep 2 14:09:48 <hostname> vgpu-4[9428]: notice: vmiop_log: Driver Version: 369.17

Sep 2 14:09:48 <hostname> vgpu-4[9428]: notice: vmiop_log: VGX Version: 5.1

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: NVOS status 0x1e

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: Assertion Failed at 0x6dcf1f80:143

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: 9 frames returned by backtrace

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv002085vgpu+0x18) [0x7f046dcf4a48]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv000041vgpu+0x31) [0x7f046dcf47c1]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidi<hostname> a-vgpu.so(_nv001288vgpu+0x560) [0x7f046dcf1f80]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv002572vgpu+0x752) [0x7f046dcec1c2]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv002060vgpu+0x34f) [0x7f046dcfa77f]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(+0x36f1f) [0x7f046dcddf1f]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/xen/bin/vgpu() [0x40bdfc]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /lib64/libpthread.so.0(+0x7dc5) [0x7f047120cdc5]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /lib64/libc.so.6(clone+0x6d) [0x7f0470f3a28d]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: VGPU message 4 failed, result code: 0x1e

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: 0xc1d00010, 0xff010000, 0xff00000d, 0x3e,

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: 0x2010, 0x0, 0x0, 0x22000, 0x22,

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: (Not logged)

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: NVOS status 0x1e

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: Assertion Failed at 0x6dcf1f80:143

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: 9 frames returned by backtrace

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv002085vgpu+0x18) [0x7f046dcf4a48]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv000041vgpu+0x31) [0x7f046dcf47c1]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv001288vgpu+0x560) [0x7f046dcf1f80]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv002572vgpu+0x752) [0x7f046dcec1c2]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv002060vgpu+0x34f) [0x7f046dcfa77f]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(+0x36f1f) [0x7f046dcddf1f]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/xen/bin/vgpu() [0x40bdfc]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /lib64/libpthread.so.0(+0x7dc5) [0x7f047120cdc5]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /lib64/libc.so.6(clone+0x6d) [0x7f0470f3a28d]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: VGPU message 4 failed, result code: 0x1e

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: 0xc1d00010, 0xff010000, 0xff00000d, 0x3e,

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: 0x2010, 0x0, 0x0, 0x12000, 0x12,

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: (Not logged)

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: NVOS status 0x1e

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: Assertion Failed at 0x6dcf1f80:143

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: 9 frames returned by backtrace

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv002085vgpu+0x18) [0x7f046dcf4a48]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv000041vgpu+0x31) [0x7f046dcf47c1]

Sep 2 14:09:48 <hostname> vgpu-4[9428]: error: vmiop_log: /usr/lib64/libnvidia-vgpu.so(_nv001288vgpu+0x560) [0x7f

In dmesg it shows IOMMU is enabled:

# dmesg |grep -i iomm

[45.375573] Using GPFN IOMMU mode, 1-to-1 offset is 0xc080000000

[45.385501] XEN-PV-IOMMU: Using software bounce buffering for IO on 32bit DMA devices (SWIOTLB)

[123.074616] XEN-PV-IOMMU – completed setting up 1-1 mapping

Related:

  • No Related Posts

Leave a Reply