Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem: info qtree still got virtio rng device after hot unplug it Version-Release number of selected component (if applicable): Host: qemu-kvm-rhev-debuginfo-2.1.0-4.el7.x86_64 ipxe-roms-qemu-20130517-5.gitc4bce43.el7.noarch qemu-kvm-rhev-2.1.0-4.el7.x86_64 qemu-img-rhev-2.1.0-4.el7.x86_64 qemu-kvm-common-rhev-2.1.0-4.el7.x86_64 qemu-kvm-tools-rhev-2.1.0-4.el7.x86_64 kernel-3.10.0-169.el7.x86_64 Guest: kernel-3.10.0-169.el7.x86_64 How reproducible: always Steps to Reproduce: 1.Boot guest with virtio rng. /usr/libexec/qemu-kvm \ -M pc \ -cpu SandyBridge \ -m 4G \ -smp 4,sockets=2,cores=2,threads=1,maxcpus=160 \ -enable-kvm \ -name rhel7 \ -uuid 990ea161-6b67-47b2-b803-19fb01d30d12 \ -smbios type=1,manufacturer='Red Hat',product='RHEV Hypervisor',version=el6,serial=koTUXQrb,uuid=feebc8fd-f8b0-4e75-abc3-e63fcdb67170 \ -k en-us \ -rtc base=localtime,clock=host,driftfix=slew \ -nodefaults \ -monitor stdio \ -qmp tcp:0:5555,server,nowait \ -boot menu=on \ -bios /usr/share/seabios/bios.bin \ -monitor unix:/tmp/monitor2,server,nowait \ -vga qxl \ -spice port=5900,disable-ticketing \ -usb \ -device usb-tablet,id=tablet0 \ -drive file=/mnt/rhel7-64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=threads \ -device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \ -device virtio-rng-pci,id=rng0 \ 2.Hot unplug virtio rng. { "execute": "device_del","arguments":{"id":"rng0"}} {"return": {}} 3. Actual results: virtio rng device has been remove from guest, but still exist in qemu. (qemu) info qtree ... dev: virtio-rng-pci, id "rng0" max-bytes = 9223372036854775807 (0x7fffffffffffffff) period = 65536 (0x10000) indirect_desc = true event_idx = true addr = 05.0 romfile = "" rombar = 1 (0x1) multifunction = false command_serr_enable = true class Class 00ff, addr 00:05.0, pci id 1af4:1005 (sub 1af4:0004) bar 0: i/o at 0x1000 [0x101f] bus: virtio-bus type virtio-pci-bus dev: virtio-rng-device, id "" max-bytes = 9223372036854775807 (0x7fffffffffffffff) period = 65536 (0x10000) (qemu) info pci ... Bus 0, device 5, function 0: Class 0255: PCI device 1af4:1005 IRQ 10. BAR0: I/O at 0xc0a0 [0xc0bf]. id "rng0" Expected results: virtio rng device has been remove from "info pci" and "info qtree" Additional info: Guest with kernel-3.10.0-123.el7.x86_64 not hit this problem. If this is expected or my steps was wrong please correct me, thanks!