Hide Forgot
Description of problem: win8.1-32 guest gui freeze after migration, but network works well. Version-Release number of selected component (if applicable): Host: RHEL-7.0-20131127.1 qemu-img-1.5.3-21.el7.x86_64 qemu-kvm-common-rhev-1.5.3-21.el7.x86_64 qemu-kvm-rhev-debuginfo-1.5.3-21.el7.x86_64 qemu-kvm-rhev-1.5.3-21.el7.x86_64 kernel-3.10.0-57.el7.x86_64 virtio-win-1.6.7-2.el7.noarch Guest: win8.1-32 How reproducible: 100% Steps to Reproduce: 1.Boot vm from src host with following cli: #/usr/libexec/qemu-kvm \ -M pc \ -cpu SandyBridge \ -m 2G \ -smp 4,sockets=2,cores=2,threads=1,maxcpus=16 \ -enable-kvm \ -name win8-32 \ -uuid 990ea161-6b67-47b2-b803-19fb01d30d12 \ -smbios type=1,manufacturer='Red Hat',product='RHEV Hypervisor',version=el6,serial=koTUXQrb,uuid=feebc8fd-f8b0-4e75-abc3-e63fcdb67170 \ -k en-us \ -rtc base=localtime,clock=host,driftfix=slew \ -nodefaults \ -monitor stdio \ -qmp tcp:0:6666,server,nowait \ -boot menu=on \ -bios /usr/share/seabios/bios.bin \ -drive file=/home/win8.1-32.qcow2,if=none,id=drive-data-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop \ -device virtio-blk-pci,bus=pci.0,addr=0x7,scsi=off,drive=drive-data-disk,id=data-disk \ -drive file=/home/boot.iso,if=none,id=drive-ide0-0-1,media=cdrom,format=raw \ -device ide-drive,bus=ide.0,unit=1,drive=drive-ide0-0-1 \ -device virtio-balloon-pci,bus=pci.0,id=balloon0 \ -netdev tap,id=hostnet0,script=/etc/ovs-ifup,downscript=/etc/ovs-ifdown \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:01:01:ef \ -device piix3-usb-uhci,id=usb \ -device usb-tablet,id=input0 \ -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0 \ -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait \ -device virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port1 \ -vga cirrus \ -vnc :0 \ 2.Do ping-pong migration between two hosts. 3. Actual results: after 1~2 times migration, guest will freeze, but ping guest got answer. Expected results: Guest works well. Additional info:
*** This bug has been marked as a duplicate of bug 1036478 ***