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.

Description of problem:

When using the qemu-kvm command on RHEL6 directly it starts a VNC screen to view the virtual guest console. For me the vnc connection randomly crashes with a message on the client:

Rect too big: 2048x18448 at 18192,42768 exceeds 720x400


Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.104.el6.x86_64
tigervnc-server-1.0.90-0.10.20100115svn3945.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Prepare 2 guests.
2. Start them with commands like
qemu-kvm -hda
/var/lib/libvirt/images/primary.img -m
1000 -net nic,macaddr=DE:AD:BE:EF:25:2A -net
tap,ifname=tap1,script=no,downscript=no -boot c -vnc :2

see bug 610219 for more detailed description on virtual guests setup. I'm trying to test this bug.

  
Actual results:
I've connected to the first guest from a RHEL5.5 client and it works ok.
Connecting to the second guest form the same client gives me Rect too big error and the vncclient program crashes. This happens randomly at short intervals.

Expected results:


Additional info:

Can you run vncviewer with "-log *:stderr:100" parameter and attach vncviewer's output, please?

Alex, ping... in needinfo for more than 3 months...

Closing insufficient_data, feel free to reopen once you provide output from comment #1 (if you still experience the issue).