Bug 609741 - QEMU driver doesn't expect "qemu-kvm-devel" as version number
Summary: QEMU driver doesn't expect "qemu-kvm-devel" as version number
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt (Show other bugs)
(Show other bugs)
Version: unspecified
Hardware: All Linux
low
medium
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-01 00:27 UTC by vekmitt
Modified: 2011-03-17 14:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-03-17 14:35:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description vekmitt 2010-07-01 00:27:57 UTC
Description of problem:
Since I have some problems with qemu-kvm-0.12.4 I was told to try qemu.git. It seems that libvirt parses the version number only in the brackets, e.g. qemu-kvm-0.12.4 returns
> QEMU PC emulator version 0.12.4 (qemu-kvm-0.12.4), Copyright (c) 2003-2008 Fabrice Bellard
but qemu.git returns
> QEMU emulator version 0.12.50 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard


How reproducible:
Use qemu.git instead of an official release of QEMU.

  
Actual results:
libvirt doesn't start the virtual machine at all, it returns the following error (syslog):
> libvirtd: error : qemudParseHelpStr:1341 : internal error cannot parse /usr/bin/qemu-kvm version number in 'QEMU emulator version 0.12.50 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard'


Expected results:
libvirt should start qemu.git just like every other release of QEMU.

Comment 1 Cole Robinson 2010-07-01 14:34:27 UTC
This is fixed upstream, a release just hasn't been cut yet. It should be within a couple weeks.

Comment 2 Cole Robinson 2011-03-17 14:35:41 UTC
Don't know the exact commit, but this has been fixed for a few releases. Closing.


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