From: Arvind R <arvino55@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] xen domU screen corruption
Date: Fri, 23 Apr 2010 14:50:45 +0530 [thread overview]
Message-ID: <u2sd799c4761004230220g4ab46646l9b9e652567ad8fa4@mail.gmail.com> (raw)
Hi,
I have a pvops-domU running on xen, using qemu-dm as the device-model.
All is fine as long as I do not switch to the qemu-console (ctrl-alt-1). After
a switch to the qemu-console, on returning to the domU console, the screen
is unreadable. This is because in hw/xenfb.c, in the function
xenfb_guest_copy(),
the case of xenfb->depth == bpp is not handled in qemu-0.12.3 release.
Reverting to the older code for handling the case solves the screen
corruption.
But now, I find that key-strokes are not echoed as they are typed.
Instead, after
the CR, the whole typed line is echoed and everything else is fine. This occurs
only after switching to the qemu-console and back. Any pointer to where to
look for the solution to the problem would be welcome.
Hope this is the right mailing-list.
Thanks.
arvind. r.
reply other threads:[~2010-04-23 9:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=u2sd799c4761004230220g4ab46646l9b9e652567ad8fa4@mail.gmail.com \
--to=arvino55@gmail.com \
--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).