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 1097641[details]
engine, libvirt, vdsm, qemu logs
Description of problem:
When you try to plug/unplug NIC on VM or add additional vNIC the VM goes down as a connection to qemu process is lost
Version-Release number of selected component (if applicable):
How reproducible:
Takes a bit of time, but if you plug/unplug existing vNIC or add, remove vNIC from VM the VM goes down
Steps to Reproduce:
1. Add vNIC to VM
2. Unplug existing vNIC
3. Plug vNIC back
4 Go over above steps several times
Actual results:
VM goes down with error message: Lost connection with qemu process
Expected results:
VM should be up and running
Additional info:
(In reply to Michal Skrivanek from comment #3)
> I didn't see guest side logs but the scenario matches bug 1270717
The RHEL 7.2.z bugzilla is: bug 1279793
Fixed in: kernel-3.10.0-327.2.1.el7
This is almost certainly the same as bug 1270717 / bug 1279793. Please retry with kernel-3.10.0-327.2.1.el7. Note that this bug can cause crashes in either host or guest, so you'll want to update the kernel in both.
This bug do not happen with these new versions on host:
kernel 3.10.0-327.2.1.el7.ppc64le (also on guest)
and libvirt-1.2.17-13.el7_2.2.ppc64le
qemu-2.3.0-31.el7_2.3.ppc64le
Created attachment 1097641 [details] engine, libvirt, vdsm, qemu logs Description of problem: When you try to plug/unplug NIC on VM or add additional vNIC the VM goes down as a connection to qemu process is lost Version-Release number of selected component (if applicable): How reproducible: Takes a bit of time, but if you plug/unplug existing vNIC or add, remove vNIC from VM the VM goes down Steps to Reproduce: 1. Add vNIC to VM 2. Unplug existing vNIC 3. Plug vNIC back 4 Go over above steps several times Actual results: VM goes down with error message: Lost connection with qemu process Expected results: VM should be up and running Additional info: