Bug 1100929 - qemu package incompatible with older version of gluster package
Summary: qemu package incompatible with older version of gluster package
Keywords:
Status: CLOSED DUPLICATE of bug 1096654
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 20
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-24 00:24 UTC by Chris Derichs
Modified: 2014-05-24 06:43 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-24 06:43:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Chris Derichs 2014-05-24 00:24:11 UTC
Description of problem:
After updating kernel*, libvirt* and qemu* and rebooting virtualization no longer works.
I see the symptoms from https://bugzilla.redhat.com/show_bug.cgi?id=1066630#c4
Most notably, /usr/bin/qemu-system-x86_64 -help returns undefined symbol: glfs_discard_async

I had 3.4.3 of gluster installed at the time this happened.
Updating to 3.5.0 fixed it. It seems like qemu should be set to depend on gluster >= 3.5


The bug showed up when I tried to use virt-manager to connect to the updated host and all (one) of my VM's were gone and I couldn't add any. Then I ssh over to the host and libvirtd is running 

some internal errors were listed in the log along with unknown OS type hvm
The internal errors pointed to qemu programs unexpectedly exiting and and the undefined symbol entry.



Version-Release number of selected component (if applicable):
the various qemu packagers are at version 1.6.2


How reproducible:



Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Richard W.M. Jones 2014-05-24 06:43:05 UTC
gluster needs to use versioned symbols.
https://www.redhat.com/archives/virt-tools-list/2014-May/msg00033.html

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


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