Red Hat Bugzilla – Bug 1018744
windows 2003 32-bit guest not display properly with '-vga cirrus' or '-vga stdio'
Last modified: 2014-01-16 21:46:22 EST
Description of problem:
windows 2003 32-bit guest not display properly with '-vga cirrus' or '-vga stdio', but with '-vga qxl' guest can display properly.
windows 2003 64-bit guest not hit this issue.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot win2003 32-bit guest with '-vga cirrus'
# /usr/libexec/qemu-kvm -net none -M pc -m 2G -cpu SandyBridge -smp 4,cores=2,threads=2,sockets=1 -monitor stdio -vnc :1 \
-drive file=/home/win2003-32.qcow2,if=none,id=guest-img \
-device ide-hd,drive=guest-img,id=os-disk \
2. use remote-viewer or vncviewer connect to guest
# remote-viewer vnc://$HOST_IP:5901
guest not display properly.
guest display properly
not install any display driver in guest.
Created attachment 811947 [details]
What's the status with upstream?
What is the RHEL-6 status (i.e. is it a regression)?
Which driver is used by windows (check device manager)? cirrus or generic?
Did you test qxl with or without guest drivers?
Created attachment 814388 [details]
1. RHEL6 has no such issue. (test on RHEL7 with qemu-kvm-1.4.0-3.el7.x86_64 hit this issue as well, so it is not a regression.)
2. Guest use cirrus driver. (has a screenshot in attachment)
3. Guest GUI work properly both with and without qxl driver.
Turned out to be a vgabios issue. With latest seavgabios everything works fine.
So we have to backport some cirrus fixes to seabios ...
please retest with seabios-22.214.171.124-8.el7
[ likely a dup of bug 979898 ]
Created attachment 851379 [details]
Tested this issue with seabios-126.96.36.199-8.el7, failed to reproduce.
# /usr/libexec/qemu-kvm -net none -M pc -m 2G -cpu SandyBridge -smp 4,cores=2,threads=2,sockets=1 -monitor stdio -vnc :1 -drive file=/home/win2003-32-virtio.qcow2,if=none,id=guest-img -device ide-hd,drive=guest-img,id=os-disk -vga cirrus
Guest display normally(see attachment in this comment).
As the result above, I'd close this as dup of bug 979898.
*** This bug has been marked as a duplicate of bug 979898 ***