Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1314230 - libvirt fails with undefined symbol
Summary: libvirt fails with undefined symbol
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F24BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2016-03-03 09:08 UTC by Mairi Dulaney
Modified: 2016-03-10 16:00 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-10 15:11:33 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1164773 0 unspecified CLOSED libvirt-1.2.10-2.fc22 fails to connect to hypervisor; error: undefined symbol: virStorageFileCreate 2022-05-16 11:32:56 UTC

Internal Links: 1164773

Description Mairi Dulaney 2016-03-03 09:08:53 UTC 
Description of problem:
libvirt starts, but the qemu module fails to load.  systemctl status gives me:

failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so: undefined symbol: virStorageFileCreate

Version-Release number of selected component (if applicable):
1.3.2-1

How reproducible:
Always

Steps to Reproduce:
1.  Upgrade libvirt stack to this release
2.  restart libvirtd
3.  failure

Actual results:
Failure; virt no work

Expected results:
Lack of failure; virt work
Comment 1 Fedora Blocker Bugs Application 2016-03-03 09:11:18 UTC 
Proposed as a Blocker for 24-beta by Fedora user jdulaney using the blocker tracking app because:

 The release must be able host virtual guest instances of the same release. 

As the default virt stack is kvm/qemu/libvirt, and the bits between libvirt and qemu are failing due to an undefined symbol, virt doesn't work, thus hitting this criteria.
Comment 2 Ján Tomko 2016-03-03 16:19:02 UTC 
This looks like bug 1164773 which was solved by a device-mapper update.

Do you see any other errors in the log?
$ journalctl -u libvirtd --since=yesterday -p err
Comment 3 Mairi Dulaney 2016-03-03 18:21:11 UTC 
No other errors of note.

With my update this morning, qemu and libvirt were both updated.  Device mapper was not changed, and prior to this update, qemu/libvirt was working just fine.  The bug you reference points the blame at devicemapper, but I fail to see how that could be the culprit in htis case.
Comment 4 Mairi Dulaney 2016-03-04 20:14:09 UTC 
Okay, I downgraded to 1.3.1-2, and the issue went away, strongly suggesting that this is an issue with the latest release of libvirt.  I'm going to do a rebuild right quick just to see if something went weird.
Comment 5 Mairi Dulaney 2016-03-04 21:53:55 UTC 
Okay, just rebuilding seems to have corrected this issue.  Looks like something got weird in the build process.  If I reinstall the 'official' build, problem comes back.  Would it be possible to get a rebuild of libvirt?
Comment 6 Kamil Páral 2016-03-07 17:34:37 UTC 
Discussed at today's blocker review meeting [1]. Accepted as a Beta blocker -  as described this sounds like a clear violation of Beta criterion "The release must be able host virtual guest instances of the same release." (with footnote describing the supported virt stack, including libvirt)

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-03-07/
Comment 7 Cole Robinson 2016-03-09 15:21:40 UTC 
I can't reproduce this on f24 with libvirt-1.3.2-1, using fully updated f24

John, is your machine fully updated? Can you still reproduce this? What version of device-mapper-libs is installed? Mine is:

# rpm -q device-mapper-libs
device-mapper-libs-1.02.117-4.fc24.x86_64
Comment 8 Mairi Dulaney 2016-03-10 15:11:33 UTC 
Okay, since it seems that the cause of this has gone away, I'm going to go ahead and close this here ticket.
Comment 9 Kamil Páral 2016-03-10 15:24:33 UTC 
John, does it work for you now? What changed?
Comment 10 Mairi Dulaney 2016-03-10 16:00:47 UTC 
Yes, it's working for me now.  What changed is I just ran an update, pulled in the new libvirt build.
Note You need to log in before you can comment on or make changes to this bug.