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:
Images lost connectivity with bridge start VMs
Version-Release number of selected component (if applicable):
RHEL 7.2
[root@kvm02 log]# rpm -qa | grep kvm
libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64
qemu-kvm-common-1.5.3-105.el7_2.7.x86_64
qemu-kvm-1.5.3-105.el7_2.7.x86_64
root@kvm02 log]# uname -an
Linux kvm02.tam.local 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 9 10:09:10 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
How reproducible:
Steps to Reproduce:
1. VMs associate to bridge created in OS
2. Start VMs, after start 3 vms
3. Connectivity go down
Sep 01 15:25:51 kvm02.tam.local kernel: br1: port 1(enp5s0) entered disabled state
Sep 01 15:25:51 kvm02.tam.local kernel: device enp5s0 left promiscuous mode
Sep 01 15:25:42 kvm02.tam.local kernel: br1: port 2(vnet0) entered disabled state
Sep 01 15:25:42 kvm02.tam.local kernel: br1: port 1(enp5s0) entered disabled state
Actual results:
Bridge go down
Expected results:
VMs don't lose connectivity when use linux bridge
Additional info:
(In reply to jason wang from comment #5)
> Hi:
>
> Several questions:
>
> - Can you reproduce the issue for refent qemu-kvm/kernel?
> - What's the qemu cli or libvirt XML for launching guest?
>
> Thanks
Hi, it seems the issue was a hardware.
Nic are not allowed to use virtualisation