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

Re: [Xen-devel] VGA passthrough is not working



On Mon, Jun 23, 2014 at 05:38:52PM +0400, Maxim Gordeev wrote:
> Hi!
> 
> I find new message into xen dmesg. Please, look at attach new_xl_dmesg.txt
> 
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed!
> gfn=ffffffff82006
> (XEN) memory_map: error -5 removing dom4 access to [5c00000,5c01fff]

Stefano,

This is what he has in dom0:

03:00.0 3D controller: NVIDIA Corporation GK110BGL [Tesla K40m] (rev a1)        
    Subsystem: NVIDIA Corporation Device 097e                                   
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- 
<MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes                                       
    Interrupt: pin A routed to IRQ 40                                           
    Region 0: Memory at de000000 (32-bit, non-prefetchable) [size=16M]          
    Region 1: Memory at 5800000000 (64-bit, prefetchable) [size=16G]            
    Region 3: Memory at 5c00000000 (64-bit, prefetchable) [size=32M]            

Which seems to fail being being mapped in dom0 in the first place:

> (XEN) p2m.c:793:d0 set_mmio_p2m_entry: set_p2m_entry failed! 
> mfn=ffffffffffffffff
> (XEN) memory_map:fail: dom3 gfn=ffffffff82001 mfn=5c00001

by the QEMU doing a map (see below at the end of this email for
his hypervisor outpuT) 

Maxim, could you supply the exact /var/log/xen/qemu-dm.log
file please? The ones in the thread seem to point to  87:00.0 and  86:00.0
device.
> 
> 
> What is this?
> 18.06.2014 11:57, Maxim Gordeev ?????:
> > Please, open archive troubleNvidia.tgz...
> > home/mgordeev/Documents/Xen/NVIDIA/lastLog/xen_logs.tgz
> >
> > I attached a files.
> > Thanks!
> > Regards!
> >
> > 17.06.2014 20:35, Konrad Rzeszutek Wilk ?????:
> >> On Tue, Jun 17, 2014 at 12:08:43PM +0400, Maxim Gordeev wrote:
> >>> Hi!
> >>>
> >>> Thanks you for help!!!
> >>>
> >>> Please see the attachment.
> >> Please also include the /var/log/xen/qem* files.
> >>
> >> And 'xl dmesg'.
> >>> Regards!
> >>> 16.06.2014 21:17, Konrad Rzeszutek Wilk ?????:
> >>>> On Mon, Jun 16, 2014 at 02:01:35PM +0400, Maxim Gordeev wrote:
> >>>>> Hi!
> >>>>>
> >>>>> I find some message into dmesg:
> >>>>> pci 0000:00:05.0: BAR 1: can't assign mem pref (size 0x100000000)
> >>>>> [    0.910157] pci 0000:00:05.0: BAR 1: trying firmware assignment [mem
> >>>>> 0x100000000-0x1ffffffff 64bit pref]
> >>>>> [    0.910162] pci 0000:00:05.0: BAR 1: assigned [mem
> >>>>> 0x100000000-0x1ffffffff 64bit pref]
> >>>>>
> >>>>> This issue when I use VM whit the next paramet?r: device_model_version
> >>>>> =  "qemu-xen"
> >>>>>
> >>>>> And lspci -s 00:05.0 -vvv :
> >>>>> Subsystem: NVIDIA Corporation Device 097e
> >>>>> Physical Slot: 5
> >>>>> ...
> >>>>>  Region 0: Memory at 85000000 (32-bit, non-prefetchable) [size=16M]
> >>>>>  Region 1: Memory at 100000000 (64-bit, prefetchable) [size=4G]
> >>>>>  Region 3: Memory at 82000000 (64-bit, prefetchable) [size=32M]
> >>>>>
> >>>>>
> >>>>> Do you help me?
> >>>> Please include (I mentioned this earlier but it probably got lost), your
> >>>> full 'dmesg' from both the guest _and_ the initial domain (dom0). Also
> >>>> your 'lspci -vvv' from dom0 _and_ from your guest.
> >>>>
> >>>> Lastly, also include you /var/log/xen/qemu-* file.
> >>>>
> >>>> Thank you.
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxx
> > http://lists.xen.org/xen-devel
> 

