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.
Created attachment 528617[details]
Screenshot of network config settings
Description of problem:
There seems to be no way to create the equivalent of following configuration:
eth0 \
eth1 -+-- bond0 +------------- rhevm (bridge)
+\- vlan50 --- bvlan50 (bridge)
|\- vlan51 --- bvlan51 (bridge)
\- vlan52 --- bvlan52 (bridge)
Near as I can tell, it's only possible to have a single Network on a single physical interface (or bond).
Is this a design restriction, a documentation limitation or a misunderstanding on my part?
Version-Release number of selected component (if applicable):
RHEV Manager for Servers and Desktops: 3.0.0_0001-41.el6
Red Hat Enterprise Virtualization Hypervisor Hosts:
OS Version - RHEL - 6Server - 6.1.0.2.el6 VDSM Version - 3.0.96.1
Additional info:
I tried creating the networks by hand on the RHEL hosts as described above, but RHEV-M doesn't understand that they're there.
Comment 3RHEL Program Management
2011-10-18 13:08:47 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.
you can set up rhev-m and other logical networks on the same bridge only if all are vlans (i.e., rhev-m would also have to be a vlan'd network).
GSS has a KB on how to set this up.
known issue on supporting this for future versions
I'm not looking to put more than one logical network on the same bridge, I'm trying to have a single bonded interface with multiple VLAN subinterfaces. Each one (the untagged and each subinterface) would have its own bridge.
Unfortunately, that is not supported, either. It was intentionally blocked since we did not want packets from a vlan'ed broadcust domain to spill over into an unrelated network (rhevm in your case). It is understood that your wiring may make sense if untrusted VMs are not going to going to be attached to the "rhevm" network, and if the latter network can spare the bandwidth.
We may consider this topology in the next version if it has an important use-case.
Created attachment 528617 [details] Screenshot of network config settings Description of problem: There seems to be no way to create the equivalent of following configuration: eth0 \ eth1 -+-- bond0 +------------- rhevm (bridge) +\- vlan50 --- bvlan50 (bridge) |\- vlan51 --- bvlan51 (bridge) \- vlan52 --- bvlan52 (bridge) Near as I can tell, it's only possible to have a single Network on a single physical interface (or bond). Is this a design restriction, a documentation limitation or a misunderstanding on my part? Version-Release number of selected component (if applicable): RHEV Manager for Servers and Desktops: 3.0.0_0001-41.el6 Red Hat Enterprise Virtualization Hypervisor Hosts: OS Version - RHEL - 6Server - 6.1.0.2.el6 VDSM Version - 3.0.96.1 Additional info: I tried creating the networks by hand on the RHEL hosts as described above, but RHEV-M doesn't understand that they're there.