Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 723970 - app-emulation/libvirt-6.2.0-r2 with xen support is segfaulting on start
Summary: app-emulation/libvirt-6.2.0-r2 with xen support is segfaulting on start
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal major (vote)
Assignee: Matthias Maier
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-19 13:07 UTC by Karl Hakimian
Modified: 2020-10-07 15:47 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (einfo,6.43 KB, text/plain)
2020-05-19 13:08 UTC, Karl Hakimian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Hakimian 2020-05-19 13:07:19 UTC
When libvirtd starts, it segfaults. I'm not finding any useful log messages. Downgradeing to 6.0.0 allows libvirtd to start again.

Reproducible: Always

Steps to Reproduce:
1. /etc/init.d/libvirtd start
Actual Results:  
Does not start. 

Expected Results:  
Should start and allow connections.

I've only seen the issue on my xen servers. On my machines without xen libvirtd seems to start fine.
Comment 1 Karl Hakimian 2020-05-19 13:08:03 UTC
Created attachment 640348 [details]
emerge --info
Comment 2 Cheyenne Wills 2020-06-12 20:10:56 UTC
I ran into the same problem.

In my debugging, the problem is somehow associated with processing /etc/libvirt/libxl.conf.  If autoballoon is uncommented libvirtd starts.  I was able to debug down to the point were it has something to do with parsing the commandline in the function libxlGetAutoballoonConf, but at the moment I wasn't able to do further debugging.  I think it's something in the g_regex_match call.

But for now my work around was to uncomment the autoballoon statement in the libxl.conf and set it to what DOM0 is.
Comment 3 Karl Hakimian 2020-06-17 13:13:29 UTC
Your workaround works for me as well. Thanks.

Hopefully someone will be able to get to the bottom of the issue, but at least I'm no longer having to run the insecure version.
Comment 4 Thomas Bettler 2020-07-06 11:32:23 UTC
reproducible here
#721620 solves the issue