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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
|
mistranslation: 0.906
user-level: 0.886
x86: 0.886
peripherals: 0.885
graphic: 0.874
architecture: 0.871
device: 0.853
semantic: 0.843
PID: 0.811
permissions: 0.801
ppc: 0.801
performance: 0.783
debug: 0.753
network: 0.729
hypervisor: 0.705
assembly: 0.674
register: 0.659
files: 0.635
kernel: 0.597
socket: 0.541
vnc: 0.536
i386: 0.532
arm: 0.511
virtual: 0.504
TCG: 0.472
boot: 0.447
risc-v: 0.430
KVM: 0.408
VMM: 0.406
--------------------
x86: 0.896
debug: 0.212
files: 0.059
virtual: 0.036
device: 0.035
PID: 0.034
TCG: 0.028
hypervisor: 0.024
semantic: 0.012
ppc: 0.011
user-level: 0.009
boot: 0.009
VMM: 0.006
risc-v: 0.005
peripherals: 0.005
register: 0.005
socket: 0.005
vnc: 0.005
performance: 0.004
architecture: 0.004
network: 0.004
kernel: 0.003
permissions: 0.003
i386: 0.003
assembly: 0.002
arm: 0.002
graphic: 0.002
mistranslation: 0.001
KVM: 0.000
PXB selected as root bus incorrectly
release: 4c41341af76cfc85b5a6c0f87de4838672ab9f89
qdev_device_add() will search for the "closest" bus possible, and bail out early if that bus is a root bus. pxb devices are considered root buses and so if you either
1. Add a PCI device on the QEMU command line *after* a pxb device, or
2. Add an integrated PCI device (like a watchdog)
#1: -device pxb-pcie,id=cxl.0,bus=pcie.0,bus_nr=52 -device ahci,id=sata0,addr=0x8
#2: -watchdog i6300esb -device pxb-pcie,id=cxl.0,bus=pcie.0,bus_nr=52
The PXB will get selected as the bus (instead of the real root bus) and this will cause an assertion failure with the message like "qemu-system-x86_64: -device ahci,id=sata0,addr=0x8: PCI: Only PCI/PCIe bridges can be plugged into pxb-pcie"
I think this is relatively solvable in the code base by determining if a bus is an expander, and skipping it if so. However, I wonder if it makes more sense to just allow expanders to have endpoint devices.
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).
Thank you and sorry for the inconvenience.
[Expired for QEMU because there has been no activity for 60 days.]
|
