summaryrefslogtreecommitdiffstats
path: root/mailinglist/output_launchpad/1463463
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-05-30 14:51:13 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-05-30 14:51:13 +0000
commit225caa38269323af1bfc2daadff5ec8bd930747f (patch)
treee0a5fefde9ee100ba6f32fb36de6707490e4164e /mailinglist/output_launchpad/1463463
parent904141bfb8d5385b75eb3b7afec1dcda89af65a7 (diff)
downloademulator-bug-study-225caa38269323af1bfc2daadff5ec8bd930747f.tar.gz
emulator-bug-study-225caa38269323af1bfc2daadff5ec8bd930747f.zip
add mailinglist scraper results
Diffstat (limited to 'mailinglist/output_launchpad/1463463')
-rw-r--r--mailinglist/output_launchpad/146346322
1 files changed, 22 insertions, 0 deletions
diff --git a/mailinglist/output_launchpad/1463463 b/mailinglist/output_launchpad/1463463
new file mode 100644
index 00000000..126bbfac
--- /dev/null
+++ b/mailinglist/output_launchpad/1463463
@@ -0,0 +1,22 @@
+PCI devices on PCI to PCI bridges stopped being accessable from Xen with QEMU 2.3.0
+
+The change set:
+
+commit 3996e85c1822e05c50250f8d2d1e57b6bea1229d
+Author: Paul Durrant <email address hidden>
+Date: Tue Jan 20 11:06:19 2015 +0000
+
+ Xen: Use the ioreq-server API when available
+...
+
+Added calls to xen_map_pcidev() when available. However these call are only done at startup, not when the guest configures the PCI to PCI bridge. So Xen 4.5.0 (which has these) using a QEMU 2.3.0 or later can no longer access PCI devices that are not on a root bridge.
+
+Since Xen's tool stack does not know about PCI to PCI bridges, a config that shows this issue also requires the correct Linux kernel argument "pci=assign-busses" is used.
+
+
+
+Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+