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 1321304 - Migration status become 'setup' after creating a internal snapshot in guest
Summary: Migration status become 'setup' after creating a internal snapshot in guest
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 7.4
Assignee: Juan Quintela
QA Contact: xianwang
URL:
Whiteboard:
Depends On:
Blocks: 1401400
TreeView+ depends on / blocked
 
Reported: 2016-03-25 10:29 UTC by Pei Zhang
Modified: 2017-05-03 11:57 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-03 11:57:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Pei Zhang 2016-03-25 10:29:14 UTC 
Description of problem:
Migration status become 'setup' after creating a internal snapshot in guest. 

Version-Release number of selected component (if applicable):
kernel:3.10.0-330.el7.x86_64
qemu-kvm-rhev:qemu-kvm-rhev-2.5.0-3.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Boot a guest
/usr/libexec/qemu-kvm \
-name mg \
-machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off,vmport=off \
-cpu Penryn \
-m 1024 -realtime mlock=off \
-smp 1,sockets=1,cores=1,threads=1 \
-monitor stdio \
-drive file=/nfs/images/mg.1458889181,format=qcow2,if=none,id=drive-virtio-disk0 \
-device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \

2. Create internal snapshot
(qemu) savevm sn1

3. Check status of migrate, it becomes 'setup'
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off 
Migration status: setup
total time: 0 milliseconds

Actual results:
status of migrate become 'setup'

Expected results:
status of migrate should keeps blank.


Additional info:
I also tested in rhel7.2.z with below versions and did not hit this issue. So this bug is a regression bug.
Versions:
3.10.0-327.13.1.el7.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.10.x86_64
Comment 4 Juan Quintela 2016-08-24 15:23:27 UTC 
Not fixed upstream yet.
Comment 6 xianwang 2017-04-06 09:22:01 UTC 
<quintela> about 1321304 .... why do you expect status to be clear, if you use libvirt, it is going to be completed

zhang pei,
could you help to reply to quintela's problem? thanks
Comment 8 Pei Zhang 2017-04-07 02:17:25 UTC 
(In reply to xianwang from comment #6)
> <quintela> about 1321304 .... why do you expect status to be clear, if you
> use libvirt, it is going to be completed
> 
> zhang pei,
> could you help to reply to quintela's problem? thanks

Hi Xianxian,

In RHEL7.3, the key point of this bug is it will case the migration fail, so this is real issue.

Re-test with RHEL7.3GA:
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off postcopy-ram: off 
Migration status: setup
total time: 0 milliseconds
(qemu) migrate -d tcp:10.66.9.128:5555
There's a migration process in progress


However, in RHEL7.4, the migration can work well after "savevm". 

I noticed the status of the migration become "completed" after "savevm" even though there is no migration job. It's perfect if the "info migrate" shows blank when there is no real migration. But the "completed" status is also OK to me, because it doesn't cause any issue. From this point of view, I guess this bug has been fixed.


The with RHEL7.4:
3.10.0-643.el7.x86_64
qemu-kvm-rhev-2.9.0-0.el7.patchwork201703291116.x86_64

(qemu) savevm sn1
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off postcopy-ram: off x-colo: off release-ram: off 
Migration status: completed
total time: 1694929 milliseconds
downtime: 0 milliseconds
setup: 0 milliseconds
transferred ram: 497157 kbytes
throughput: 0.00 mbps
remaining ram: 0 kbytes
total ram: 4326224 kbytes
duplicate: 959614 pages
skipped: 0 pages
normal: 121942 pages
normal bytes: 487768 kbytes
dirty sync count: 2
(qemu) migrate -d tcp:10.73.72.152:5555
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off postcopy-ram: off x-colo: off release-ram: off 
Migration status: active
total time: 3546 milliseconds
expected downtime: 300 milliseconds
setup: 425 milliseconds
transferred ram: 43737 kbytes
throughput: 141.79 mbps
remaining ram: 3445532 kbytes
total ram: 4326224 kbytes
duplicate: 1169333 pages
skipped: 0 pages
normal: 132395 pages
normal bytes: 529580 kbytes
dirty sync count: 1



Thanks,
Pei
Comment 9 Juan Quintela 2017-05-03 11:57:42 UTC 
Closing as they are happy with current result of Last Release.
Note You need to log in before you can comment on or make changes to this bug.