This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 453981 - KVM: pvmmu breakage with gcc 4.3.0
KVM: pvmmu breakage with gcc 4.3.0
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mark McLoughlin
Fedora Extras Quality Assurance
:
: 449786 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-03 12:36 EDT by Mark McLoughlin
Modified: 2008-07-08 05:30 EDT (History)
4 users (show)

See Also:
Fixed In Version: kernel-2.6.26-0.115.rc9.git2.fc10
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-08 05:30:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Mark McLoughlin 2008-07-03 12:36:27 EDT
Rawhide (2.6.26-rc) guests running on a rawhide host is broken at the moment,
because of this:

  http://www.mail-archive.com/kvm@vger.kernel.org/msg01023.html

If you set earlyprintk=serial, you just see the guest hang at e.g.:

     0MB HIGHMEM available.
     511MB LOWMEM available.

To fix rawhide, we can either:

  1) Wait for Avi to send a fix to Linus and have the fix pulled in naturally

  2) Take whatever fix Avi accepts into git and backporting 

  3) Just disabling CONFIG_KVM_GUEST for now

Since it's been broken for quite a while, I'm just assuming we'll do (1), but
that doesn't happen soon we should probably just do (3)
Comment 1 Mark McLoughlin 2008-07-07 05:35:06 EDT
Fix went into Linus's tree just after -rc9:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ca3739327b89bb
Comment 2 Mark McLoughlin 2008-07-07 18:20:54 EDT
*** Bug 449786 has been marked as a duplicate of this bug. ***
Comment 3 Mark McLoughlin 2008-07-08 05:30:04 EDT
Should be fixed now by kernel-2.6.26-0.115.rc9.git2.fc10

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