kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Glauber Costa <glommer@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: kvm-userspace: VGA/VESA framebuffer broken
Date: Fri, 05 Dec 2008 19:22:48 +0100	[thread overview]
Message-ID: <49397178.4040302@web.de> (raw)
In-Reply-To: <49396D83.4050409@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 752 bytes --]

Avi Kivity wrote:
> Jan Kiszka wrote:
>> Garbage is gone, but update does not happen automatically. I have to
>> switch to the monitor or some other SDL console in back in order to see
>> the latest framebuffer updates.
>>   
> 
> That was indeed a symptom during the brokenness.  Which guest are you
> running?

Various home-brewed or openSuse kernels from 2.6.23 to 27.

>  also, please supply commit hashes you're working with so I can
> check I didn't push the wrong thing.

58e235dc112a8d0cc309af0f2e526087235ab633 (kernel) and
38fb92b29d43f8503fd78a30158f93d40cd88de2 (userspace).

Jan

PS: fc94d163d1e3424199166cf50449e03447400579 (fold vcpu_info into
CPUState) broke -kvm-no-irqchip. Currently trying to understand why.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 10:04 kvm-userspace: VGA/VESA framebuffer broken Jan Kiszka
2008-12-05 10:18 ` 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 [this message]
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=49397178.4040302@web.de \
    --to=jan.kiszka@web.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).