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.
Descriptionleidwang@redhat.com
2022-10-28 02:05:46 UTC
Description of problem:
fwcfg can not be disabled
Version-Release number of selected component (if applicable):
qemu-kvm-7.1.0-2.el9.x86_64
kernel-5.14.0-162.6.1.el9_1.x86_64
prewhql-227
How reproducible:
100%
Steps to Reproduce:
1.boot up a guest
/usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1' \
-sandbox on \
-machine q35,memory-backend=mem-machine_mem \
-device pcie-root-port,id=pcie-root-port-0,multifunction=on,bus=pcie.0,addr=0x1,chassis=1 \
-device pcie-pci-bridge,id=pcie-pci-bridge-0,addr=0x0,bus=pcie-root-port-0 \
-nodefaults \
-device VGA,bus=pcie.0,addr=0x2 \
-m 30720 \
-object '{"qom-type": "memory-backend-ram", "size": 32212254720, "id": "mem-machine_mem"}' \
-smp 40,maxcpus=40,cores=20,threads=1,dies=1,sockets=2 \
-cpu 'Icelake-Server',ds=on,ss=on,dtes64=on,vmx=on,pdcm=on,hypervisor=on,tsc-adjust=on,avx512ifma=on,sha-ni=on,rdpid=on,fsrm=on,md-clear=on,stibp=on,arch-capabilities=on,xsaves=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,rdctl-no=on,ibrs-all=on,skip-l1dfl-vmentry=on,mds-no=on,pschange-mc-no=on,tsx-ctrl=on,hle=off,rtm=off,mpx=off,intel-pt=off,hv_stimer,hv_synic,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,kvm_pv_unhalt=on \
-chardev socket,path=/var/tmp/avocado_djl3f8ou/monitor-qmpmonitor1-20221128-213026-Tlf2OHxi,server=on,wait=off,id=qmp_id_qmpmonitor1 \
-mon chardev=qmp_id_qmpmonitor1,mode=control \
-chardev socket,path=/var/tmp/avocado_djl3f8ou/monitor-catch_monitor-20221128-213026-Tlf2OHxi,server=on,wait=off,id=qmp_id_catch_monitor \
-mon chardev=qmp_id_catch_monitor,mode=control \
-device pvpanic,ioport=0x505,id=idnk1MzQ \
-chardev socket,path=/var/tmp/avocado_djl3f8ou/serial-serial0-20221128-213026-Tlf2OHxi,server=on,wait=off,id=chardev_serial0 \
-device isa-serial,id=serial0,chardev=chardev_serial0 \
-chardev socket,id=seabioslog_id_20221128-213026-Tlf2OHxi,path=/var/tmp/avocado_djl3f8ou/seabios-20221128-213026-Tlf2OHxi,server=on,wait=off \
-device isa-debugcon,chardev=seabioslog_id_20221128-213026-Tlf2OHxi,iobase=0x402 \
-device pcie-root-port,id=pcie-root-port-1,port=0x1,addr=0x1.0x1,bus=pcie.0,chassis=2 \
-device qemu-xhci,id=usb1,bus=pcie-root-port-1,addr=0x0 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-device pcie-root-port,id=pcie-root-port-2,port=0x2,addr=0x1.0x2,bus=pcie.0,chassis=3 \
-device '{"id": "virtio_scsi_pci0", "driver": "virtio-scsi-pci", "bus": "pcie-root-port-2", "addr": "0x0"}' \
-blockdev '{"node-name": "file_image1", "driver": "file", "auto-read-only": true, "discard": "unmap", "aio": "threads", "filename": "/home/kvm_autotest_root/images/win10-32-virtio-scsi.qcow2", "cache": {"direct": true, "no-flush": false}}' \
-blockdev '{"node-name": "drive_image1", "driver": "qcow2", "read-only": false, "cache": {"direct": true, "no-flush": false}, "file": "file_image1"}' \
-device '{"driver": "scsi-hd", "id": "image1", "drive": "drive_image1", "write-cache": "on"}' \
-device pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \
-device virtio-net-pci,mac=9a:cf:03:f7:e3:57,id=idp17iP1,netdev=idzZtgMU,bus=pcie-root-port-3,addr=0x0 \
-netdev tap,id=idzZtgMU,vhost=on \
-monitor stdio \
-vnc :0 \
-device vmcoreinfo \
-rtc base=localtime,clock=host,driftfix=slew \
-boot menu=off,order=cdn,once=c,strict=off \
-enable-kvm \
-device pcie-root-port,id=pcie_extra_root_port_0,multifunction=on,bus=pcie.0,addr=0x3,chassis=5
2.try to disable fwcfg driver via device manager or cmd
Actual results:
The disable button in device is gray,and also can not disable the
driver by cmd
Expected results:
the driver can be disabled
Additional info:
Comment 1Yvugenfi@redhat.com
2022-11-15 08:27:08 UTC
Is the issue reproducible on every Windows OS version or only on a specific one? Is there a difference between 32 and 64bit versions?
Comment 2leidwang@redhat.com
2022-11-29 05:32:31 UTC
(In reply to Yvugenfi from comment #1)
> Is the issue reproducible on every Windows OS version or only on a specific
> one? Is there a difference between 32 and 64bit versions?
Hi Yan,
sorry for the delay.
The issue is not only for some specific Windows os version, and it can be reproduce on 32 and 64 bits Windows.
Thanks,
Leidong
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (virtio-win bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2451
Description of problem: fwcfg can not be disabled Version-Release number of selected component (if applicable): qemu-kvm-7.1.0-2.el9.x86_64 kernel-5.14.0-162.6.1.el9_1.x86_64 prewhql-227 How reproducible: 100% Steps to Reproduce: 1.boot up a guest /usr/libexec/qemu-kvm \ -name 'avocado-vt-vm1' \ -sandbox on \ -machine q35,memory-backend=mem-machine_mem \ -device pcie-root-port,id=pcie-root-port-0,multifunction=on,bus=pcie.0,addr=0x1,chassis=1 \ -device pcie-pci-bridge,id=pcie-pci-bridge-0,addr=0x0,bus=pcie-root-port-0 \ -nodefaults \ -device VGA,bus=pcie.0,addr=0x2 \ -m 30720 \ -object '{"qom-type": "memory-backend-ram", "size": 32212254720, "id": "mem-machine_mem"}' \ -smp 40,maxcpus=40,cores=20,threads=1,dies=1,sockets=2 \ -cpu 'Icelake-Server',ds=on,ss=on,dtes64=on,vmx=on,pdcm=on,hypervisor=on,tsc-adjust=on,avx512ifma=on,sha-ni=on,rdpid=on,fsrm=on,md-clear=on,stibp=on,arch-capabilities=on,xsaves=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,rdctl-no=on,ibrs-all=on,skip-l1dfl-vmentry=on,mds-no=on,pschange-mc-no=on,tsx-ctrl=on,hle=off,rtm=off,mpx=off,intel-pt=off,hv_stimer,hv_synic,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,kvm_pv_unhalt=on \ -chardev socket,path=/var/tmp/avocado_djl3f8ou/monitor-qmpmonitor1-20221128-213026-Tlf2OHxi,server=on,wait=off,id=qmp_id_qmpmonitor1 \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,path=/var/tmp/avocado_djl3f8ou/monitor-catch_monitor-20221128-213026-Tlf2OHxi,server=on,wait=off,id=qmp_id_catch_monitor \ -mon chardev=qmp_id_catch_monitor,mode=control \ -device pvpanic,ioport=0x505,id=idnk1MzQ \ -chardev socket,path=/var/tmp/avocado_djl3f8ou/serial-serial0-20221128-213026-Tlf2OHxi,server=on,wait=off,id=chardev_serial0 \ -device isa-serial,id=serial0,chardev=chardev_serial0 \ -chardev socket,id=seabioslog_id_20221128-213026-Tlf2OHxi,path=/var/tmp/avocado_djl3f8ou/seabios-20221128-213026-Tlf2OHxi,server=on,wait=off \ -device isa-debugcon,chardev=seabioslog_id_20221128-213026-Tlf2OHxi,iobase=0x402 \ -device pcie-root-port,id=pcie-root-port-1,port=0x1,addr=0x1.0x1,bus=pcie.0,chassis=2 \ -device qemu-xhci,id=usb1,bus=pcie-root-port-1,addr=0x0 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -device pcie-root-port,id=pcie-root-port-2,port=0x2,addr=0x1.0x2,bus=pcie.0,chassis=3 \ -device '{"id": "virtio_scsi_pci0", "driver": "virtio-scsi-pci", "bus": "pcie-root-port-2", "addr": "0x0"}' \ -blockdev '{"node-name": "file_image1", "driver": "file", "auto-read-only": true, "discard": "unmap", "aio": "threads", "filename": "/home/kvm_autotest_root/images/win10-32-virtio-scsi.qcow2", "cache": {"direct": true, "no-flush": false}}' \ -blockdev '{"node-name": "drive_image1", "driver": "qcow2", "read-only": false, "cache": {"direct": true, "no-flush": false}, "file": "file_image1"}' \ -device '{"driver": "scsi-hd", "id": "image1", "drive": "drive_image1", "write-cache": "on"}' \ -device pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \ -device virtio-net-pci,mac=9a:cf:03:f7:e3:57,id=idp17iP1,netdev=idzZtgMU,bus=pcie-root-port-3,addr=0x0 \ -netdev tap,id=idzZtgMU,vhost=on \ -monitor stdio \ -vnc :0 \ -device vmcoreinfo \ -rtc base=localtime,clock=host,driftfix=slew \ -boot menu=off,order=cdn,once=c,strict=off \ -enable-kvm \ -device pcie-root-port,id=pcie_extra_root_port_0,multifunction=on,bus=pcie.0,addr=0x3,chassis=5 2.try to disable fwcfg driver via device manager or cmd Actual results: The disable button in device is gray,and also can not disable the driver by cmd Expected results: the driver can be disabled Additional info: