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 xiaodwan from comment #0)
> This also occurs when connecting to a rhel6 guest on rhel7.
I'm not sure what you wanted to say. The guest operating system is really irrelevant here.
And the bug is really useless since you cloned it with all private comments. Please file a new one or clone the existing one, but make sure you remove all irrelevant comments so the the bug description can be public. And don't forget to provide information specific to the rhel7, such as package versions.
Anyway, since it seems like it happens only in some specific scenarios in rhel7, it may be better to file a new bug from scratch describing what works and what doesn't work.
(In reply to Jiri Denemark from comment #1)
> (In reply to xiaodwan from comment #0)
> > This also occurs when connecting to a rhel6 guest on rhel7.
>
> I'm not sure what you wanted to say. The guest operating system is really
> irrelevant here.
>
Hi, This is not about guest OS.
The scenario here is connecting a "listen type='network'" guest on rhel6 from rhel7 by virt-viewer.
If you agree, i want to make the comment #0 public and reopen this bug.
(In reply to xiaodwan from comment #2)
> (In reply to Jiri Denemark from comment #1)
> Hi, This is not about guest OS.
> The scenario here is connecting a "listen type='network'" guest on rhel6
> from rhel7 by virt-viewer.
So the domain is running on a rhel6 host and you are connecting to a virt-viewer running on a rhel7 host, is that right? Does it all work if both the domain and virt-viewer are running on rhel7?
> If you agree, i want to make the comment #0 public and reopen this bug.
No, making it public is easy, but the main point is that comment #0 contains a lot of irrelevant comments because you didn't remove them before saving the clone. And this can't be fixed.
> So the domain is running on a rhel6 host and you are connecting to a
> virt-viewer running on a rhel7 host, is that right?
Yes
> Does it all work if both the domain and virt-viewer are running on rhel7?
This works.
> > If you agree, i want to make the comment #0 public and reopen this bug.
> No, making it public is easy, but the main point is that comment #0 contains
> a lot of irrelevant comments because you didn't remove them before saving
> the clone. And this can't be fixed.
Thanks. I'll file a new bug for the different scenario on rhel7.