Bug 243548 - new kvm release = version 27
Summary: new kvm release = version 27
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kvm
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-09 16:49 UTC by ericm24x7
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-06-09 19:04:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description ericm24x7 2007-06-09 16:49:38 UTC
Description of problem:

There is a new kvm release (version 27) from upstream dated 6/3/07. I thought
the existing kvm sources from fedora (version 26-1) could benefit from the
update. I compiled and tested the sources under x86_64: No problem so far.

http://sourceforge.net/project/showfiles.php?group_id=180599

Just a note: I'm not sure if it's necessary to have a separate kvm package since
it is already build into the latest kernel (build > 2.6.20). Maybe it's
appropriate to automatically install its user based commands (modified qemu
needed by kvm) when virtualized aware cpu is detected.

Comment 1 Jeremy Katz 2007-06-09 19:04:45 UTC
Building kvm-27 now.  And the separate package is still needed -- it's what
provides the userspace commands.  The kernel side is all integrated into the
kernel package.

Comment 2 Avi Kivity 2007-06-10 08:23:17 UTC
kvm-27 has a nasty oops.  it would be better to revert to kvm-26 (kernel side 
only; userspace may remain kvm-27).

Comment 3 Jeremy Katz 2007-06-10 12:20:02 UTC
(In reply to comment #2)
> kvm-27 has a nasty oops.  it would be better to revert to kvm-26 (kernel side 
> only; userspace may remain kvm-27).

Haven't actually done an update of the kernel piece yet; on my list for this
week, so good to know.  Will probably also pull in the suspend fixes at the same
time.


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