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/
Home Products Support Community News


[Xen-bugs] [Bug 1565] New: PCI passthrough no longer works after domU sh

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1565] New: PCI passthrough no longer works after domU shutdown.
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sun, 17 Jan 2010 10:11:16 -0800
Delivery-date: Sun, 17 Jan 2010 10:11:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: PCI passthrough no longer works after domU shutdown.
           Product: Xen
           Version: unspecified
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: 2.6.18 dom0
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: nettie@xxxxxxxxxx

Xen version: 3.4.2 x86_64
dom0 and domU kernel (3.4.2 release)

I'm using PCI passthrough to pass an ISDN BRI adapter to an asterisk domU. 

Everything works fine when the domU is started for the first time, lspci
actually shows the presence of the PCI adapter and the services which are using
it are working properly.

If the domU is shutdown and started again the PCI adapter is no longer visible
in the domU, lspci shoes nothing.


/var/log/xen/xend.log shows nothing different in both cases, the PCI adapter
seems to be correctly assigned to the domU.


xm pci-list <domU> shows the adapter correctly assigned to the domU even if
lspci no longer shows it.
domain   bus   slot   func
0x0000  0x0b   0x02    0x0


The only workaround I was able to find is a dom0 reboot.


With older Xen versions (3.1.x) rebooting the domU using the PCI-backed adapter
was causing a spurious interrupt on IRQ#16 and a softcrash of the dom0
(networking no longer working and other issues).

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>