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 1047242 - Live migration during Windows installation causes guest desktop to freeze
Summary: Live migration during Windows installation causes guest desktop to freeze
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Dr. David Alan Gilbert
QA Contact: Qianqian Zhu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-30 05:14 UTC by Qunfang Zhang
Modified: 2017-01-09 12:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-09 12:50:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Guest desktop when it freezes. (24.42 KB, image/png)
2013-12-30 05:15 UTC, Qunfang Zhang 		no flags Details
View All

Description Qunfang Zhang 2013-12-30 05:14:53 UTC 
Description of problem:
I just try to migrate a windows guest during installation, however the guest desktop freezes after it is migrated to the destination host.

Version-Release number of selected component (if applicable):
kernel-3.10.0-64.el7.x86_64
qemu-kvm-1.5.3-30.el7.x86_64

How reproducible:
Randomly, I hit it twice today.

Steps to Reproduce:
1. Boot a windows guest on src host and start installation. 
 /usr/libexec/qemu-kvm -M pc -cpu SandyBridge,hv_spinlocks=0x1fff,hv_relaxed,hv_vapic -enable-kvm -m 2G -smp 4,sockets=4,cores=1,threads=1 -name win8-64 -uuid 9a0e67ec-f286-d8e7-0548-0c1c9ec93009 -nodefconfig -nodefaults -monitor stdio -rtc base=utc,clock=host,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -usb -device usb-tablet,id=input1  -device usb-mouse,id=mouse -drive file=/mnt/installation.raw,if=none,id=drive-sata0-0-0,format=raw,cache=none,werror=stop,rerror=stop -device ide-drive,bus=ide.1,unit=0,drive=drive-sata0-0-0,id=sata0-0-0 -drive file=/mnt/en_windows_server_2012_r2_vl_x64_dvd_3319595.iso,if=none,media=cdrom,id=drive-sata0-0-1,readonly=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-sata0-0-1,id=sata0-0-1,bootindex=1 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:d5:51:8a,bus=pci.0,addr=0x4 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc :10 -vga std -device intel-hda,id=sound0,bus=pci.0,addr=0x5 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0,addr=0x7 -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel1,name=port1,bus=virtio-serial0.0,id=port1 -chardev socket,id=channel2,path=/tmp/helloworld2,server,nowait -device virtserialport,chardev=channel2,name=port2,bus=virtio-serial0.0,id=port2 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -qmp tcp:0:5555,server,nowait -drive if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0

2. Boot the guest on destination host with "-incoming x-rdma:0:5800"

3. Migrate the guest during installation. 


Actual results:
After migration, guest desktop freezes. The installation process will not change any more. And the mouse point could not move.

Expected results:
Guest desktop should not freeze. 

Additional info:
"top" on host:

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                    
19769 root      20   0 2945796 1.998g   7948 S   6.0 58.5   1:31.19 qemu-kvm                                                   
19926 root      20   0  123652   1572   1080 R   6.0  0.0   0:00.02 top
Comment 1 Qunfang Zhang 2013-12-30 05:15:59 UTC 
Created attachment 843270 [details]
Guest desktop when it freezes.
Comment 4 Dr. David Alan Gilbert 2014-08-13 13:32:02 UTC 
Hi Qunfang,
  You said 'Randomly, I hit it twice today.' about how many times had you migrated ? (i.e. is it it 2 in 10 or 2 in 100 ?)
