Bug 915672

Summary: Win2008R2 - do S3 while migrating a guest but then fail to resume it in destination
Product: Red Hat Enterprise Linux 7 Reporter: langfang <flang>
Component: qemu-kvmAssignee: Amit Shah <amit.shah>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: amit.shah, chayang, flang, hhuang, juzhang, knoel, michen, qzhang, rbalakri, sluo, virt-maint, vrozenfe, xfu, xigao
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-04 05:22:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 923626    

Description langfang 2013-02-26 10:08:27 UTC
Description of problem:

do S3 while migrating a guest but then fail to resume it in destination

Version-Release number of selected component (if applicable):

HOst:
# uname -r
3.7.0-0.36.el7.x86_64
# rpm -q qemu-kvm
qemu-kvm-1.3.0-6.el7.x86_64

Guest:win2008R2

drivers:
virtio-win-1.6.3-3.el6 

How reproducible:

100%

Steps to Reproduce:
1.After guest boot up,do S3--->Choose "Sleep"
2.While S3 state ,do migration from src to dst.
3.After migrate finished,resume guest by clicking ps/2 mouse/keyboards, or send "system_wakeup" qemu command.


Actual results:

Fail to resume the guest.


Expected results:

Resume the geust successfully.

Additional info:

1.Same steps use rhel7 guest ,after step3,guest will resume automatically,there have a bug for the problem (bug 915139)
2.My CLI:
 /usr/libexec/qemu-kvm  -M pc-1.3 -enable-kvm -m 4G -smp 4,sockets=2,cores=2,threads=1 -uuid 03272402-4538-4a7f-aa3e-3df4da3d5f48  -no-user-config -nodefaults -rtc base=utc  -drive file=/home/win2008r2-64-virtio.qcow2,format=qcow2,if=none,id=drive-ide0-0-0-0,werror=stop,rerror=stop,cache=none -device virtio-blk-pci,drive=drive-ide0-0-0-0,id=ide0-0-0,addr=0x3 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:60:3f:29,bus=pci.0,addr=0x4  -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x6 -chardev socket,id=channel0,path=/tmp/tty0,server,nowait -device virtserialport,chardev=channel0,name=org.linux-kvm.port.1,bus=virtio-serial0.0,id=port1 -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device  virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -monitor stdio  -boot menu=on,order=c -spice port=5800,disable-ticketing -vga qxl  -drive file=/usr/share/virtio-win/virtio-win.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0  -usb -device usb-tablet,id=input0

Comment 2 Qunfang Zhang 2013-02-26 10:34:52 UTC
Hi, Amit and Vadim
Is this a dup of bug 915631?

Comment 3 langfang 2013-03-01 11:16:19 UTC
Test this bug not with any virtio device hit the same problem

 /usr/libexec/qemu-kvm  -M pc-1.3 -enable-kvm -m 4G -smp 4,sockets=2,cores=2,threads=1 -uuid a779cceb-9d82-41bb-8110-c5b61cd0f4c8  -no-user-config -nodefaults -rtc base=utc  -drive file=/home/win2008r2-64-virtio.qcow2,format=qcow2,if=none,id=drive-ide0-0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0-0,id=ide0-0-0 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:60:3f:29,bus=pci.0,addr=0x4  -monitor stdio  -boot menu=on,order=c -spice port=5800,disable-ticketing -vga qxl  -usb -device usb-tablet,id=input0