I''m using XEN 3.1 and am trying to do some XEN VM migration with Windows HVMs. When I try to migrate the VM, the VM gets renamed and the new one created on the new host, but it hangs waiting for the original VM to suspend. The following messages appear in the xm log output: [2007-11-30 11:46:33 6565] DEBUG (XendCheckpoint:88) [xc_save]: /usr/lib64/xen/b in/xc_save 23 3 0 0 4 [2007-11-30 11:46:33 6565] DEBUG (XendCheckpoint:88) [xc_save]: /usr/lib64/xen/b in/xc_save 23 3 0 0 4 [2007-11-30 11:46:33 6565] DEBUG (XendCheckpoint:320) suspend [2007-11-30 11:46:33 6565] DEBUG (XendCheckpoint:320) suspend [2007-11-30 11:46:33 6565] DEBUG (XendCheckpoint:91) In saveInputHandler suspend [2007-11-30 11:46:33 6565] DEBUG (XendCheckpoint:91) In saveInputHandler suspend [2007-11-30 11:46:33 6565] DEBUG (XendCheckpoint:93) Suspending 3 ... [2007-11-30 11:46:33 6565] DEBUG (XendCheckpoint:93) Suspending 3 ... [2007-11-30 11:46:33 6565] DEBUG (XendDomainInfo:443) XendDomainInfo.shutdown(su spend) [2007-11-30 11:46:33 6565] DEBUG (XendDomainInfo:443) XendDomainInfo.shutdown(su spend) [2007-11-30 11:46:33 6565] DEBUG (XendDomainInfo:931) XendDomainInfo.handleShutd ownWatch [2007-11-30 11:46:33 6565] DEBUG (XendDomainInfo:931) XendDomainInfo.handleShutd ownWatch And that''s about it - the xm migrate (or suspend) command just hangs and waits. The VM is still accessible via something like virt-manager and is still running. Anyone have any suggestions for getting this to work. Another related items seems to be that xm shutdown does not work, either - it produces the same behavior, the log just says "shutdown" instead of "suspend." Thanks, Nick _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users