Bug 1678311 - [pc] No "DEVICE_DELETED" event in qmp after "device_del"
Summary: [pc] No "DEVICE_DELETED" event in qmp after "device_del"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: 8.0
Hardware: Unspecified
OS: Windows
high
unspecified
Target Milestone: rc
: ---
Assignee: Julia Suvorova
QA Contact: qing.wang
URL:
Whiteboard:
Depends On: 1677105 1678290 1754756
Blocks: 1744438
TreeView+ depends on / blocked
 
Reported: 2019-02-18 13:30 UTC by Xueqiang Wei
Modified: 2021-08-16 01:52 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1678290
: 1810858 (view as bug list)
Environment:
Last Closed: 2021-08-15 07:26:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
debug info (810.02 KB, application/gzip)
2019-11-21 06:04 UTC, qing.wang
no flags Details
debug info (1.81 MB, application/gzip)
2019-12-10 09:22 UTC, qing.wang
no flags Details

Comment 1 Xueqiang Wei 2019-02-18 13:34:49 UTC
How reproducible:
8/150

Host:
kernel-4.18.0-67.el8.x86_64
qemu-kvm-2.12.0-61.module+el8+2786+5afd5ae3

Guest:
windows2019
virtio-win-prewhql-0.1-163.iso

Comment 3 Xueqiang Wei 2019-02-21 06:26:44 UTC
unplug virtio-blk disk hit this issue, downgrade viostor to virtio-win-prewhql-0.1-160 and retest on windows10 and windows2019, also hit this issue.


Details:

Host:
kernel-4.18.0-68.el8.x86_64
qemu-kvm-2.12.0-61.module+el8+2786+5afd5ae3


Guest:
Windows10 x86_64
Windows2019

guest system disk is virtio-scsi disk, vioscsi version is virtio-win-prewhql-0.1-163
guest data disk is virio-blk disk, viostor version is virtio-win-prewhql-0.1-160

Comment 4 Ademar Reis 2019-02-25 16:17:39 UTC
See also bug 1669931 and bug 1523017, it might be a windows driver issue.

Comment 8 Xueqiang Wei 2019-04-01 06:03:27 UTC
Markus commented on fast train bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1678290#c9

Comment 9 John Ferlan 2019-04-02 13:17:05 UTC
NB: Since Gal got assigned bz 1678290, I've reassigned this and bz 1677105 to him in order to keep the 3 bugs "together" (similarly altered the priority as well).

Comment 10 Xueqiang Wei 2019-07-03 06:03:22 UTC
Change the priority to high since it's a normal use case and easy to reproduce.

Related comment from Markus here: https://bugzilla.redhat.com/show_bug.cgi?id=1678290#c9

Comment 13 Ademar Reis 2019-09-20 18:47:47 UTC
In bug 1678290 (from where this is cloned) the component is virtio-win, while here it's qemu-kvm-rhev. I'm not sure if this is intentional or a leftover from the clone... Also there, the problem can't be reproduced with libvirt, so this should not be affecting customers, therefore priority=medium. See https://bugzilla.redhat.com/show_bug.cgi?id=1678290#c33 for details.

Comment 16 qing.wang 2019-11-21 06:04:35 UTC
Created attachment 1638323 [details]
debug info

Comment 18 qing.wang 2019-12-10 09:22:01 UTC
Created attachment 1643555 [details]
debug info

Comment 20 Ademar Reis 2020-02-05 22:54:18 UTC
QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks

Comment 29 qing.wang 2020-08-18 07:07:15 UTC
Hit same issue with automation:
{'kvm_version': '4.18.0-214.el8.x86_64', 'qemu_version': 'qemu-kvm-5.0.0-0.module+el8.3.0+6620+5d5e1420.x86_64'}

python ConfigTest.py --testcase=block_hotplug.block_virtio.fmt_qcow2.default.with_plug.with_repetition.one_pci.i440fx --iothread_scheme=roundrobin --nr_iothreads=2 --platform=x86_64 --guestname=Win10 --driveformat=virtio_scsi --nicmodel=virtio_net --imageformat=qcow2 --machines=i440fx --customsparams="qemu_force_use_drive_expression = no\nimage_aio=threads\ncd_format=ide" --clone=no

Comment 33 qing.wang 2021-01-19 09:03:58 UTC
Hit same issue on {'kvm_version': '4.18.0-262.el8.x86_64', 'qemu_version': 'qemu-kvm-5.2.0-2.module+el8.4.0+9186+ec44380f.x86_64'}


python ConfigTest.py --testcase=block_hotplug.block_virtio.fmt_qcow2.default.with_plug.with_repetition.one_pci.i440fx --iothread_scheme=roundrobin --nr_iothreads=2 --platform=x86_64 --guestname=Win10 --driveformat=virtio_scsi --nicmodel=virtio_net --imageformat=qcow2 --machines=i440fx --customsparams="vm_mem_limit = 12G\nimage_aio=threads\ncd_format=ide"

http://fileshare.englab.nay.redhat.com/pub/section2/images_backup/qlogs/%5b8.4-AV%5d-9-PC+Seabios+Win10+Qcow2+Virtio_scsi+Local+aio_threads+qemu-5.2/test-results/022-Host_RHEL.m8.u4.product_av.qcow2.virtio_scsi.up.virtio_net.Guest.Win10.x86_64.io-github-autotest-qemu.block_hotplug.block_virtio.fmt_qcow2.with_plug.with_repetition.one_pci/

Comment 37 RHEL Program Management 2021-08-15 07:26:50 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 38 qing.wang 2021-08-16 01:52:06 UTC
QE agree to close, this bug looks like related to windows guest, 
windows hotplug-unplug issue is tracked by Bug 1833187 - [virtio-win][viostor+vioscsi] Disk still display in guest after hotunplug .


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