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.
Description of problem:
when the resolution of virtual console is set up to a higher value, guest will core dump
Version-Release number of selected component (if applicable):
# uname -r
2.6.32-220.el6.x86_64
# rpm -qa| grep qemu-kvm
qemu-kvm-0.12.1.2-2.213.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.boot a guest
/usr/libexec/qemu-kvm -cpu qemu64,+sse2 -smp 2 -m 2G -drive file=/mnt/rhel-server-64.raw,if=none,id=drive-virtio-disk1,media=disk,cache=none,format=raw,werror=stop -device virtio-blk-pci,bus=pci.0,addr=0x3,drive=drive-virtio-disk1,id=virtio-disk1,bootindex=1 -vnc :0 -boot menu=on -M rhel6.2.0 -balloon none -netdev tap,id=id10,script=/etc/qemu-ifup -device virtio-net-pci,netdev=id10,mac=9a:fe:9d:9b:24:10,id=ndev10,bus=pci.0,addr=0x5 -serial vc:1000x1000
2.Ctrl+Alt+3,guest works normally
3.set the resolution of vc to a higher value
/usr/libexec/qemu-kvm -serial vc:10000x10000
4 Ctrl+Alt+3,guest core dumped
(gdb) bt
#0 vnc_refresh_server_surface (vd=0x3772010) at vnc.c:2321
#1 0x00000000004de22c in vnc_refresh (opaque=0xffffffffffffffff) at vnc.c:2361
#2 0x000000000040c578 in qemu_run_timers (timeout=1000) at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:1309
#3 main_loop_wait (timeout=1000) at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:4058
#4 0x000000000042af2a in kvm_main_loop () at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:2225
#5 0x000000000040deb5 in main_loop (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>)
at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:4234
#6 main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:6470
Actual results:
guest core dump
Expected results:
when resolution of vc is set up to a higher value, guest should boot with default max value or guest can not boot.
Additional info:
(In reply to comment #2)
> FYI,
> -serial vc:xxy
>
> whether x or y larger than 2048 will cause guest core dump
>
> Mike
hi, Mike
Indeed, this issue is triggered under x or y larger than 2048.
Best Regards
Description of problem: when the resolution of virtual console is set up to a higher value, guest will core dump Version-Release number of selected component (if applicable): # uname -r 2.6.32-220.el6.x86_64 # rpm -qa| grep qemu-kvm qemu-kvm-0.12.1.2-2.213.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.boot a guest /usr/libexec/qemu-kvm -cpu qemu64,+sse2 -smp 2 -m 2G -drive file=/mnt/rhel-server-64.raw,if=none,id=drive-virtio-disk1,media=disk,cache=none,format=raw,werror=stop -device virtio-blk-pci,bus=pci.0,addr=0x3,drive=drive-virtio-disk1,id=virtio-disk1,bootindex=1 -vnc :0 -boot menu=on -M rhel6.2.0 -balloon none -netdev tap,id=id10,script=/etc/qemu-ifup -device virtio-net-pci,netdev=id10,mac=9a:fe:9d:9b:24:10,id=ndev10,bus=pci.0,addr=0x5 -serial vc:1000x1000 2.Ctrl+Alt+3,guest works normally 3.set the resolution of vc to a higher value /usr/libexec/qemu-kvm -serial vc:10000x10000 4 Ctrl+Alt+3,guest core dumped (gdb) bt #0 vnc_refresh_server_surface (vd=0x3772010) at vnc.c:2321 #1 0x00000000004de22c in vnc_refresh (opaque=0xffffffffffffffff) at vnc.c:2361 #2 0x000000000040c578 in qemu_run_timers (timeout=1000) at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:1309 #3 main_loop_wait (timeout=1000) at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:4058 #4 0x000000000042af2a in kvm_main_loop () at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:2225 #5 0x000000000040deb5 in main_loop (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:4234 #6 main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:6470 Actual results: guest core dump Expected results: when resolution of vc is set up to a higher value, guest should boot with default max value or guest can not boot. Additional info: