Red Hat Bugzilla – Bug 981235
RFE: Request detail migration statistics output for live migration on RHEL6.5
Last modified: 2014-03-03 19:24:44 EST
Description of problem: In rhel7, we have wonderful migration statistics output for migration[1], And for RHEL6, the information is not detail. And after migration finish, we could only get the Migration Status (refer to step 3). It's better to the detail information to RHEL6, and it's useful for QE to check the migration status especially the downtime. [1] (qemu) info migrate capabilities: xbzrle: off Migration status: completed total time: 129769 milliseconds downtime: 239 milliseconds transferred ram: 3932719 kbytes remaining ram: 0 kbytes total ram: 4202880 kbytes duplicate: 73614 pages normal: 983162 pages normal bytes: 3932648 kbytes Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Migrate a guest 2. Before migration finish: (qemu) info migrate Migration status: active transferred ram: 42020 kbytes remaining ram: 1660192 kbytes total ram: 2228616 kbytes 3. After migration finished: (qemu) info migrate Migration status: completed Actual results: The output information is not detail. Expected results: 1. Add more detail information to rhel6 like rhel7. 2. After migration finished, should also show the statistics output instead of only "Migration Status". Additional info:
Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.377.el6.x86_64 How reproducible: Always
Verified this bug on qemu-kvm-0.12.1.2-2.398.el6.x86_64. 1. Boot a guest: /usr/libexec/qemu-kvm -cpu SandyBridge -M rhel6.5.0 -enable-kvm -m 2048 -smp 2,sockets=2,cores=1,threads=1 -name rhel6.4-64 -uuid 9a0e67ec-f286-d8e7-0548-0c1c9ec93009 -nodefconfig -nodefaults -monitor stdio -rtc base=utc,clock=host,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/home/RHEL-Server-6.4-64-virtio.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=1,drive=drive-ide0-1-0,id=ide0-1-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=0x3 -chardev socket,id=charserial0,path=/tmp/isa-serial,server,nowait -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=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -qmp tcp:0:5566,server,nowait -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 2. Boot the guest on another terminal of host with listening mode "-incoming tcp:0:5800", replace the vnc port and qmp port to some other value. 3. Migrate guest. (qemu) migrate -d tcp:0:5800 4. Check the migration status until finish. (qemu) info migrate Migration status: active total time: 9157 milliseconds transferred ram: 286799 kbytes remaining ram: 293148 kbytes total ram: 2113920 kbytes (qemu) info migrate Migration status: completed total time: 15950 milliseconds downtime: 46 milliseconds transferred ram: 548803 kbytes remaining ram: 56 kbytes total ram: 2113920 kbytes (qemu) info migrate Migration status: completed total time: 15950 milliseconds downtime: 46 milliseconds transferred ram: 548803 kbytes remaining ram: 164 kbytes total ram: 2113920 kbytes (qemu) info migrate Migration status: completed total time: 15950 milliseconds downtime: 46 milliseconds transferred ram: 548803 kbytes remaining ram: 216 kbytes total ram: 2113920 kbytes ..... (many time's repeat of "info migrate") (qemu) info migrate Migration status: completed total time: 15950 milliseconds downtime: 46 milliseconds transferred ram: 548803 kbytes remaining ram: 604 kbytes total ram: 2113920 kbytes Hi, Orit Could you help check the step 4 outputs? After the migration has completed, the "remaining ram" values will increase from a small value to a larger one (604k in this case). And then will not change any more. In my opinion, it should be 0k after finish migration. Thanks, Qunfang
Hi Qunfang, I would expect remaining ram to become 0 after migration completes. It looks like a problem with the accounting of the remaining ram. Adding the migration stats has exposed this issue, can you open a Bz for it. Thanks, Orit
(In reply to Orit Wasserman from comment #10) > Hi Qunfang, > I would expect remaining ram to become 0 after migration completes. > It looks like a problem with the accounting of the remaining ram. > Adding the migration stats has exposed this issue, can you open a Bz for it. > > Thanks, > Orit Hi, Orit Get it and I create bug 1000231 to track this issue. As the migration statistics output has been added, so I would like to set this bug status to VERIFIED. And let's track the 'remaining ram' issue in bug 1000231. Thanks. Qunfang
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-1553.html