diff options
Diffstat (limited to 'results/classifier/108/other/1463463')
| -rw-r--r-- | results/classifier/108/other/1463463 | 37 |
1 files changed, 37 insertions, 0 deletions
diff --git a/results/classifier/108/other/1463463 b/results/classifier/108/other/1463463 new file mode 100644 index 000000000..96ab0568e --- /dev/null +++ b/results/classifier/108/other/1463463 @@ -0,0 +1,37 @@ +device: 0.778 +network: 0.571 +semantic: 0.546 +graphic: 0.540 +vnc: 0.532 +socket: 0.511 +other: 0.477 +performance: 0.476 +permissions: 0.443 +PID: 0.437 +boot: 0.418 +files: 0.376 +KVM: 0.354 +debug: 0.338 + +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.] + |