Hi James,


It's a problem that affects any PVonHVM domain afaict, so I'd rather defer to the person who made the change originally.

I did some test. Linux PVM live migration works well on Xen3.4. As you said above, PVHVM fails live migration and got error: "Error: /usr/lib/xen/bin/xc_save 32 8 0 0 5 failed", but save/restore is OK.
So this problem should be fixed on xen side instead of pv driver side?

Following is the log of linux PVHVM live migration:

[2009-08-19 10:52:08 2832] DEBUG (XendCheckpoint:110) [xc_save]: /usr/lib/xen/bin/xc_save 32 8 0 0 5
[2009-08-19 10:52:08 2832] INFO (XendCheckpoint:418) xc_save: failed to get the suspend evtchn port
[2009-08-19 10:52:08 2832] INFO (XendCheckpoint:418)
[2009-08-19 10:52:08 2832] INFO (XendCheckpoint:418) Saving memory pages: iter 1   0%ERROR Internal error: Error when writing to state file (4a) (errno 104)
[2009-08-19 10:52:08 2832] INFO (XendCheckpoint:418) Save exit rc=1
[2009-08-19 10:52:08 2832] ERROR (XendCheckpoint:164) Save failed on domain OVM_EL5U3_X86_PVHVM_4GB (8) - resuming.
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 132, in save
    forkHelper(cmd, fd, saveInputHandler, False)
File "/usr/lib/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 406, in forkHelper
    raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib/xen/bin/xc_save 32 8 0 0 5 failed
[2009-08-19 10:52:08 2832] DEBUG (XendDomainInfo:2806) XendDomainInfo.resumeDomain(8)

Thanks
Annie.