>  
>  Xen 4.4.1-pre
> (XEN) Xen version 4.4.1-pre (root@xxxxxxxxxxxxx) (gcc (Debian 4.8.3-2) 4.8.3) 
> debug=n Wed Jun 11 08:13:07 CDT 2014
> (XEN) Latest ChangeSet: 
> (XEN) Bootloader: GRUB 1.99-27+deb7u2
> (XEN) Command line: placeholder dom0_mem=512M
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
> (XEN)  EDID info not retrieved because no DDC retrieval method detected
> (XEN) Disc information:
> (XEN)  Found 1 MBR signatures
> (XEN)  Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009b000 (usable)
> (XEN)  000000000009b000 - 00000000000a0000 (reserved)
> (XEN)  00000000000e0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 000000007dce1000 (usable)
> (XEN)  000000007dce1000 - 000000007dd70000 (reserved)
> (XEN)  000000007dd70000 - 000000007de7a000 (ACPI data)
> (XEN)  000000007de7a000 - 000000007e0ab000 (ACPI NVS)
> (XEN)  000000007e0ab000 - 000000007f34c000 (reserved)
> (XEN)  000000007f34c000 - 000000007f800000 (ACPI NVS)
> (XEN)  0000000080000000 - 0000000090000000 (reserved)
> (XEN)  00000000fed1c000 - 00000000fed40000 (reserved)
> (XEN)  00000000ff000000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 0000001080000000 (usable)
> (XEN) ACPI: RSDP 000F04A0, 0024 (r2 SUPERM)
> (XEN) ACPI: XSDT 7DDA5090, 009C (r1 SUPERM SMCI--MB        1 AMI     10013)
> (XEN) ACPI: FACP 7DDB0D88, 00F4 (r4 SUPERM SMCI--MB        1 AMI     10013)
> (XEN) ACPI: DSDT 7DDA51B8, BBCD (r2 SUPERM SMCI--MB        0 INTL 20091112)
> (XEN) ACPI: FACS 7E0A2080, 0040
> (XEN) ACPI: APIC 7DDB0E80, 0294 (r3                        1 AMI     10013)
> (XEN) ACPI: FPDT 7DDB1118, 0044 (r1                        1 AMI     10013)
> (XEN) ACPI: SRAT 7DDB1160, 0530 (r1 A M I  AMI SRAT        1 AMI.        0)
> (XEN) ACPI: SLIT 7DDB1690, 0030 (r1 A M I  AMI SLIT        0 AMI.        0)
> (XEN) ACPI: HPET 7DDB16C0, 0038 (r1 SUPERM SMCI--MB        1 AMI.        5)
> (XEN) ACPI: PRAD 7DDB16F8, 00BE (r2 PRADID  PRADTID        1 MSFT  4000000)
> (XEN) ACPI: SPMI 7DDB17B8, 0040 (r5 A M I   OEMSPMI        0 AMI.        0)
> (XEN) ACPI: SSDT 7DDB17F8, C7AE8 (r2  INTEL    CpuPm     4000 INTL 20091112)
> (XEN) ACPI: EINJ 7DE792E0, 0130 (r1    AMI AMI EINJ        0             0)
> (XEN) ACPI: ERST 7DE79410, 0230 (r1  AMIER AMI ERST        0             0)
> (XEN) ACPI: HEST 7DE79640, 00A8 (r1    AMI AMI HEST        0             0)
> (XEN) ACPI: BERT 7DE796E8, 0030 (r1    AMI AMI BERT        0             0)
> (XEN) ACPI: DMAR 7DE79718, 0160 (r1 A M I   OEMDMAR        1 INTL        1)
> (XEN) ACPI: MCFG 7DE79878, 003C (r1 SUPERM SMCI--MB        1 MSFT       97)
> (XEN) System RAM: 65500MB (67072496kB)
> (XEN) Domain heap initialised DMA width 32 bits
> (XEN) ACPI: 32/64X FACS address mismatch in FADT - 7e0a2080/0000000000000000, 
> using 32
> (XEN) Processor #0 7:14 APIC version 21
> (XEN) Processor #2 7:14 APIC version 21
> (XEN) Processor #4 7:14 APIC version 21
> (XEN) Processor #6 7:14 APIC version 21
> (XEN) Processor #8 7:14 APIC version 21
> (XEN) Processor #16 7:14 APIC version 21
> (XEN) Processor #18 7:14 APIC version 21
> (XEN) Processor #20 7:14 APIC version 21
> (XEN) Processor #22 7:14 APIC version 21
> (XEN) Processor #24 7:14 APIC version 21
> (XEN) Processor #32 7:14 APIC version 21
> (XEN) Processor #34 7:14 APIC version 21
> (XEN) Processor #36 7:14 APIC version 21
> (XEN) Processor #38 7:14 APIC version 21
> (XEN) Processor #40 7:14 APIC version 21
> (XEN) Processor #48 7:14 APIC version 21
> (XEN) Processor #50 7:14 APIC version 21
> (XEN) Processor #52 7:14 APIC version 21
> (XEN) Processor #54 7:14 APIC version 21
> (XEN) Processor #56 7:14 APIC version 21
> (XEN) Processor #1 7:14 APIC version 21
> (XEN) Processor #3 7:14 APIC version 21
> (XEN) Processor #5 7:14 APIC version 21
> (XEN) Processor #7 7:14 APIC version 21
> (XEN) Processor #9 7:14 APIC version 21
> (XEN) Processor #17 7:14 APIC version 21
> (XEN) Processor #19 7:14 APIC version 21
> (XEN) Processor #21 7:14 APIC version 21
> (XEN) Processor #23 7:14 APIC version 21
> (XEN) Processor #25 7:14 APIC version 21
> (XEN) Processor #33 7:14 APIC version 21
> (XEN) Processor #35 7:14 APIC version 21
> (XEN) Processor #37 7:14 APIC version 21
> (XEN) Processor #39 7:14 APIC version 21
> (XEN) Processor #41 7:14 APIC version 21
> (XEN) Processor #49 7:14 APIC version 21
> (XEN) Processor #51 7:14 APIC version 21
> (XEN) Processor #53 7:14 APIC version 21
> (XEN) Processor #55 7:14 APIC version 21
> (XEN) Processor #57 7:14 APIC version 21
> (XEN) IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
> (XEN) IOAPIC[1]: apic_id 2, version 32, address 0xfec01000, GSI 24-47
> (XEN) IOAPIC[2]: apic_id 3, version 32, address 0xfec40000, GSI 48-71
> (XEN) Enabling APIC mode:  Phys.  Using 3 I/O APICs
> (XEN) Switched to APIC driver x2apic_cluster.
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Detected 3000.090 MHz processor.
> (XEN) Initing memory sharing.
> (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7
> (XEN) Intel VT-d iommu 0 supported page sizes: 4kB, 2MB, 1GB.
> (XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB.
> (XEN) Intel VT-d Snoop Control enabled.
> (XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
> (XEN) Intel VT-d Queued Invalidation enabled.
> (XEN) Intel VT-d Interrupt Remapping enabled.
> (XEN) Intel VT-d Shared EPT tables enabled.
> (XEN) I/O virtualisation enabled
> (XEN)  - Dom0 mode: Relaxed
> (XEN) Interrupt remapping enabled
> (XEN) Enabled directed EOI with ioapic_ack_old on!
> (XEN) ENABLING IO-APIC IRQs
> (XEN)  -> Using old ACK method
> (XEN) Platform timer is 14.318MHz HPET
> (XEN) Allocated console ring of 128 KiB.
> (XEN) VMX: Supported advanced features:
> (XEN)  - APIC MMIO access virtualisation
> (XEN)  - APIC TPR shadow
> (XEN)  - Extended Page Tables (EPT)
> (XEN)  - Virtual-Processor Identifiers (VPID)
> (XEN)  - Virtual NMI
> (XEN)  - MSR direct-access bitmap
> (XEN)  - Unrestricted Guest
> (XEN)  - APIC Register Virtualization
> (XEN)  - Virtual Interrupt Delivery
> (XEN)  - Posted Interrupt Processing
> (XEN) HVM: ASIDs enabled.
> (XEN) HVM: VMX enabled
> (XEN) HVM: Hardware Assisted Paging (HAP) detected
> (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
> (XEN) Brought up 40 CPUs
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN)  Xen  kernel: 64-bit, lsb, compat32
> (XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1ec5000
> (XEN) PHYSICAL MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000001050000000->0000001054000000 (104550 pages to be 
> allocated)
> (XEN)  Init. ramdisk: 000000107d866000->0000001080000000
> (XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff81000000->ffffffff81ec5000
> (XEN)  Init. ramdisk: ffffffff81ec5000->ffffffff8465f000
> (XEN)  Phys-Mach map: ffffffff8465f000->ffffffff8475f000
> (XEN)  Start info:    ffffffff8475f000->ffffffff8475f4b4
> (XEN)  Page tables:   ffffffff84760000->ffffffff84789000
> (XEN)  Boot stack:    ffffffff84789000->ffffffff8478a000
> (XEN)  TOTAL:         ffffffff80000000->ffffffff84c00000
> (XEN)  ENTRY ADDRESS: ffffffff818c81f0
> (XEN) Dom0 has maximum 40 VCPUs
> (XEN) Scrubbing Free RAM: 
> ..................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................done.
> (XEN) Initial low memory virq threshold set at 0x4000 pages.
> (XEN) Std. Loglevel: Errors and warnings
> (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> (XEN) Xen is relinquishing VGA console.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
> Xen)
> (XEN) Freed 276kB init memory.
> (XEN) p2m.c:793:d0 set_mmio_p2m_entry: set_p2m_entry failed! 
> mfn=ffffffffffffffff
> (XEN) memory_map:fail: dom3 gfn=ffffffff82001 mfn=5c00001
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82000
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82000
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82001
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82002
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82003
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82004
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82005
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82006
> (XEN) memory_map: error -5 removing dom3 access to [5c00000,5c01fff]
> (XEN) printk: 8185 messages suppressed.
> (XEN) p2m.c:793:d0 set_mmio_p2m_entry: set_p2m_entry failed! 
> mfn=ffffffffffffffff
> (XEN) memory_map:fail: dom4 gfn=ffffffff82001 mfn=5c00001
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82000
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82000
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82001
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82002
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82003
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82004
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82005
> (XEN) p2m.c:816:d0 clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=ffffffff82006
> (XEN) memory_map: error -5 removing dom4 access to [5c00000,5c01fff]

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.