Bug 971379 - [REGRESSION] qemu-kvm : after upgrading from F17 to F18, RHEL5 guest starts looping (cpu 100%) immediately after loading the initramdisk
Summary: [REGRESSION] qemu-kvm : after upgrading from F17 to F18, RHEL5 guest starts l...
Status: CLOSED DUPLICATE of bug 967652
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu (Show other bugs)
(Show other bugs)
Version: 18
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
Keywords: Regression
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-06 11:40 UTC by Jaromír Cápík
Modified: 2016-02-01 01:58 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-11 21:11:25 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jaromír Cápík 2013-06-06 11:40:32 UTC
Description of problem:

I just upgraded my workstation from F17 to F18 and can't start my RHEL5 guest anymore. The issue is present with qemu-kvm only. When I start the guest with qemu-system-x86_64, it seems to run without problems (just terribly sloooow).
There seems to be some kind of loop, because the qemu-kvm process eats the whole CPU and nothing happens.

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

How reproducible:

Comment 1 Jaromír Cápík 2013-06-06 11:44:32 UTC
Note : RHEL6 guest and Fedora Rawhide seems to run correctly.

Comment 2 Paolo Bonzini 2013-06-20 12:05:55 UTC
What kernel version?  Might be a dup of bug 967652.

Comment 3 Jaromír Cápík 2013-06-20 13:51:49 UTC
uname -a says it's 3.9.2-200.fc18.x86_64

Comment 4 Jaromír Cápík 2013-06-20 13:54:47 UTC
tested guest kernels ... 2.6.18-8.el5 and 2.6.18-348.el5

Comment 5 Cole Robinson 2013-07-11 21:11:25 UTC
I think this is a dup, please reopen if I'm wrong.

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

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