Ubuntu

unfortunate configuration makes virtualbox perform poorly

Reported by Nicholas on 2009-11-09
86
This bug affects 18 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

Hi,
I've noticed major performance regression working with virtualbox over ubuntu 9.10.
I've tested mainline kernel builds as well as proposed (even 2.6.31-15), but the regression was still here.
After some debug, I've found the problem in some changes made to the kernel configuration between jaunty and karmic.
In particular, recompiling the kernel with PREEMPT=Y (preemptible kernel) and CONFIG_HZ_250=y solves the problem.

I hope it helps,
--
Nicholas

Nicholas (roundtrip) wrote :
Nicholas (roundtrip) on 2009-11-16
Changed in linux (Ubuntu):
assignee: nobody → Ubuntu Kernel Team (ubuntu-kernel-team)
Peter P. (peter-p-launchpad) wrote :

might be related to this discussion:
http://www.virtualbox.org/ticket/5501

Marc G. (marc-gu) wrote :

I'm also affected by this bug. I'm running kernel 2.6.31-17-generic.

Changed in linux (Ubuntu):
status: New → Confirmed

VMWare might be affected as well. See the following discussion:
http://communities.vmware.com/thread/239982?start=0&tstart=0

Andy Whitcroft (apw) wrote :

Although the HZ did drop from 250 to 100 in karmic to lucid update PREEMPT has always been off in both cases, so if CONFIG_HZ=250 is not sufficient there are other issues.

tags: added: lucid regression-potential
Nicholas (roundtrip) wrote :

I've tested 2.6.32 with CONFIG_HZ=250 and without PREEMPT, and it works just fine.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
tags: added: regression-release
removed: regression-potential

Nicolas, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
assignee: Ubuntu Kernel Team (ubuntu-kernel-team) → nobody
status: Triaged → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.