|
No progress here. The PV domUs seem to migrate just fine, it's the HVM ones that have issues. I haven't tried an O/S other than Windows in an HVM for migration, either. I also need to try without the GPL PV drivers to see if maybe it is one of the known issues that James Harper mentioned in those drivers.
-Nick
>>> James Pifer <jep@xxxxxxxxxxxxxxxx> 2008/12/17 17:33 >>>
On Fri, 2008-12-12 at 12:31 -0700, Nick Couchman wrote:
> 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
I have a very similar setup. Just got my second server updated and added
to ocfs2 cluster.
SLES10 SP2, xen-3.2.0_16718_18-0.3, Kernel 2.6.16.60-0.33-xen
Tested Windows 2k3 HVM
GPL PV version 0.9.11
Shared storage on OCFS2, using files for domU hard drive
Couldn't wait to try a migration. Same thing. Locked up the domU. 100%
CPU in the domU. Did you make any progress?
I haven't tried a sles domU yet.
Thanks,
James
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.
|
