Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 519401

Summary:	Migration of Xen guest results in a paused, unresponsive domU
Product:	Red Hat Enterprise Linux 5	Reporter:	Albert Hopkins <ahopkins>
Component:	xen	Assignee:	Xen Maintainance List <xen-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	high	Docs Contact:
Priority:	medium
Version:	5.3	CC:	casmith, clalance, jdenemar, minovotn, sdodson, smayhew, xen-maint
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-12-16 15:14:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Albert Hopkins 2009-08-26 13:28:51 UTC

When a Xen domU is migrated (via clusvcadm -M) the domU successfully migrates (as reported in both hosts' logs) but the guest sometimes ends up on the target dom0 in a paused state. 

Attempting to unpause the domU (xm unpause) sets the domU back to a blocked state but the domU is still inactive.  There is nothing on the console and the system cannot be pinged.  Running an xm destroy on the domU at this point sometimes results in a zombie.

If a domU ends up in a paused state after a migration we now just destroy it and let the cluster restart the domU again.  We then migration the domU again with no issue.

This issue appears similar to, if not a duplicate of,bug #512300.

Comment 1 Michal Novotny 2009-10-21 06:14:36 UTC

Could you provide us more information about the guest you used? Mainly type (PV/FV) and number of cpus/memory?

Thanks,
Michal

Comment 2 Michal Novotny 2009-10-21 06:17:31 UTC

(In reply to comment #0)
> When a Xen domU is migrated (via clusvcadm -M) the domU successfully migrates
> (as reported in both hosts' logs) but the guest sometimes ends up on the target
> dom0 in a paused state. 
> 
> Attempting to unpause the domU (xm unpause) sets the domU back to a blocked
> state but the domU is still inactive.  There is nothing on the console and the
> system cannot be pinged.  Running an xm destroy on the domU at this point
> sometimes results in a zombie.
> 
> If a domU ends up in a paused state after a migration we now just destroy it
> and let the cluster restart the domU again.  We then migration the domU again
> with no issue.
> 
> This issue appears similar to, if not a duplicate of,bug #512300.  

One more question since I have never run into this issue yet... You are using `clusvcadm -M` command which is cluster administration command, right ? So, you can reproduce it in cluster environment, right? Could you also reproduce it in non-cluster environment ?

Thanks,
Michal

Comment 12 Jiri Denemark 2009-12-16 15:14:32 UTC

Great, thanks for the testing. I'm setting this bug as a dup of bug 522850, then.

*** This bug has been marked as a duplicate of bug 522850 ***

Comment 13 Paolo Bonzini 2010-04-08 15:50:17 UTC

This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).

Comment 14 Chris Lalancette 2010-07-19 13:54:35 UTC

Clearing out old flags for reporting purposes.

Chris Lalancette