Comment 5 Qunfang Zhang 2014-08-14 06:02:20 UTC 
(In reply to Dr. David Alan Gilbert from comment #4)
> Hi Qunfang,
>   You said 'Randomly, I hit it twice today.' about how many times had you
> migrated ? (i.e. is it it 2 in 10 or 2 in 100 ?)

Hi, David

I could not tell an exact number about the migration time now. But usually when I hit such issue in migration, I will try it for about 10~20 round ping-pong migration. It should not reach to 50 or 100 times because testing it manually for so many times will spend too much time and will block my further test process. 


Thanks,
Qunfang
Comment 8 HongyangDai 2016-08-03 09:16:18 UTC 
I hit the same issue with the versions:

qemu-kvm-2.6.0-16.el7.x86_64
kernel-3.10.0-481.el7.x86_64

How reproducible:
I hit it many times today.

Steps to Reproduce:
1. Boot a windows guest on src host and start installation. 
/usr/libexec/qemu-kvm  -name win -cpu Westmere,check -m 2048 -realtime mlock=off -smp 4,sockets=2,cores=2,threads=1 -uuid 7bef3814-631a-48bb-bae8-2b1de75f7a13 -nodefaults -monitor stdio -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot order=c,menu=on -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/mnt/nfs/win10x64.iso,if=none,media=cdrom,id=drive-virtio-win0,readonly=on,format=raw -device ide-drive,drive=drive-virtio-win0,id=virtio-win0 -drive file=/mnt/nfs/virtio-win.iso,if=none,media=cdrom,id=drive-virtio-win1,readonly=on,format=raw -device ide-drive,drive=drive-virtio-win1,id=virtio-win1 -drive file=/mnt/nfs/winsys.qcow2,if=none,id=drive-virtio-blk0,format=qcow2,werror=stop,rerror=stop -device virtio-scsi-pci,id=virtio-blk0,disable-legacy=true,disable-modern=false -device scsi-disk,drive=drive-virtio-blk0,scsi-id=0,lun=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on -spice port=5930,disable-ticketing -vga qxl -global qxl-vga.vram_size=33554432 -device qxl,id=video1,vram_size=67108864,bus=pci.0,addr=0x4 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=3C:D9:2B:09:AB:44,bus=pci.0,addr=0x7 -qmp tcp:0:5555,server,nowait  -boot order=d

2. Boot the guest on destination host with "-incoming x-rdma:0:5800"

3. Migrate the guest during installation.
Comment 9 Dr. David Alan Gilbert 2016-08-03 10:00:13 UTC 
(In reply to HongyangDai from comment #8)
> I hit the same issue with the versions:
> 
> qemu-kvm-2.6.0-16.el7.x86_64
> kernel-3.10.0-481.el7.x86_64
> 
> How reproducible:
> I hit it many times today.
> 
> Steps to Reproduce:
> 1. Boot a windows guest on src host and start installation. 
> /usr/libexec/qemu-kvm  -name win -cpu Westmere,check -m 2048 -realtime
> mlock=off -smp 4,sockets=2,cores=2,threads=1 -uuid
> 7bef3814-631a-48bb-bae8-2b1de75f7a13 -nodefaults -monitor stdio -rtc
> base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard
> -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot
> order=c,menu=on -device
> virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive
> file=/mnt/nfs/win10x64.iso,if=none,media=cdrom,id=drive-virtio-win0,
> readonly=on,format=raw -device
> ide-drive,drive=drive-virtio-win0,id=virtio-win0 -drive
> file=/mnt/nfs/virtio-win.iso,if=none,media=cdrom,id=drive-virtio-win1,
> readonly=on,format=raw -device
> ide-drive,drive=drive-virtio-win1,id=virtio-win1 -drive
> file=/mnt/nfs/winsys.qcow2,if=none,id=drive-virtio-blk0,format=qcow2,
> werror=stop,rerror=stop -device
> virtio-scsi-pci,id=virtio-blk0,disable-legacy=true,disable-modern=false
> -device scsi-disk,drive=drive-virtio-blk0,scsi-id=0,lun=0 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on -spice
> port=5930,disable-ticketing -vga qxl -global qxl-vga.vram_size=33554432
> -device qxl,id=video1,vram_size=67108864,bus=pci.0,addr=0x4 -netdev
> tap,id=hostnet0,vhost=on -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=3C:D9:2B:09:AB:44,bus=pci.0,
> addr=0x7 -qmp tcp:0:5555,server,nowait  -boot order=d
> 
> 2. Boot the guest on destination host with "-incoming x-rdma:0:5800"
> 
> 3. Migrate the guest during installation.


That's win10 so a lot newer than this old bug; so I suggest it might be better with a new bug for that.  It's also possibly related to 1357765.
Are you sure you were using x-rdma? I think x-rdma only works on older qemu and you say you're using newer 2.6.0 qemu.
Comment 10 Dr. David Alan Gilbert 2016-08-03 10:01:15 UTC 
oops, wrong needinfo.
Comment 11 HongyangDai 2016-08-04 02:11:54 UTC 
I am sorry for my carelessness .In fact ,I set up the VM with "-incoming tcp:0:5800". OK,I will file  new bug for this.
Comment 17 Dr. David Alan Gilbert 2017-01-09 12:50:35 UTC 
As comment 15 it seems to work now; not quite sure which fix helped; possibly the set related to bz 1357765
Note You need to log in before you can comment on or make changes to this bug.