All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: kvmarm <kvmarm@lists.cs.columbia.edu>, kvm <kvm@vger.kernel.org>
Subject: vexpress: Framebuffer broken with KVM enabled
Date: Mon, 16 Feb 2015 10:13:30 +0100	[thread overview]
Message-ID: <54E1B4BA.3030705@web.de> (raw)

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?

Jan

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: kvmarm <kvmarm@lists.cs.columbia.edu>, kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] vexpress: Framebuffer broken with KVM enabled
Date: Mon, 16 Feb 2015 10:13:30 +0100	[thread overview]
Message-ID: <54E1B4BA.3030705@web.de> (raw)

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?

Jan

             reply	other threads:[~2015-02-16  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16  9:13 Jan Kiszka [this message]
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:20   ` [Qemu-devel] " Anup Patel
2015-02-16  9:26   ` Jan Kiszka
2015-02-16  9:26     ` [Qemu-devel] " Jan Kiszka
2015-02-16  9:34   ` Alexander Spyridakis
2015-02-16  9:34     ` [Qemu-devel] " Alexander Spyridakis
2015-02-16 10:04     ` Jan Kiszka
2015-02-16 10:04       ` [Qemu-devel] " 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=54E1B4BA.3030705@web.de \
    --to=jan.kiszka@web.de \
    --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 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.