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] Re: with Xen4 config -> (pci-passthrough-strict-check no), D

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: with Xen4 config -> (pci-passthrough-strict-check no), DomU init reports "Error: pci: PCI Backend and pci-stub don't own device"
From: 0bo0 <0.bugs.only.0@xxxxxxxxx>
Date: Fri, 29 Jan 2010 14:36:28 -0800
Delivery-date: Fri, 29 Jan 2010 14:36:47 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=+RZEgQpBoweVktCdkf3aJOplrHvYB4RUU6Q5RDAfJsI=; b=Z9vjyFwSBTmx17dyv/aJcjgUvw6vgxUsIIftUUp8n1Wd+b40289ObdRs64fgiXtEVO y/lxVC1Eq2tQaBNIEI6MWQX1CY2HhhDjf3G9EdBI7R/+aJkQXQ6QF+LyWdRyqjkNztNv kgiZce7QmbWzThd+pHd6nptf4hcsVUGym9O5o=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Y0XZItK2RqrlcduLilC9NqmO8ZIWGRGnBl2qd31hjd5sM+YvTyyVCyqEa1whpnB7yl plmHuMYAdiHXZYHGtxKbF0YVH3rCiEiX8zbg/Snb92znysd5lbpBRUOaHNcnUqizinjG bZOnr2Fr/+ytxmwnj0dlM8keNQwQFrrJJ+MDQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <c67eed301001291410w2c926730s6c2d7ce5e9c5d46b@xxxxxxxxxxxxxx>
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>
References: <c67eed301001291410w2c926730s6c2d7ce5e9c5d46b@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
checking @ source,

...
 # Test whether the device is owned by pciback or pci-stub.
        try:
            pci_device = PciDevice(new_dev)
        except Exception, e:
            raise VmError("pci: failed to locate device and "+
                    "parse its resources - "+str(e))
        if pci_device.driver!='pciback' and pci_device.driver!='pci-stub':
            raise VmError(("pci: PCI Backend and pci-stub don't own device %s")\
                            %pci_device.name)
...

verifying the device is being seized @ startup; looks not to be :-/

...
dmesg | egrep "4:06|4:07|pciback"
...
[    0.216794] PCI: 0000:04:07.0 has been reserved for guest domain.
[    0.216794] PCI: 0000:04:06.0 has been reserved for guest domain.
[    0.260161] pci 0000:04:06.0: reg 10: [mem 0xfbfe0000-0xfbffffff]
[    0.260171] pci 0000:04:06.0: reg 14: [mem 0xfbfc0000-0xfbfdffff]
[    0.260180] pci 0000:04:06.0: reg 18: [io  0xec00-0xec3f]
[    0.260214] pci 0000:04:06.0: reg 30: [mem 0xfbfa0000-0xfbfbffff pref]
[    0.260221] pci 0000:04:06.0: Disabling memory decoding and
releasing memory resources.
[    0.260262] pci 0000:04:06.0: PME# supported from D0 D3hot D3cold
[    0.260268] pci 0000:04:06.0: PME# disabled
[    0.260340] pci 0000:04:07.0: reg 10: [mem 0xfbf9fc00-0xfbf9fc7f 64bit]
[    0.260357] pci 0000:04:07.0: reg 18: [mem 0xfbf90000-0xfbf97fff 64bit]
[    0.260367] pci 0000:04:07.0: reg 20: [io  0xe880-0xe88f]
[    0.260385] pci 0000:04:07.0: reg 30: [mem 0xfbf00000-0xfbf7ffff pref]
[    0.260391] pci 0000:04:07.0: Disabling memory decoding and
releasing memory resources.
[    0.260434] pci 0000:04:07.0: supports D1 D2
[    0.273957] pci 0000:04:07.0: BAR 6: assigned [mem
0xf0100000-0xf017ffff pref]
[    0.273961] pci 0000:04:06.0: BAR 0: assigned [mem 0xfbf00000-0xfbf1ffff]
[    0.273972] pci 0000:04:06.0: BAR 0: set to [mem
0xfbf00000-0xfbf1ffff] (PCI address [0xfbf00000-0xfbf1ffff]
[    0.273977] pci 0000:04:06.0: BAR 1: assigned [mem 0xfbf20000-0xfbf3ffff]
[    0.273985] pci 0000:04:06.0: BAR 1: set to [mem
0xfbf20000-0xfbf3ffff] (PCI address [0xfbf20000-0xfbf3ffff]
[    0.273991] pci 0000:04:06.0: BAR 6: assigned [mem
0xf0180000-0xf019ffff pref]
[    0.273995] pci 0000:04:07.0: BAR 2: assigned [mem
0xfbf40000-0xfbf47fff 64bit]
[    0.274008] pci 0000:04:07.0: BAR 2: set to [mem
0xfbf40000-0xfbf47fff 64bit] (PCI address [0xfbf40000-0xfbf47fff]
[    0.274013] pci 0000:04:07.0: BAR 0: assigned [mem
0xfbf48000-0xfbf4807f 64bit]
[    0.274026] pci 0000:04:07.0: BAR 0: set to [mem
0xfbf48000-0xfbf4807f 64bit] (PCI address [0xfbf48000-0xfbf4807f]
[    5.562894] sata_sil24 0000:04:07.0: version 1.1
[    5.562913] sata_sil24 0000:04:07.0: enabling device (019d -> 019f)
[    5.562933] sata_sil24 0000:04:07.0: PCI INT A -> GSI 21 (level,
low) -> IRQ 21
[   29.932444] pciback 0000:04:06.0: seizing device
[   29.932501] pciback 0000:04:06.0: enabling device (0115 -> 0117)
[   29.932521] pciback 0000:04:06.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[   29.932528] pciback 0000:04:06.0: PCI INT A disabled

dropping back to

  uname -ri
    2.6.31.12-2-xen x86_64


the dmesg output and the DomU init results are the same ... no-go.

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