Yep - XP 32-bit. Disabled those options on the net card, but still have the same symptoms...|
Thanks - Nick
From: Iyer, Anoop <anoop.iyer@xxxxxxx>
To: Nick Couchman <Nick.Couchman@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] HVM Migration
Date: Fri, 12 Dec 2008 15:50:08 -0600
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
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
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
Xen-users mailing list