From: Jan Kiszka <jan.kiszka@web.de>
To: Alexander Spyridakis <a.spyridakis@virtualopensystems.com>
Cc: Anup Patel <anup@brainfault.org>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
kvmarm <kvmarm@lists.cs.columbia.edu>
Subject: Re: [Qemu-devel] vexpress: Framebuffer broken with KVM enabled
Date: Mon, 16 Feb 2015 11:04:10 +0100 [thread overview]
Message-ID: <54E1C09A.7030002@web.de> (raw)
In-Reply-To: <CAJRNFKLG2k6+4v2p-A22v36TLFX=djkx9cH1wK_qAcQ0M_vCoQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
On 2015-02-16 10:34, Alexander Spyridakis wrote:
> On Mon, Feb 16, 2015 at 2:43 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> Hi,
>>
>> next issue related to KVM/QEMU on the TK1: The guest image I'm running
>> gives proper framebuffer output when in emulation mode. Once KVM is
>> enabled, the screen is - at best - only initially updated. Sometimes I
>> see the famous tux images and a bit of the console texts, but usually it
>> stays black. Explanations?
>
> Hello Jan,
>
> If you want to force rendering, you can do something similar with the
> following hack:
> https://github.com/virtualopensystems/qemu/commit/64dd1b3e3a2353433edb9c63d00271f515bd06fb
>
> Of course expect performance to not be up to par.
Yep, confirmed - both that it works and that it's slow (better not try
this with SDL, exported via X...).
Thanks,
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2015-02-16 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 9:13 [Qemu-devel] vexpress: Framebuffer broken with KVM enabled Jan Kiszka
2015-02-16 9:20 ` Anup Patel
2015-02-16 9:26 ` Jan Kiszka
2015-02-16 9:34 ` Alexander Spyridakis
2015-02-16 10:04 ` Jan Kiszka [this message]
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=54E1C09A.7030002@web.de \
--to=jan.kiszka@web.de \
--cc=a.spyridakis@virtualopensystems.com \
--cc=anup@brainfault.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=qemu-devel@nongnu.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).