This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-users] HVM Migration

To: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] HVM Migration
From: "Iyer, Anoop" <anoop.iyer@xxxxxxx>
Date: Fri, 12 Dec 2008 15:50:08 -0600
Delivery-date: Fri, 12 Dec 2008 13:52:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4942598E0200009900031D4F@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4942598E0200009900031D4F@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aclckz6FP52AQ5tJR0WhuqWVn20PXgAD8vIw
Thread-topic: [Xen-users] HVM Migration
Is it 32-bit XP?

Since your symptom sounds the same as mine from yesterday with the same 
codebase (mine was Win2003, yours is XP; we're both using GPLPV; I too saw the 
processor pegged and the VM unresponsive) you might try the workaround James 
Harper suggested to me – disabling checksum offload and large send offload in 
the NIC – before doing the migration.

For what it’s worth, my VM that had issues yesterday was also a “migrated” VM 
(not live).


PS: Thanks for your response yesterday. :)

From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Nick Couchman
Sent: Friday, December 12, 2008 1:31 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] HVM Migration

I'm having an issue with migration (live or not) from one Xen system to 
another.  Here's my environment:
- SLES10 SP2, Xen 3.2.0, Kernel 2.6.16 (.60-0.33)
- HVMs running Windows XP SP3
- GPL PV Tools
- Shared storage on OCFS2, using files for domU hard drive.

The issue I have is that, after migration, the Windows domU pegs the CPU and is 
completely unresponsive.  Doesn't matter if the migration is a "live" migration 
or not, the results are the same.  Anyone have any ideas as to what might be 
going on here?

Thanks - Nick
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>