Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
I was able to reproduce misbehavior on fairly recent source tree, but it appears to fixed in the current git HEAD, commit id:
c5b6537b1f1f3e126c2f06f84ca88fe3df6cde34
The only thing to note is that the domain will begin running on the dst host when the migration completes. It's not entirely clear to me if that's a bug or not.
(In reply to comment #2)
> I was able to reproduce misbehavior on fairly recent source tree, but it
> appears to fixed in the current git HEAD, commit id:
>
> c5b6537b1f1f3e126c2f06f84ca88fe3df6cde34
>
> The only thing to note is that the domain will begin running on the dst host
> when the migration completes. It's not entirely clear to me if that's a bug or
> not.
Moving to MODIFIED.
tested with
libvirt-0.9.4-12.el6.x86_64
qemu-kvm-0.12.1.2-2.192.el6.x86_64
kernel-2.6.32-197.el6.x86_64
Steps
1. start domain "migrate"
# virsh start migrate
2. wait for the domain fully started.
3. prepare migration environment and do migrate
# virsh migrate --live migrate qemu+ssh://${dest_host_ip}/system
4.Before step 3 finished,open the other terminal and suspend guest os on source
host .
Result:
Guest could be migrated successfully . So set bug status to VERIFIED
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/RHBA-2011-1513.html
Description of problem: When do migration, pause the domain will cause migration error. on 0.8.7-18 there is no problem, so it is a regression bug. Version-Release number of selected component (if applicable): kernel-2.6.32-171.el6.x86_64 qemu-kvm-0.12.1.2-2.172.el6.x86_64 libvirt-0.9.4-0rc1.el6.x86_64 How reproducible: 80% Steps to Reproduce: 1. start domain "migrate" # virsh start migrate 2. wait for the domain fully started. 3. prepare migration environment and do migrate # virsh migrate --live migrate qemu+ssh://${dest_host_ip}/system 4.Before step 3 finished,open the other terminal and suspend guest os on source host . # virsh suspend migrate Actual results: migration will report error: error: An error occurred, but the cause is unknown Expected results: migration will succeed Additional info: with LIBVIRT_DEBUG=1 .... 16:10:57.802: 23407: debug : virDomainFree:2144 : dom=0x7f421c0008c0, (VM: name=rhel61, uuid=303b0ad4-c3b2-d75b-28e8-76f3cee0b78f), 16:10:57.802: 23407: debug : virUnrefDomain:276 : unref domain 0x7f421c0008c0 rhel61 1 16:10:57.802: 23407: debug : virReleaseDomain:238 : release domain 0x7f421c0008c0 rhel61 303b0ad4-c3b2-d75b-28e8-76f3cee0b78f 16:10:57.802: 23407: debug : virReleaseDomain:246 : unref connection 0x16f58f0 3 16:10:57.802: 23406: debug : virDomainFree:2144 : dom=0x16f5c30, (VM: name=rhel61, uuid=303b0ad4-c3b2-d75b-28e8-76f3cee0b78f), 16:10:57.802: 23406: debug : virUnrefDomain:276 : unref domain 0x16f5c30 rhel61 1 16:10:57.802: 23406: debug : virReleaseDomain:238 : release domain 0x16f5c30 rhel61 303b0ad4-c3b2-d75b-28e8-76f3cee0b78f 16:10:57.802: 23406: debug : virReleaseDomain:246 : unref connection 0x16f58f0 2 error: An error occurred, but the cause is unknown 16:10:57.802: 23406: debug : virConnectClose:1320 : conn=0x16f58f0 16:10:57.802: 23406: debug : virUnrefConnect:145 : unref connection 0x16f58f0 1 16:10:57.802: 23406: debug : virReleaseConnect:94 : release connection 0x16f58f0 ...