Description of problem: I have Fedora 12 installed as a virtual guest in VirtualBox 3.1.4 on a Windows XP SP3 32-bit host. Guest additions are installed. After a fresh install, and logging into the system, the system load is will past 5. With only one CPU installed on the system, this puts a great deal of stress on the guest.
The load also picks up substantially when doing updates, installing packages, using sound or video applications, or doing anything lightly intensive on the system.
Version-Release number of selected component (if applicable): This doesn't seem to be applied to any specific component outside of the system itself. I've turned off a number of services that I don't need, and still find the load excruciatingly high. However, due to the requirements of filing a new bug, I've labeled the component as Upstart, although this might not be accurate.
How reproducible: Upon every login, install of an RPM package or running updates from PackageKit.
Steps to Reproduce:
1. Install Virtualbox 3.1.4 on Windows XP.
2. Install Fedora 12 as a guest in Virtualbox.
3. Login to Fedora, and notice the system load.
Actual results: Load is around 5-6 when logging in. Similar results when using PackageKit.
Expected results: I would expect the load to be less than .5 when doing day-to-day tasks.
Additional info: Installing guest additions from Virtualbox into the Fedora guest does not change the results.
I've also submitted a bug to VirtualBox directly: please follow any progress there as appropriate.
Upstart was an... interesting guess...
If it shows up in all sorts of apps its probably either the kernel or some widely-linked library like glibc. Kernel's smart money.
It appears the kernel is a better guess. Booting into kernel 18.104.22.168-174.2.22.fc12.i686 allows for a successful login to GDM, while booting into 22.214.171.124-67.fc12.i686 does not. It just hangs after providing my password to GDM.
If you need any log files, let me know.
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.