kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Andreas Ntaflos, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 582145
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

As well, 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-rc5

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

** Attachment removed: "BootDmesg.txt"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582145/+attachment/2122976/+files/BootDmesg.txt

** Attachment removed: "ProcCpuinfo.txt"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582145/+attachment/2122978/+files/ProcCpuinfo.txt

** Attachment removed: "Lspci.txt"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582145/+attachment/2122977/+files/Lspci.txt

** Attachment removed: "ProcInterrupts.txt"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582145/+attachment/2122979/+files/ProcInterrupts.txt

** Attachment removed: "ProcModules.txt"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582145/+attachment/2122980/+files/ProcModules.txt

** Attachment removed: "UdevDb.txt"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582145/+attachment/2122981/+files/UdevDb.txt

** Attachment removed: "UdevLog.txt"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582145/+attachment/2122982/+files/UdevLog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/582145

Title:
  Virtual guests' console is unusably slow due to framebuffer usage

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  This was also discussed in https://lists.ubuntu.com/archives/ubuntu-
  server/2010-May/004172.html

  The problem is that the console of a Ubuntu 10.04 (server) virtual
  machine/guest becomes incredibly slow and really unusable as soon as
  it starts scrolling. This is apparently due to the kernel switching on
  the console framebuffer which does not play well with the VNC-based
  console viewers of virt-manager. I have created a screencast to
  demonstrate, please find it here: https://daff.pseudoterminal.org/misc
  /console-slow.ogg

  I have experienced this using KVM and virt-manager/virt-viewer on
  Ubuntu 10.04 and Ubuntu 9.10 hosts (using the server edition, FWIW).
  Apparently it also happens with VirtualBox but I have not tested this
  myself. The only solution for the time being seems to be to blacklist
  the vga16fb module as suggested by Paul Nuffer:

      $ echo "blacklist vga16fb" | sudo tee -a /etc/modprobe.d/blacklist

  Merely adding "nomodeset" to the kernel boot options is not
  sufficient.

  I don't even know exactly to which package this bug belongs let alone
  what to do about it except force the kernel not to use a console
  framebuffer. I know Plymouth needs the framebuffer to display splash
  screens and whatnot but there should be a proper way to disable it
  when running as a virtual machine. And since the splash screen is
  disabled anyway when creating a server virtual machine there is really
  no use in a framebuffer, especially if it slows everything down to a
  crawl. So what to do?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/582145/+subscriptions