Description of problem:
When using the console in text mode the background is garbled which
makes the text hard to read.
Steps to Reproduce:
1. start a virtual console from virt-manager
2. look at OS in text console mode
consistent black background
Works ok in qemu console for instance.
Created attachment 154011 [details]
This is a bug in the QEMU VNC server I believe. I see the same kind of
corruption when using a regular 'vncviewer' client. It seems to particularly
occur when changing resolutions.
So it is a qemu bug?
This bug is trivially reproducable with current QEMU cvs HEAD, simply by booting
the Fedora Core 6 boot.iso on i386
dd if=/dev/zero of=foo.img bs=1M count=0 seek=1024
qemu -hda foo.img -cdrom boot.iso -boot d -vnc :1 &
On the very first text mode switch - from syslinux to booting the kernel, the
pattern shown in #1 will be seen.
I did a quick hack forward porting Xen's tools/iommu/patches/vnc-fixes patch
file to work with QEMU & this solved the problem. I'll do a real forward port &
send it to upstream QEMU for comment & attach a version suitable for QEMU 0.9.0
*** Bug 239990 has been marked as a duplicate of this bug. ***
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.
If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Thanks, closing - I think this has been fixed for a while. :)