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.

Created attachment 1101714 [details]
display abnormal after reboot

Description of problem:
Reboot guest after ping-pong migration with dd operation inside guest, remote-viewer display abnormal.

Version-Release number of selected component (if applicable):
kernel: kernel-2.6.32-584.el6.x86_64
qemu-kvm: qemu-kvm-0.12.1.2-2.481.el6.x86_64

How reproducible:
1/3, hit once, can't be reproduced so far.

Steps to Reproduce:
1.Launch guest with -vnc:10 --device cirrus-vga,id=video0,bus=pci.0,addr=0x4
2.Do 100 rounds ping-pong migration when do dd operation inside guest
3.After migration finished, remote-view vnc://xxx:5910
4.Reboot inside guest.

Actual results:
Display abnormal as attached picture shows, keyboard and mouse doesn't work; but it could ssh remotely and do other operations successfully, and no errors in dmesg.

Expected results:
Guest reboot correctly

Additional info:

Since this is a corner case and we can't reproduce it, I'm closing it due to low priority. Please reopen if it ever happens again.