From: Andriy Gapon <avg@FreeBSD.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] broken screendump for text mode?
Date: Wed, 07 Sep 2011 22:49:52 +0300 [thread overview]
Message-ID: <4E67CAE0.3000907@FreeBSD.org> (raw)
In-Reply-To: <4E5D14D6.9000405@FreeBSD.org>
on 30/08/2011 19:50 Andriy Gapon said the following:
>
> I use Qemu 0.15.0 (via a FreeBSD qemu-devel-0.15.0 port) and observe the following
> problem with the screendump command.
>
> Environment:
> - qemu started with a standard vga adapter emulation (not sure if this important)
> - SDL interface is used (not sure if this important)
> - guest operating system uses the text mode
> - monitor console is activated with Ctrl+Alt+2
> - screendump command is executed in the monitor console
>
> I observe the following effects in this case:
> - contents of the guest screen is "dumped" over the monitoring console
> - produced ppm file has only a single top-most line (of characters) from the guest
> screen
>
> It seems that the problem is caused in the vga_draw_text function in hw/vga.c.
> The problem is that the dpy_update function is called for each line of text and
> only the first of such calls produces the ppm output.
>
> Perhaps in the case when full_update is true there should only be a single
> dpy_update call for the whole screen. I think that this should produce a complete
> screen dump. Not sure if that would help with the guest screen contents being
> draw over the monitor console.
I have to guess that this issue is not of interest to the active qemu developers?
I will try to look into it some time myself, because I find the feature to be
useful from time to time (if it worked).
--
Andriy Gapon
prev parent reply other threads:[~2011-09-07 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 16:50 [Qemu-devel] broken screendump for text mode? Andriy Gapon
2011-09-07 19:49 ` Andriy Gapon [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=4E67CAE0.3000907@FreeBSD.org \
--to=avg@freebsd.org \
--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).