Bug 669630 - during migration , restart libvirtd on the destination machine will cause the guest paused after being migrated or prevent from a successful migration
Summary: during migration , restart libvirtd on the destination machine will cause the...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-14 06:52 UTC by Vivian Bian
Modified: 2011-04-14 05:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-14 09:11:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Vivian Bian 2011-01-14 06:52:23 UTC
Description of problem:

Sometimes 

[root@source ~]# virsh migrate --live kvm qemu+ssh://10.66.93.106/system
root.93.106's password: 
error: server closed connection: 
error: Reconnected to the hypervisor


[root@target ~]# service libvirtd restart
Stopping libvirtd daemon:                                  [  OK  ]
Starting libvirtd daemon:                                  [  OK  ]

[root@dhcp-93-134 ~]# virsh list --all
 Id Name                 State
----------------------------------

sometimes 

[root@source ~]# virsh migrate --live kvm qemu+ssh://10.66.93.106/system
root.93.106's password: 
error: server closed connection: 
error: Reconnected to the hypervisor


[root@target ~]# service libvirtd restart
Stopping libvirtd daemon:                                  [  OK  ]
Starting libvirtd daemon:                                  [  OK  ]

[root@dhcp-93-134 ~]# virsh list --all
 Id Name                 State
----------------------------------
  5 kvm                  paused 

Version-Release number of selected component (if applicable):
libvirt-0.8.7-1.el6.x86_64

How reproducible:
always

  

Expected results:
guest could be migrated successfully

Additional info:

Comment 2 Vivian Bian 2011-01-14 09:11:24 UTC
libvirt is not able to cope with such situation since during migration, the client (or source libvirtd) has open connections to both sides through which the migration is controlled... if any of the connection is dropped, something will fail; how it fails depends on what libvirtd is restarted and in which migration phase that happens


So this is the expected result . Close this bug as NOTABUG


Note You need to log in before you can comment on or make changes to this bug.