Bug 507899

Forgot to add:
qemu-0.10.5-3.fc11.x86_64
vgabios-0.6-0.5.b.fc11.noarch

Thanks for the report

Could you include the qemu-kvm command line you used?

Created attachment 349279 [details]
CentOS 5.3 startup script

I'm still getting nailed by the bug even after the latest round of qemu updates. (0.10.6-9.fc11 from updates-testing)

- Gilboa

I experience the same bug on Fedora-11.

qemu command line:
/usr/bin/qemu-kvm -vga std -S -M pc -m 1024 -smp 1 -name HAL-XP64 -uuid e9f68cdb-0dcc-13ff-3449-8435373e631a -monitor pty -pidfile /var/run/libvirt/qemu//HAL-XP64.pid -localtime -boot c -drive file=/var/lib/libvirt/images/HAL-XP64.img,if=ide,index=0,boot=on -drive file=,if=ide,media=cdrom,index=2 -net nic,macaddr=54:52:00:54:21:7c,vlan=0 -net tap,fd=16,vlan=0 -net nic,macaddr=54:52:00:0b:69:e3,vlan=1 -net tap,fd=17,vlan=1 -serial pty -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:0 -soundhw es1370

TigerVNC command line: vncviewer 127.0.0.1

Thanks guys

Note, AFAIK if you use libvirt to start the guest and virt-viewer to connect to the console, you won't see this issue. See:

   http://wiki.libvirt.org/page/QEMUSwitchToLibvirt

Not denying this is a qemu bug, just that we mostly focus our efforts on getting the qemu+libvirt combination to work well

Well, I haven't tried virt-viewer from the command line, 
but the viewer that runs in virt-manager (isn't it same thing as virt-viewer?) 
is even worse than TigerVNC -- it randomly stops saying "disconnected". 
In fact this is the main reason I'm using TigerVNC vncviewer -- 
it's easier to restart it.

P.S. The guest OS is Windows.

Here is the error message from virt-manager viewer:

TCP/IP error: VNC connection to hypervisor host got refused or disconnected!

I cannot be sure but I *think* this might be caused by the same problem as "rect too long" -- because the pattern is very similar -- it happens when for example scrolling windows in the guest OS.

BTW I tried 2 other VNC clients as well -- krdc and vinagre.
Same thing -- they randomly stop working, typically when scrolling windows.

As I said, most likely this is caused by the same problem with qemu.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Would you mind testing with qemu 0.12.3 in updates-testing for F-12 right now to see if this reproduces for you?

incompatibility between qemu and vnc protocol.

solution here (from 2006)
http://www.linux-kvm.org/page/FAQ#.22rect_too_big.22_Message_when_using_VNC_Display

fixed it for me. btw fc12 is also bit by this.

Latest F12 package (qemu*-0.12.3-2.fc12.x86_64) seems to be working just fine.
Not only I managed to do a full $ find / on the guest without crash the VNC client on the host (vinagre), I no longer see garbage in text displays (as I used to in previous releases).

Kudos!

- Gilboa

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Seems to be OK in F12. Please close.

Thanks,
Gilboa

where the heck do you get this 0.12.3-2.fc12.x86_64, yum update still only shows 0.11

It's in updates-testing.

- Gilboa

qemu-kvm-0.12.3-4.fc12.x86_64
qemu-common-0.12.3-4.fc12.x86_64
qemu-img-0.12.3-4.fc12.x86_64
qemu-kvm-tools-0.12.3-4.fc12.x86_64
qemu-system-x86-0.12.3-4.fc12.x86_64

i still get the bug with 0.12.3-4.x86_64. please keep this bug open.

Rect too big: 4294x4167 at 4293,4166 exceeds 720x400

behavior is even worse in some ways now, as there is now cases where screen updates get hung totally.

Are you seeing it in text consoles or X11?

- Gilboa

text consoles. all my VMs are text only.

I've upgrade qemu to the latest packages from updates-testing.
I did a find / on the VM (which usually blows the VNC client) and it work just fine.

Which VGA card are you using in your VM's?

- Gilboa

Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

qemu-system-x86-0.12.5-1.fc13.x86_64
tigervnc-1.0.90-0.15.20100420svn4030.fc13.x86_64

 CConn:       connected to host localhost port 5911
 CConnection: Server supports RFB protocol version 3.8
 CConnection: Using RFB protocol version 3.8
 TXImage:     Using default colormap and visual, TrueColor, depth 24.
 CConn:       Using pixel format depth 24 (32bpp) little-endian rgb888
 CConn:       Using Tight encoding
Rect too big: 640x480 at 0,0 exceeds 720x400
 main:        Rect too big

It is easily reproducible by connecting very early during qemu-kvm startup.
But it occasionally happens also when VNC decides to switch encoding later during ongoing connection but that depends on network bandwidth etc.

Created attachment 470789 [details]
tcpflow stream produced by qemu-kvm.

nc -l 5911 <127.000.000.001.05910-127.000.000.001.45056 >/dev/null
vncviewer localhost:11

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Can't seem to reproduce it under F14/F15.
Jan?

At least with:
qemu-system-x86-0.14.0-7.fc15.x86_64
tigervnc-1.0.90-4.fc15.x86_64

I am no longer able to reproduce it.
Beware, on F14 running F15 qemu-kvm in chroot locks up X.