All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Glauber Costa <glommer@redhat.com>, Avi Kivity <avi@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: kvm-userspace: VGA/VESA framebuffer broken
Date: Fri, 05 Dec 2008 11:04:24 +0100	[thread overview]
Message-ID: <4938FCA8.3010408@siemens.com> (raw)

Hi,

latest kvm-userspace git 6892f63c18a526c7b54bbde2f59287787eabe1f8
appears to have a bug /wrt VGA/VESA modes. I just fired up one of my
Linux test kernels which runs a framebuffer console in mode 0x317, but
the display just contains garbage. Reverting to
82daa70a1d5bcad3a93150ffc5afbcb9e77361fb makes the problem disappear again.

I also tried latest qemu with -enable-kvm against the same kernel
modules, and the result is somehow better in that there is some output
on the screen -- but it is horribly slow.

Glauber, Avi, is this a problem of latest qemu upstream changes to the
vga emulation or a merge issue?

Jan

-- 
Siemens AG, Corporate Technology, CT SE 26
Corporate Competence Center Embedded Linux

             reply	other threads:[~2008-12-05 10:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 10:04 Jan Kiszka [this message]
2008-12-05 10:18 ` kvm-userspace: VGA/VESA framebuffer broken Glauber Costa
2008-12-05 10:19 ` Avi Kivity
2008-12-05 10:36   ` Jan Kiszka
2008-12-05 15:42     ` Avi Kivity
2008-12-05 18:00       ` Jan Kiszka
2008-12-05 18:05         ` Avi Kivity
2008-12-05 18:22           ` Jan Kiszka
2008-12-07 15:01             ` Avi Kivity
2008-12-07 22:20               ` Michael Tokarev
2008-12-08  8:00                 ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4938FCA8.3010408@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.