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


[Xen-devel] Win2003R2 64 suspend failed in self live migration

To: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Win2003R2 64 suspend failed in self live migration
From: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>
Date: Wed, 15 Jun 2011 20:05:35 +0800
Cc: james.harper@xxxxxxxxxxxxxxxx
Delivery-date: Wed, 15 Jun 2011 05:06:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <BAY0-MC4-F15zXiPuZe00229bef@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BAY0-MC4-F15zXiPuZe00229bef@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi James;
     I've been testing Windows HVM live migration for a while, OS type covers 2003, and 2008.
     It works well most of time. I mean migration been two physical host.
     But 2003R2 64 bit failed on self live migration. (VM migration on the same host)
     After instal debug version PV driver inside VM, not debug log show up.
     Later I learnt that, in your code  you implied that the debug routine could not be hooked since
     "// can't patch IDT on AMD64 "(in xenpci_dbprint.c XenPci_HookDbgPrint())
      I was able to get the log output simply by redefine the KdPrint macro like below. But unfortunately
, VM is suffuring hang now and then. 
      So is it proper to do this, or how to obtain 64bit log properly?
       As for self migration, I've noticed that VM is able to migrate once, but after migration, the network
is in trouble, VM can not access outside.  It looks like xennet is not function properly. Meanwhile, it looks
like "a fake arp" is needed after migration, as linux pv.
        I shall dig more, but currently the hang in log brother me a lot.
        Could you kindly offer me some help?
----------debug log ----       
void xmaoDPrint(PCH Format, ...);
#undef KdPrint
#define KdPrint(A)  xmaoDPrint
void xmaoDPrint(PCHAR fmt, ...){
 char buf[4096];
  va_list argptr;
 memset(buf, 0, 4096);
  va_start(argptr, fmt);
  RtlStringCchVPrintfA(buf, 4095, fmt, argptr);
 XenDbgPrint(buf, (ULONG)strlen(buf));

Xen-devel mailing list