Bug 1741390
Summary: | Exclusive check for direct type passthrough mode interface will crash the libvirtd | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | yalzhang <yalzhang> | ||||||
Component: | libvirt | Assignee: | Laine Stump <laine> | ||||||
Status: | CLOSED ERRATA | QA Contact: | yalzhang <yalzhang> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 8.1 | CC: | jdenemar, jtomko, laine, xuzhang | ||||||
Target Milestone: | rc | Keywords: | Regression | ||||||
Target Release: | 8.1 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | libvirt-5.6.0-2.el8 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2019-11-06 07:18:29 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1585087 | ||||||||
Attachments: |
|
Description
yalzhang@redhat.com
2019-08-15 02:36:13 UTC
Please include a backtrace for crash reports: https://libvirt.org/bugs.html#quality Created attachment 1604255 [details]
backtrace for libvirtd crash
Created attachment 1604256 [details]
backtrace, output of br fu
Fix posted upstream: https://www.redhat.com/archives/libvir-list/2019-August/msg00589.html These two patches were pushed upstream. The first is necessary for the bugfix. The second is a small change that was made at the same time that will make any future patches to the same code easier to backport. commit dac697e8d7d6d9a607e61caeeec06b259edf513f Author: Laine Stump <laine> Date: Thu Aug 15 21:52:28 2019 -0400 network: fix crash during cleanup from failure to allocate port commit 39de732aa728ae9b8a9414ad08b8d0ee7ed02732 origin/HEAD) Author: Laine Stump <laine> Date: Thu Aug 15 22:28:27 2019 -0400 network: replace virSaveLastError() with virErrorPreserveLast() Test on libvirt-5.6.0-2.virtcov.el8.x86_64, the result is as expected except the network connection will clear after libvirtd restart, please help to check, Thank you! 1. # virsh net-dumpxml direct-macvtap <network> <name>direct-macvtap</name> <uuid>3d3376a1-77b5-49e9-bbf1-c2c268fa8e02</uuid> <forward dev='eno27v2' mode='passthrough'> <interface dev='eno27v2'/> <interface dev='eno27v1'/> </forward> </network> # virsh attach-interface rhel network direct-macvtap --model virtio Interface attached successfully # virsh net-dumpxml direct-macvtap <network connections='1'> <name>direct-macvtap</name> <uuid>3d3376a1-77b5-49e9-bbf1-c2c268fa8e02</uuid> <forward dev='eno27v2' mode='passthrough'> <interface dev='eno27v2' connections='1'/> <interface dev='eno27v1'/> </forward> </network> 2. Restart libvirtd will clear current the connection: # systemctl restart libvirtd # virsh net-dumpxml direct-macvtap <network> <name>direct-macvtap</name> <uuid>3d3376a1-77b5-49e9-bbf1-c2c268fa8e02</uuid> <forward dev='eno27v2' mode='passthrough'> <interface dev='eno27v2'/> <interface dev='eno27v1'/> </forward> </network> # virsh attach-interface rhel network direct-macvtap --model virtio error: Failed to attach interface error: error creating macvtap interface macvtap1@eno27v2 (52:54:00:5e:ac:45): Invalid argument Loss of the connection counts during libvirtd restart is also the result of the refactoring that added the virNetworkPort APIs, but it is a separate Bug. Please file a BZ for this (also check the connection count for other types of network to see if they are affected similarly). Your testing does show that *this* BZ has been fixed though, so it can be moved to VERIFIED. Hi Laine, Thank you! File Bug 1745815 and set this one to be verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3723 |