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:
Support of tcp option should be added for chardev-add from QMP
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.3.0-31.el7.x86_64
How reproducible:
more than 10 times
Steps to Reproduce:
1.boot up a guest and try to add a chardev with socket backend with *tcp* option
2.
3.
Actual results:
The chardev can not be added to guest.
Expected results:
QE have this command for socket backend with *unix* option and it works well
{"execute":"chardev-
add","arguments":{"id":"channel0","backend":{"type":"socket","data":{"addr":
{"type":"unix", "data": {"path": "/tmp/mm"}}}}}}
Additional info:
There's no useful information in QE's hand for this cmd even if QE checking source code or ask it for Libvirt QE.So please have a look.Many thanks!
Hi Developer,
Research the issue again,this command should work
{"execute":"chardev-add","arguments":{"id":"charserial1","backend":{"type":"socket","data":{"addr":{"type":"inet","data":{"host":"0.0.0.0","port":"2445"}},"wait":false,"telnet":false,"server": true}}}}
But we always use *tcp* option but not *inet*.
Best Regards,
Min Deng
Comment 4Markus Armbruster
2016-02-17 18:42:09 UTC
Your bug report lacks a reproducer. Without one, I'm reduced to guessing. Guessing makes me grumpy.
I'm guessing you're trying to use the command from comment#2, except with "type": "tcp" instead of "type": "inet". That's rejected with a fairly clear error message:
{"error": {"class": "GenericError", "desc": "Invalid parameter 'tcp'"}}
Valid address types are "inet" (address family AF_INET or AF_INET6), "unix" (address family AF_UNIX), and "fd" (a file descriptor received with getfd). The command given in comment#2 is a valid example of type "inet".
If my guess is correct, you've since found out how this thing works, and your bug can be closed NOTABUG.
If it isn't, please provide a reproducer. Stick to the template step 1, 2, 3, actual results, expected results. Give actual commands and actual output, not vague descriptions. Thanks.
(In reply to Markus Armbruster from comment #4)
> Your bug report lacks a reproducer. Without one, I'm reduced to guessing.
> Guessing makes me grumpy.
>
> I'm guessing you're trying to use the command from comment#2, except with
> "type": "tcp" instead of "type": "inet". That's rejected with a fairly
> clear error message:
>
> {"error": {"class": "GenericError", "desc": "Invalid parameter 'tcp'"}}
>
> Valid address types are "inet" (address family AF_INET or AF_INET6), "unix"
> (address family AF_UNIX), and "fd" (a file descriptor received with getfd).
> The command given in comment#2 is a valid example of type "inet".
>
> If my guess is correct, you've since found out how this thing works, and
> your bug can be closed NOTABUG.
>
> If it isn't, please provide a reproducer. Stick to the template step 1, 2,
> 3, actual results, expected results. Give actual commands and actual
> output, not vague descriptions. Thanks.
Thanks for your detail reply and the issues has been resolved,so close it.
Description of problem: Support of tcp option should be added for chardev-add from QMP Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.3.0-31.el7.x86_64 How reproducible: more than 10 times Steps to Reproduce: 1.boot up a guest and try to add a chardev with socket backend with *tcp* option 2. 3. Actual results: The chardev can not be added to guest. Expected results: QE have this command for socket backend with *unix* option and it works well {"execute":"chardev- add","arguments":{"id":"channel0","backend":{"type":"socket","data":{"addr": {"type":"unix", "data": {"path": "/tmp/mm"}}}}}} Additional info: There's no useful information in QE's hand for this cmd even if QE checking source code or ask it for Libvirt QE.So please have a look.Many thanks!