Re: PCI assignement with nvidia K1: RmInitAdapter failed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alex Williamson <alex.williamson@xxxxxxxxxx> a écrit :

Do you see any IOMMU faults in dmesg on
the host around this error?

No, the only messages produces by IOMMU occurred at boot time.

Does nouveau work?

Not really. When I load the nouveau module in the guest I have the following messages:

Jul 11 11:56:29 raringvm1 kernel: [ 555.659921] [drm] Initialized drm 1.1.0 20060810
Jul 11 11:56:29 raringvm1 kernel: [  555.668919] wmi: Mapper loaded
Jul 11 11:56:29 raringvm1 kernel: [ 555.685793] checking generic (fa000000 160000) vs hw (f0000000 8000000) Jul 11 11:56:29 raringvm1 kernel: [ 555.685795] checking generic (fa000000 160000) vs hw (f8000000 2000000) Jul 11 11:56:29 raringvm1 kernel: [ 555.689434] nouveau [ DEVICE][0000:00:03.0] BOOT0 : 0x0e7320a2 Jul 11 11:56:29 raringvm1 kernel: [ 555.689438] nouveau [ DEVICE][0000:00:03.0] Chipset: GK107 (NVE7) Jul 11 11:56:29 raringvm1 kernel: [ 555.689439] nouveau [ DEVICE][0000:00:03.0] Family : NVE0 Jul 11 11:56:29 raringvm1 kernel: [ 555.690528] nouveau [ VBIOS][0000:00:03.0] checking PRAMIN for image... Jul 11 11:56:29 raringvm1 kernel: [ 555.690554] nouveau [ VBIOS][0000:00:03.0] ... signature not found Jul 11 11:56:29 raringvm1 kernel: [ 555.690556] nouveau [ VBIOS][0000:00:03.0] checking PROM for image... Jul 11 11:56:29 raringvm1 kernel: [ 555.899715] nouveau [ VBIOS][0000:00:03.0] ... appears to be valid Jul 11 11:56:29 raringvm1 kernel: [ 555.899717] nouveau [ VBIOS][0000:00:03.0] using image from PROM Jul 11 11:56:29 raringvm1 kernel: [ 555.899797] nouveau [ VBIOS][0000:00:03.0] BIT signature found Jul 11 11:56:29 raringvm1 kernel: [ 555.899798] nouveau [ VBIOS][0000:00:03.0] version 80.07.4e.00.06 Jul 11 11:56:29 raringvm1 kernel: [ 555.906258] nouveau [ PFB][0000:00:03.0] RAM type: DDR3 Jul 11 11:56:29 raringvm1 kernel: [ 555.906261] nouveau [ PFB][0000:00:03.0] RAM size: 4096 MiB Jul 11 11:56:29 raringvm1 kernel: [ 555.906262] nouveau [ PFB][0000:00:03.0] ZCOMP: 0 tags Jul 11 11:56:29 raringvm1 kernel: [ 555.955664] nouveau [ THERM][0000:00:03.0] Found an max1617 at address 0x4c (controlled by lm_sensors) Jul 11 11:56:31 raringvm1 kernel: [ 555.955666] nouveau [ I2C][0000:00:03.0] detected monitoring device: max1617 Jul 11 11:56:31 raringvm1 kernel: [ 555.999204] [TTM] Zone kernel: Available graphics memory: 2024782 kiB Jul 11 11:56:31 raringvm1 kernel: [ 555.999205] [TTM] Initializing pool allocator Jul 11 11:56:31 raringvm1 kernel: [ 555.999208] [TTM] Initializing DMA pool allocator Jul 11 11:56:31 raringvm1 kernel: [ 555.999267] nouveau [ DRM] VRAM: 4096 MiB Jul 11 11:56:31 raringvm1 kernel: [ 555.999268] nouveau [ DRM] GART: 512 MiB Jul 11 11:56:31 raringvm1 kernel: [ 555.999270] nouveau [ DRM] BIT BIOS found Jul 11 11:56:31 raringvm1 kernel: [ 555.999271] nouveau [ DRM] Bios version 80.07.4e.00 Jul 11 11:56:31 raringvm1 kernel: [ 555.999273] nouveau [ DRM] TMDS table version 2.0 Jul 11 11:56:31 raringvm1 kernel: [ 555.999274] nouveau [ DRM] DCB version 4.0 Jul 11 11:56:31 raringvm1 kernel: [ 555.999275] nouveau [ DRM] DCB outp 00: 02000f00 00020030 Jul 11 11:56:31 raringvm1 kernel: [ 555.999276] nouveau [ DRM] DCB conn 00: 00000000 Jul 11 11:56:31 raringvm1 kernel: [ 556.002406] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). Jul 11 11:56:31 raringvm1 kernel: [ 556.002408] [drm] No driver support for vblank timestamp query. Jul 11 11:56:31 raringvm1 kernel: [ 556.012527] nouveau E[ PDISP][0000:00:03.0] chid 0 mthd 0x0000 data 0x00000000 0x10001000 0x00000001 Jul 11 11:56:31 raringvm1 kernel: [ 558.005281] [TTM] Finalizing pool allocator Jul 11 11:56:31 raringvm1 kernel: [ 558.005285] [TTM] Finalizing DMA pool allocator Jul 11 11:56:31 raringvm1 kernel: [ 558.005300] [TTM] Zone kernel: Used memory at exit: 0 kiB Jul 11 11:56:31 raringvm1 kernel: [ 558.013388] nouveau: probe of 0000:00:03.0 failed with error -16

So I don't know what it the error -16 but when I try to start an X server it starts well and finally complains about KMS that is not enabled. I checked in the config file and CONFIG_FRAMEBUFFER_CONSOLE is set to y.

As KMS seems required by the nouveau driver, X failed to use nouveau. Here is the logs in Xorg.log:

[    22.234] (II) LoadModule: "nouveau"
[    22.235] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[    22.236] (II) Module nouveau: vendor="X.Org Foundation"
[    22.236] 	compiled for 1.13.3, module version = 1.0.7
[    22.236] 	Module class: X.Org Video Driver
[    22.236] 	ABI class: X.Org Video Driver, version 13.1
[    22.236] (II) NOUVEAU driver Date:   Wed Mar 27 09:50:03 2013 +0100
[    22.236] (II) NOUVEAU driver for NVIDIA chipset families :
[    22.236] 	RIVA TNT        (NV04)
[    22.236] 	RIVA TNT2       (NV05)
[    22.236] 	GeForce 256     (NV10)
[    22.236] 	GeForce 2       (NV11, NV15)
[    22.236] 	GeForce 4MX     (NV17, NV18)
[    22.236] 	GeForce 3       (NV20)
[    22.236] 	GeForce 4Ti     (NV25, NV28)
[    22.236] 	GeForce FX      (NV3x)
[    22.236] 	GeForce 6       (NV4x)
[    22.236] 	GeForce 7       (G7x)
[    22.236] 	GeForce 8       (G8x)
[    22.236] 	GeForce GTX 200 (NVA0)
[    22.236] 	GeForce GTX 400 (NVC0)
[    22.236] (--) using VT number 7

[    22.239] (EE) [drm] KMS not enabled
[    22.239] (EE) No devices detected.


Regards,
Guillaume

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux