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.
Bug 1168535 - The RHEL7.1 guest show dark screen after S3 when migrate guest from rhel6.6 host to rhel7.1 host
Summary: The RHEL7.1 guest show dark screen after S3 when migrate guest from rhel6.6 h...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.1
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Amit Shah
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: Virt-S3/S4-7.0
TreeView+ depends on / blocked
 
Reported: 2014-11-27 09:12 UTC by huiqingding
Modified: 2015-09-19 06:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-19 06:37:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description huiqingding 2014-11-27 09:12:13 UTC 
Description of problem:
The RHEL7.1 guest show dark screen after S3 when migrate guest from rhel6.5 host to rhel7 host

Version-Release number of selected component (if applicable):
RHEL6.6 src host:
kernel-2.6.32-515.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64

RHEL7.1 dst host:
kernel-3.10.0-210.el7.x86_64
qemu-kvm-rhev-2.1.2-13.el7.x86_64

RHEL7.1 guest:
kernel-3.10.0-210.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. boot a RHEL7.1 guest on the src host:
# /usr/libexec/qemu-kvm -cpu Opteron_G1,enforce \
-enable-kvm  -m 4096  -smp 2,sockets=2,cores=1,threads=1,maxcpus=160 \
-monitor stdio \
-M rhel6.5.0 \
-numa node -numa node \
-global PIIX4_PM.disable_s3=0 \
-global PIIX4_PM.disable_s4=0 \
-drive file=/mnt/rhel_7_1_rhel6.qcow2,if=none,id=drive-scsi-disk,format=qcow2,cache=none,werror=stop,rerror=stop \
-device virtio-scsi-pci,id=scsi0,addr=0x13  \
-device scsi-hd,drive=drive-scsi-disk,bus=scsi0.0,id=data-disk2,bootindex=1 \
-netdev tap,id=hostnet0,vhost=on,id=hostnet0,script=/etc/qemu-ifup \
-device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=c2:9a:2f:9c:de:10,bus=pci.0,addr=0x5 \
-qmp tcp:0:4445,server,nowait \
-serial unix:/tmp/tty0,server,nowait \
-spice port=5901,password=redhat-vga,disable-ticketing -vga qxl \

2. boot the guest on the dst host:
# /usr/libexec/qemu-kvm -cpu Opteron_G1,enforce \
-enable-kvm  -m 4096  -smp 2,sockets=2,cores=1,threads=1,maxcpus=160 \
-monitor stdio \
-M rhel6.5.0 \
-numa node -numa node \
-global PIIX4_PM.disable_s3=0 \
-global PIIX4_PM.disable_s4=0 \
-drive file=/mnt/rhel_7_1_rhel6.qcow2,if=none,id=drive-scsi-disk,format=qcow2,cache=none,werror=stop,rerror=stop \
-device virtio-scsi-pci,id=scsi0,addr=0x13  \
-device scsi-hd,drive=drive-scsi-disk,bus=scsi0.0,id=data-disk2,bootindex=1 \
-netdev tap,id=hostnet0,vhost=on,id=hostnet0,script=/etc/qemu-ifup \
-device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=c2:9a:2f:9c:de:10,bus=pci.0,addr=0x5 \
-qmp tcp:0:4445,server,nowait \
-serial unix:/tmp/tty0,server,nowait \
-spice port=5901,password=redhat-vga,disable-ticketing -vga qxl \
-incoming tcp:0:5800

3. do migration
(qemu) migrate -d tcp:10.66.106.11:5800

4. after migration, do S3 inside the guest
# pm-suspend

Actual results:
after step4, the guest cannot resume with dark screen and the serial console outputs:
[drm:qxl_process_single_command] *ERROR* got unwritten 183
[    0.149004] Failed to access perfctr msr (MSR c0010001 is ffffffffffffffff)
[   69.752945] i8042: No controller found
[   69.756420] mce: Unable to init device /dev/mcelog (rc: -5)


Expected results:

The guest can be resumed after S3.

Additional info:
Comment 2 Dr. David Alan Gilbert 2014-12-01 10:17:24 UTC 
Hi
   Some questions:
     1) If you resume the guest, does the guest ping or is it completely dead?
     2) Does this test work for 6.6->7.0 host migration?
     3) Does this test for for 7.0 guest?
Comment 3 Amit Shah 2014-12-10 05:48:39 UTC 
Looks like a guest bug:

> [drm:qxl_process_single_command] *ERROR* got unwritten 183

If the guest continues to respond to ping or ssh, it'll confirm this.
Comment 4 huiqingding 2014-12-10 09:19:37 UTC 
Hi, Amit and David,

>      1) If you resume the guest, does the guest ping or is it completely
> dead?

when resume the guest, cannot ping and ssh the guest.

>      2) Does this test work for 6.6->7.0 host migration?

Hit the same problem, when migration RHEL7.1 guest from 6.6->7.0 host

RHEL6.6 src host:
kernel-2.6.32-515.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64
RHEL7.0 dst host:
kernel-3.10.0-123.9.3.el7.x86_64
qemu-kvm-rhev-1.5.3-60.el7_0.10.x86_64
RHEL7.1 guest:
kernel-3.10.0-210.el7.x86_64

>      3) Does this test for for 7.0 guest?

Use 7.0 guest, also hit this problem, the guest kernel is kernel-3.10.0-123.el7.x86_64

Best regards
Huiqing
Note You need to log in before you can comment on or make changes to this bug.