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.
Need to add the ability for qpid to talk AMQP over interfaces other than ip. virtio-serial is a transport that allows guest to host communication for kvm guests. virtio-serial transport is necessary to support Matahari on KVM guests in RHEV to talk to vdsm running on the host. This will enable Matahari to be the 'RHEV guest agent' on both Windows and RHEL.
Comment 1RHEL Program Management
2011-01-07 04:39:02 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
This request was erroneously denied for the current release of Red Hat
Enterprise Linux. The error has been fixed and this request has been
re-proposed for the current release.
Created attachment 509822[details]
Description of a virtioserial channel that tunnels QPID connections.
This version uses proxy processes on each end of the virtioserial tunnel; the protocol is not bundled in qpid as a transport. This transport is useful for any service port and not just qpid's 5672.
> This version uses proxy processes on each end of the virtioserial tunnel; the
> protocol is not bundled in qpid as a transport. This transport is useful for
> any service port and not just qpid's 5672.
If that's the case, should this be part of qpid-cpp package or do we need to consider bundling with qemu-kvm package and/or creating a completely new package?
Dor, do you have any thoughts here?
Good question, for the time being virt-agent will have its own protocol. Not sure there are other users. Maybe the RHEV agent will be interested of sharing this.
Qemu-kvm might bundle the host site of it but the guest side will require a separate package so maybe qpid-cpp or new one will be needed.