From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm <kvm@vger.kernel.org>,
Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Subject: Re: Frame buffer corruptions with KVM >= 2.6.36
Date: Thu, 14 Oct 2010 14:31:08 +0200 [thread overview]
Message-ID: <4CB6F80C.8050202@redhat.com> (raw)
In-Reply-To: <4CB6F3F1.9060409@redhat.com>
On 10/14/2010 02:13 PM, Avi Kivity wrote:
>
>> and this commit just makes the
>> corruptions more likely. This may even be a QEMU issue in the cirrus/vga
>> model (both qemu-kvm and upstream show the effect).
>>
>
> What about -no-kvm?
>
Doesn't happen there.
My guess is the initial dirty log after the switch does not contain all
1s so memory isn't updated. Probably need to force a full redraw in
that case.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-10-14 12:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 7:27 Frame buffer corruptions with KVM >= 2.6.36 Jan Kiszka
2010-10-14 12:04 ` Avi Kivity
2010-10-14 12:11 ` Avi Kivity
2010-10-14 12:13 ` Jan Kiszka
2010-10-14 12:10 ` Jan Kiszka
2010-10-14 12:13 ` Avi Kivity
2010-10-14 12:31 ` Avi Kivity [this message]
2010-10-14 12:36 ` Jan Kiszka
2010-10-14 12:38 ` Avi Kivity
2010-10-15 6:41 ` Takuya Yoshikawa
2010-10-18 12:14 ` Takuya Yoshikawa
2010-10-18 12:17 ` 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=4CB6F80C.8050202@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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