Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The problem is in seabios/vgabios.
There was a bug fixed by commit in upstream:
commit b7b92935df0e309149c042d587e4764548f10608
Author: Kevin O'Connor <kevin>
Date: Sat Mar 9 13:04:47 2013 -0500
vgabios: Fix cirrus memory clear on mode switch.
The cirrus_clear_vram() code wasn't actually doing anything because of
a u8 overflow. Fix that.
Fill with 0xff when performing a legacy cirrus mode switch (WinXP has
been observed to incorrectly render dialog boxes if the memory is
filled to 0). This was the behavior of the original LGPL vgabios
code. To support this, add mechanism (MF_LEGACY) to allow vga drivers
to detect if the mode switch is from vesa or int10.
Signed-off-by: Kevin O'Connor <kevin>
I'm sending a back-port to corresponding repository.
Comment 7Miroslav Rezanina
2014-01-13 09:33:09 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: Boot win2k3 with -vga cirrus, the display is abnormal. Version-Release number of selected component (if applicable): * Red Hat Enterprise Linux Server release 7.0 Beta(Maipo) * kernel-3.10.0-0.rc7.64.el7.x86_64 * qemu-img-1.5.0-2.el7.x86_64 * virtio-win-prewhql-0.1-65 * spice-server-0.12.3-1.el7.x86_64 * seabios-1.7.2-2.el7.x86_64 * vgabios-0.6b-3.7.el6.noarch How reproducible: 100% Steps to Reproduce: 1.Boot guest with CLI /usr/libexec/qemu-kvm -drive file=win2k3-32.qcow2,if=none,cache=unsafe,media=disk,format=qcow2,id=drive-ide0-0-1 -device ide-drive,id=ide1,drive=drive-ide0-0-1,bus=ide.1 -device virtio-balloon-pci,id=balloon1 -monitor stdio -vnc :2 -vga cirrus -usb -device usb-tablet,id=tablet1 -boot menu=on -global kvm-pit.lost_tick_policy=discard -chardev file,path=/root/console.log,id=serial1 -device isa-serial,chardev=serial1,id=s1 -cpu SandyBridge -M pc -smp 4,cores=4 -m 2G -enable-kvm -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,mac=00:51:3c:24:31:11,id=net0 2. 3. Actual results: display abnormal Expected results: display normal Additional info: If use -vga std guest display normal.