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.
(In reply to Ademar Reis from comment #6)
> QMP usage is not going to be supported in RHEL7 and this bug is harmless
> when using libvirt. Closing as WONTFIX.
Why QMP not be support in rhel7? The libvirt must call for from QMP monitor, maybe you mistaked it to HMP, so reopen it to fix it. Please correct me if any mistake.
Best Regards,
sluo
Hi Sluo,
I can only repeat Ademar's comment 6:
- *direct* QMP usage (ie. talking directly to the qemu monitor over QMP) is not supported in RHEL-7,
- libvirt of course talks to the qemu monitor, using QMP, and that is supported. But libvirt can already handle the duplicate RESET event (this is what Ademar meant with "harmless".
Please consider re-closing. Thanks.
(In reply to Laszlo Ersek from comment #8)
> Hi Sluo,
>
> I can only repeat Ademar's comment 6:
> - *direct* QMP usage (ie. talking directly to the qemu monitor over QMP) is
> not supported in RHEL-7,
> - libvirt of course talks to the qemu monitor, using QMP, and that is
> supported. But libvirt can already handle the duplicate RESET event (this is
> what Ademar meant with "harmless".
>
Yep, sorry for not being clear before and thanks Laszlo for explaining.
Description of problem: Executing "system_reset" command in qmp, two RESET events are reported. Version-Release number of selected component (if applicable): qemu-kvm-1.4.0-2.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. boot up a vm. /root/autotest/autotest-devel/client/tests/kvm/qemu -monitor stdio -enable-kvm -chardev socket,id=seabioslog_id_20130410-113920-4uZvymfO,path=/tmp/seabios-20130410-113920-4uZvymfO,server,nowait -device isa-debugcon,chardev=seabioslog_id_20130410-113920-4uZvymfO,iobase=0x402 -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=0x4 -drive file=./RHEL-Server-6.4-64-virtio.qcow2,if=none,id=drive-virtio-disk1,media=disk,cache=unsafe,snapshot=off,format=qcow2,aio=native -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -device virtio-net-pci,netdev=idiJsfiK,mac=9a:d9:da:db:dc:dd,bus=pci.0,addr=0x3,id=idbJLUxv -netdev tap,id=idiJsfiK,vhost=on -m 4096 -smp 4,maxcpus=4,cores=2,threads=1,sockets=2 -cpu SandyBridge -M pc -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 -vnc :0 -vga cirrus -rtc base=utc,clock=host,driftfix=slew -qmp tcp:0:5234,server,nowait -drive file=./Windows8-ReleasePreview-64bit-English.iso,if=none,id=drive-virtio-disk2,media=cdrom,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-virtio-disk2,id=virtio-disk2 2. telnet host_ip 5234 3. {"execute":"qmp_capabilities"} {"return": {}} { "execute": "system_reset" } {"return": {}} {"timestamp": {"seconds": 1365752070, "microseconds": 703225}, "event": "RESET"} {"timestamp": {"seconds": 1365752070, "microseconds": 783227}, "event": "RESET"} Actual results: Two pieces of RESET event are reported. Expected results: One piece of RESET event is reported. Additional info: Host kernel 3.9.0-0.rc6.50.el7.x86_64