Hide Forgot
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): qemu-kvm-rhev-1.5.3-9.el7.x86_64 How reproducible: 100% 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 \ -vga cirrus 2. use remote-viewer or vncviewer connect to guest # remote-viewer vnc://$HOST_IP:5901 3. Actual results: guest not display properly. Expected results: guest display properly Additional info: not install any display driver in guest.
Created attachment 811947 [details] screen shot
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] device-driver-screenshot 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-1.7.2.2-8.el7 [ likely a dup of bug 979898 ]
Created attachment 851379 [details] screen shot(seabios-1.7.2.2-8) Tested this issue with seabios-1.7.2.2-8.el7, failed to reproduce. Command line: # /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 Result: 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 ***