Bug 1842330 - libvirtd crash on libxl driver
Summary: libvirtd crash on libxl driver
Keywords:
Status: CLOSED DUPLICATE of bug 1842318
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 32
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-31 23:38 UTC by Brandon
Modified: 2020-06-01 20:41 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-01 20:10:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brandon 2020-05-31 23:38:25 UTC
Description of problem:
Libvirt will crash with a segfault when trying to load the libxl driver.  Crash details can be found at:
https://retrace.fedoraproject.org/faf/reports/2934472/

I believe this is related to missing the following commit:
https://github.com/libvirt/libvirt/commit/88011ed280c4f946a7b8e7ffcea2335eb075de60

Version-Release number of selected component (if applicable):
6.1.0-3 still exhibits this behavior.

How reproducible:
I'm not an expert, but I believe this is always reproducible when libvirtd is started if is libvirt-daemon-driver-libxl.x86_64 installed.

Steps to Reproduce:
1. install libvirt, libvirt-daemon-driver-libxl.x86_64
2. start libvirtd

Actual results:
Segfault in libvirtd.

Expected results:
Service starts successfully.

Additional info:

Backtrace not submitted through abrt because of 1762719.  Manual backtrace through GDB shows failure in libxlGetAutoballoonConf, where cfg->verInfo is NULL.

This behavior started with F32 upgrade of F31 following official release.

Comment 1 Brandon 2020-06-01 20:10:00 UTC

*** This bug has been marked as a duplicate of bug 1842318 ***


Note You need to log in before you can comment on or make changes to this bug.