WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] pt_pci_write_config: Warning: Guest attempt to set address t

To: 'Ian Pratt' <Ian.Pratt@xxxxxxxxxxxxx>
Subject: [Xen-devel] pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:03.0][Offset:30h][Length:4]
From: Tim Moore <timothy.moore@xxxxxxxxxxx>
Date: Mon, 13 Apr 2009 15:12:01 +0100
Accept-language: en-US, en-GB
Acceptlanguage: en-US, en-GB
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 13 Apr 2009 07:12:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acm8QdB5tCUjaCJPR4+4CWOI/5M4eQ==
Thread-topic: pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:03.0][Offset:30h][Length:4]

Hi Ian,

 

I noticed that you updated the qemu-dm passthrough debug messages recently and was wondering if you could help me with this issue?

(Please see xen-devel postings for further info)

 

To sum things up, I have a non-hvm DomU with PCI Passthrough working successfully. The problem is that this is not working for any hvm DomU. Is this BAR warning related to my issue? I`m assume the vendor driver is attempting to set BAR and not just accepting the values passed in.

 

What I find strange is that I am using the vendor driver under the non-hvm DomU also. Maybe pcifront is doing something that qemu-dm is not ?

 

Here is the qemu-dm log output … (relevant parts)

 

register_real_device: Assigning real physical device 03:00.0 ...

pt_register_regions: IO region registered (size=0x01000000 base_addr=0xb2000000)

pt_register_regions: IO region registered (size=0x10000000 base_addr=0xe000000c)

pt_register_regions: IO region registered (size=0x02000000 base_addr=0xb0000004)

pt_register_regions: IO region registered (size=0x00000080 base_addr=0x00001001)

pt_msi_setup: msi mapped with pirq ff

register_real_device: Real physical device 03:00.0 registered successfuly!

IRQ type = MSI-INTx

Register xen platform.

Done register platform.

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.

xs_read(/local/domain/0/device-model/3/xen_extended_power_mgmt): read error

xs_read(): vncpasswd get error. /vm/900c41f9-a3f6-d78f-2270-93e116ee07e7/vncpasswd.

I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0

pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:03.0][Offset:30h][Length:4]

pt_iomem_map: e_phys=e0000000 maddr=e0000000 type=8 len=268435456 index=1 first_map=1

cirrus vga map change while on lfb mode

pt_iomem_map: e_phys=f2000000 maddr=b0000000 type=0 len=33554432 index=3 first_map=1

pt_iomem_map: e_phys=f4000000 maddr=b2000000 type=0 len=16777216 index=0 first_map=1

pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:03.0][Offset:30h][Length:4]

pt_ioport_map: e_phys=c200 pio_base=1000 len=128 index=5 first_map=1

mapping vram to f0000000 - f0400000

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.

platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.

track_dirty_vram(f0000000, 26) failed (-1, 22)

track_dirty_vram(f0000000, 26) failed (-1, 22)

track_dirty_vram(f0000000, 26) failed (-1, 22)

track_dirty_vram(f0000000, 26) failed (-1, 22)

 

Many Thanks,

Tim

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel