blob: 8b043b7181bb872ce0f01d16579603846347c36b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
device: 0.778
hypervisor: 0.777
kernel: 0.658
ppc: 0.655
mistranslation: 0.652
architecture: 0.582
network: 0.571
peripherals: 0.553
semantic: 0.546
graphic: 0.540
vnc: 0.532
socket: 0.511
risc-v: 0.482
performance: 0.476
i386: 0.469
register: 0.468
permissions: 0.443
x86: 0.440
PID: 0.437
boot: 0.418
VMM: 0.399
TCG: 0.394
user-level: 0.389
files: 0.376
KVM: 0.354
virtual: 0.350
debug: 0.338
assembly: 0.286
arm: 0.231
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.]
|