RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1432891 - The device hot pluged to pci-bridge doesn't show up
Summary: The device hot pluged to pci-bridge doesn't show up
Keywords:
Status: CLOSED DUPLICATE of bug 1436549
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.4
Hardware: ppc64le
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Marcel Apfelbaum
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-16 10:42 UTC by Zhengtong
Modified: 2017-04-03 00:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-03 00:56:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Zhengtong 2017-03-16 10:42:28 UTC
Description of problem:
Devices hotplugged to pci-bridge doesn't show up

Version-Release number of selected component (if applicable):
Host: 3.10.0-589.el7.ppc64le
Guest: 3.10.0-603.el7.ppc64le
qemu-kvm-rhev-2.8.0-5.el7
SLOF-20160223-6.gitdbbfda4.el7.noarch

How reproducible:
3/3

Steps to Reproduce:
1.Boot a guest with a pci-bridge device
/usr/libexec/qemu-kvm 
...
-device pci-bridge,id=pbr,chassis_nr=1 \
...

2.Hotplug a virtio-blk-pci device to the pci-bridge device

{"execute":"__com.redhat_drive_add","arguments":{"file":"/home/test.img","format":"qcow2","id":"test"}}

{"execute":"device_add","arguments":{"driver":"virtio-blk-pci","drive":"test","bus":"pbr","addr":"0xa","id":"blk_dev1"}}

3.Check the new added device inside guest

Actual results:
The device hotplugged didn't show up in the guest or "info qtree" in hmp
[root@localhost ~]# lsblk 
lsblk
NAME                      MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda                         8:0    0  20G  0 disk 
├─sda1                      8:1    0   4M  0 part 
├─sda2                      8:2    0   1G  0 part /boot
└─sda3                      8:3    0  19G  0 part 
  ├─rhel_dhcp70--156-root 253:0    0  17G  0 lvm  /
  └─rhel_dhcp70--156-swap 253:1    0   2G  0 lvm  [SWAP]
[root@localhost ~]# ls /dev/vd* 
ls /dev/vd*
ls: cannot access /dev/vd*: No such file or directory

No new device

Expected results:
It show shows up in guest and "info qtree"

Additional info:
Works on x86 platform

Comment 2 David Gibson 2017-03-31 06:04:21 UTC
Marcel, see anlysis of what's going on in bug 1436549.  Basic problem is that qemu is trying to use the standard hotplug handler, but that won't work for a PAPR guest.

Comment 3 Marcel Apfelbaum 2017-03-31 12:42:17 UTC
(In reply to David Gibson from comment #2)
> Marcel, see anlysis of what's going on in bug 1436549.  Basic problem is
> that qemu is trying to use the standard hotplug handler, but that won't work
> for a PAPR guest.

Hi David,

It seems like a duplicate of the bug you mentioned.
I agree that disabling shpc was a "bold" move, but an error
is better than a silent bug.
I am not sure how I can help, my ppc knowledge is close to 0.
Any thoughts?

Thanks,
Macel

Comment 4 David Gibson 2017-04-03 00:56:34 UTC
Yes, I agree the error message is better behaviour.

So, I'll close this as a duplicate of bug 1436549.  I'll follow up there with some more questions.

*** This bug has been marked as a duplicate of bug 1436549 ***


Note You need to log in before you can comment on or make changes to this bug.